[Dev-Docs AI Improvement]: Manage your apps in Developer Portal #13652
Conversation
…eveloper-portal.md by yashy797
Acrolinx ScorecardsWe currently enforce a minimum score of 80. Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:
More info about Acrolinx Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally. |
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit a2c735b: ✅ Validation status: passed
For more details, please refer to the build report. |
There was a problem hiding this comment.
Pull request overview
This PR updates the documentation for "Manage your apps in Developer Portal" to improve clarity and readability. The changes focus on streamlining language, improving grammar, and ensuring consistent terminology throughout the document.
Key Changes:
- Improved grammar and readability by replacing verbose phrases with more concise alternatives (e.g., "you can see" → "you see", "allows you to" → "lets you")
- Enhanced clarity by simplifying technical descriptions and removing unnecessary words
- Standardized article usage for product names and technical terms
| # Manage your apps in Developer Portal | ||
|
|
||
| After you upload your app in Microsoft Teams, you can manage your app in Developer Portal. The article provides comprehensive guidance on app configuration, analytics, and validation to enhance the Teams app experience.<br> | ||
| After you upload your app in Microsoft Teams, you can manage your app in Developer Portal. This article provides comprehensive guidance on app configuration, analytics, and validation to enhance Teams app experience.<br> |
There was a problem hiding this comment.
Grammar issue: The article should use "the" before "Teams app experience" for proper article usage.
Suggested change: "to enhance the Teams app experience" → "to enhance the Teams app experience"
| After you upload your app in Microsoft Teams, you can manage your app in Developer Portal. This article provides comprehensive guidance on app configuration, analytics, and validation to enhance Teams app experience.<br> | |
| After you upload your app in Microsoft Teams, you can manage your app in Developer Portal. This article provides comprehensive guidance on app configuration, analytics, and validation to enhance the Teams app experience.<br> |
| * **Single sign-on**: Bot registered on Microsoft Entra ID supports single sign-on (SSO). If a bot is registered on Bot Framework portal (or within the Developer Portal under **Bot management**), then a bot doesn't support SSO, and you have to register your bot on Microsoft Entra ID to support SSO. For a bot registered on Microsoft Entra ID, add the **Application ID URI**. To get **Application ID URI** from Microsoft Entra ID, see [how to use SSO authentication for bots](../../bots/how-to/authentication/auth-aad-sso-bots.md). | ||
| * **Languages**: This section allows you to set up or change the language of your app. | ||
| * **Domain**: This section allows you to add the domains to load your apps in the Teams client, such as *.example.com. | ||
| * **Single sign-on**: Bot registered on Microsoft Entra ID supports single sign-on (SSO). If a bot registers on Bot Framework portal (or within Developer Portal under **Bot management**), then the bot doesn't support SSO, and you must register your bot on Microsoft Entra ID to support SSO. For a bot registered on Microsoft Entra ID, add **Application ID URI**. To get **Application ID URI** from Microsoft Entra ID, see [how to use SSO authentication for bots](../../bots/how-to/authentication/auth-aad-sso-bots.md). |
There was a problem hiding this comment.
Grammar issue: Inconsistent verb tense. "If a bot registers" should be "If a bot is registered" to match the passive voice used in the surrounding sentence structure.
Suggested change: "If a bot registers on Bot Framework portal" → "If a bot is registered on Bot Framework portal"
| * **Single sign-on**: Bot registered on Microsoft Entra ID supports single sign-on (SSO). If a bot registers on Bot Framework portal (or within Developer Portal under **Bot management**), then the bot doesn't support SSO, and you must register your bot on Microsoft Entra ID to support SSO. For a bot registered on Microsoft Entra ID, add **Application ID URI**. To get **Application ID URI** from Microsoft Entra ID, see [how to use SSO authentication for bots](../../bots/how-to/authentication/auth-aad-sso-bots.md). | |
| * **Single sign-on**: Bot registered on Microsoft Entra ID supports single sign-on (SSO). If a bot is registered on Bot Framework portal (or within Developer Portal under **Bot management**), then the bot doesn't support SSO, and you must register your bot on Microsoft Entra ID to support SSO. For a bot registered on Microsoft Entra ID, add **Application ID URI**. To get **Application ID URI** from Microsoft Entra ID, see [how to use SSO authentication for bots](../../bots/how-to/authentication/auth-aad-sso-bots.md). |
| * **Domain**: This section allows you to add the domains to load your apps in the Teams client, such as *.example.com. | ||
| * **Single sign-on**: Bot registered on Microsoft Entra ID supports single sign-on (SSO). If a bot registers on Bot Framework portal (or within Developer Portal under **Bot management**), then the bot doesn't support SSO, and you must register your bot on Microsoft Entra ID to support SSO. For a bot registered on Microsoft Entra ID, add **Application ID URI**. To get **Application ID URI** from Microsoft Entra ID, see [how to use SSO authentication for bots](../../bots/how-to/authentication/auth-aad-sso-bots.md). | ||
| * **Languages**: This section lets you set up or change your app language. | ||
| * **Domain**: This section lets you add domains to load your apps in Teams client, such as *.example.com. |
There was a problem hiding this comment.
Grammar issue: Missing article "the" before "Teams client".
Suggested change: "add domains to load your apps in Teams client" → "add domains to load your apps in the Teams client"
| * **Domain**: This section lets you add domains to load your apps in Teams client, such as *.example.com. | |
| * **Domain**: This section lets you add domains to load your apps in the Teams client, such as *.example.com. |
| > * 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. | ||
| > * Bots created using Microsoft Teams Developer Portal are **single tenant** by default. | ||
| > * **Multi tenant** bots are deprecated, but bots already created as **Multi tenant** continue to work as expected. | ||
| > * When you create a bot using Developer Portal, a corresponding [servicePrincipal](/graph/api/resources/serviceprincipal?view=graph-rest-1.0&preserve-view=true) automatically creates in your Microsoft Entra ID tenant. |
There was a problem hiding this comment.
Grammar issue: Passive voice usage is inconsistent. The phrase "automatically creates in your Microsoft Entra ID tenant" should be "is automatically created in your Microsoft Entra ID tenant" to match the passive voice pattern used in the documentation.
Suggested change: "a corresponding servicePrincipal automatically creates in your Microsoft Entra ID tenant" → "a corresponding servicePrincipal is automatically created in your Microsoft Entra ID tenant"
| > * When you create a bot using Developer Portal, a corresponding [servicePrincipal](/graph/api/resources/serviceprincipal?view=graph-rest-1.0&preserve-view=true) automatically creates in your Microsoft Entra ID tenant. | |
| > * When you create a bot using 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. |
| > * Bots created using Microsoft Teams Developer Portal are **single tenant** by default. | ||
| > * **Multi tenant** bots are deprecated, but bots already created as **Multi tenant** continue to work as expected. | ||
| > * When you create a bot using Developer Portal, a corresponding [servicePrincipal](/graph/api/resources/serviceprincipal?view=graph-rest-1.0&preserve-view=true) automatically creates in your Microsoft Entra ID tenant. | ||
| > * In delegated scenarios with work or school accounts, the admin must assign a supported [Microsoft Entra role](/entra/identity/role-based-access-control/permissions-reference?toc=%2Fgraph%2Ftoc.json) or a custom role with supported role permission. The following least privileged roles support this operation. |
There was a problem hiding this comment.
Grammar issue: Missing article "a" before "supported role permission".
Suggested change: "or a custom role with supported role permission" → "or a custom role with a supported role permission"
| > * In delegated scenarios with work or school accounts, the admin must assign a supported [Microsoft Entra role](/entra/identity/role-based-access-control/permissions-reference?toc=%2Fgraph%2Ftoc.json) or a custom role with supported role permission. The following least privileged roles support this operation. | |
| > * In delegated scenarios with work or school accounts, the admin must assign 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 support this operation. |
| ## Publish | ||
|
|
||
| In the **Publish** section, you can publish your app to your org or to the Teams Store. | ||
| In the **Publish** section, you can publish your app to your org or to Microsoft Teams Store. |
There was a problem hiding this comment.
Grammar issue: Missing article "the" before "Microsoft Teams Store".
Suggested change: "publish your app to your org or to Microsoft Teams Store" → "publish your app to your org or to the Microsoft Teams Store"
| In the **Publish** section, you can publish your app to your org or to Microsoft Teams Store. | |
| In the **Publish** section, you can publish your app to your org or to the Microsoft Teams Store. |
| Agent Identity Blueprint provides reusable configurations for agents in **Agent 365** that perform tasks and interact with users or Microsoft 365 services. Each blueprint acts as a template that specifies how an agent configures and connects to a back-end service. | ||
|
|
||
| Agent Identity Blueprints are created and managed in **Developer Portal**, while the agent identities derived from them are managed in the **Microsoft 365 Admin Center**. To get started and for complete end-to-end guidance on extending your agent to Agent 365, use the [Microsoft Agent 365 SDK](/microsoft-agent-365/developer/?tabs=python). | ||
| Agent Identity Blueprints create and manage in Developer Portal, while agent identities derived from them manage in Microsoft 365 Admin Center. To get started and for complete end-to-end guidance on extending your agent to Agent 365, use [Microsoft Agent 365 SDK](/microsoft-agent-365/developer/?tabs=python). |
There was a problem hiding this comment.
Grammar issue: Passive voice usage is inconsistent. The phrase "create and manage in Developer Portal" and "manage in Microsoft 365 Admin Center" should be "are created and managed in Developer Portal" and "are managed in the Microsoft 365 Admin Center" to maintain consistent passive voice and include the article "the".
Suggested change: "Agent Identity Blueprints create and manage in Developer Portal, while agent identities derived from them manage in Microsoft 365 Admin Center" → "Agent Identity Blueprints are created and managed in Developer Portal, while agent identities derived from them are managed in the Microsoft 365 Admin Center"
| Agent Identity Blueprints create and manage in Developer Portal, while agent identities derived from them manage in Microsoft 365 Admin Center. To get started and for complete end-to-end guidance on extending your agent to Agent 365, use [Microsoft Agent 365 SDK](/microsoft-agent-365/developer/?tabs=python). | |
| Agent Identity Blueprints are created and managed in Developer Portal, while agent identities derived from them are managed in the Microsoft 365 Admin Center. To get started and for complete end-to-end guidance on extending your agent to Agent 365, use [Microsoft Agent 365 SDK](/microsoft-agent-365/developer/?tabs=python). |
| :::image type="content" source="../../assets/images/tdp/create-new-agent-blueprint.png" alt-text="Create a new agent blueprint window" lightbox="../../assets/images/tdp/create-new-agent-blueprint.png"::: | ||
|
|
||
| A unique **Agent Blueprint ID** is automatically generated. This ID is used when you create agent identities based on this blueprint. | ||
| A unique **Agent Blueprint ID** automatically generates. This ID uses when you create agent identities based on this blueprint. |
There was a problem hiding this comment.
Grammar issue: The phrase "This ID uses when you create" is missing "is". It should be "This ID is used when you create" to form a proper passive voice construction.
Suggested change: "This ID uses when you create agent identities based on this blueprint" → "This ID is used when you create agent identities based on this blueprint"
| A unique **Agent Blueprint ID** automatically generates. This ID uses when you create agent identities based on this blueprint. | |
| A unique **Agent Blueprint ID** is automatically generated. This ID is used when you create agent identities based on this blueprint. |
| * **Announcement**: Latest updates of your apps on Developer Portal. | ||
| * **Active users (Preview)**: Shows you the active user count. | ||
| * **Basic information**: Shows you the **App ID**, **Version**, **Manifest version**, and other basic information. | ||
| * **Active users (Preview)**: Displays active user count. |
There was a problem hiding this comment.
Grammar issue: Missing article "the" before "active user count".
Suggested change: "Displays active user count" → "Displays the active user count"
| * **Active users (Preview)**: Displays active user count. | |
| * **Active users (Preview)**: Displays the active user count. |
|
|
||
| 1. **Agent Blueprint ID**: A system-generated unique identifier for the blueprint. | ||
| 1. **Name**: The name assigned when the blueprint was created. | ||
| 1. **Name**: The name assigned when the blueprint created. |
There was a problem hiding this comment.
Grammar issue: Missing article "the" and passive voice inconsistency.
Suggested change: "The name assigned when the blueprint created" → "The name assigned when the blueprint was created"
| 1. **Name**: The name assigned when the blueprint created. | |
| 1. **Name**: The name assigned when the blueprint was created. |
This PR updates the content of the file: msteams-platform/concepts/build-and-test/manage-your-apps-in-developer-portal.md.
Submitted by: @yashy797