diff --git a/msteams-platform/concepts/build-and-test/manage-your-apps-in-developer-portal.md b/msteams-platform/concepts/build-and-test/manage-your-apps-in-developer-portal.md
index 75b165b4127..bd72edd69ea 100644
--- a/msteams-platform/concepts/build-and-test/manage-your-apps-in-developer-portal.md
+++ b/msteams-platform/concepts/build-and-test/manage-your-apps-in-developer-portal.md
@@ -258,6 +258,17 @@ To add a bot:
 
     :::image type="content" source="../../assets/images/tdp/Add_new_bot.PNG" alt-text="Add a new bot by using bot management option." lightbox="../../assets/images/tdp/Add_new_bot.PNG":::
 
+> [!NOTE]
+>
+> * When you create a bot using the **Microsoft Teams Developer Portal**, a corresponding [servicePrincipal](/graph/api/resources/serviceprincipal?view=graph-rest-1.0&preserve-view=true) is automatically created in your **Microsoft Entra ID** tenant.
+> * In delegated scenarios with work or school accounts, the admin must be assigned a supported [Microsoft Entra role](/entra/identity/role-based-access-control/permissions-reference?toc=%2Fgraph%2Ftoc.json) or a custom role with a supported role permission. The following least privileged roles are supported for this operation.
+>
+>   * For multitenant apps:
+>     * Application Administrator
+>     * Cloud Application Administrator
+>
+>   * For single-tenant apps where the calling user is a nonadmin user but is the owner of the backing application, the user must have the *Application Developer* role.
+
 From the Developer Portal, you can go to Bot Framework portal and configure your bot to update icon and other properties.
 
   > [!NOTE]