[Dev-Docs AI Improvement]: Manage your apps in Developer Portal #13653
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 d0ef182: ✅ Validation status: passed
For more details, please refer to the build report. |
| * **Analytics** | ||
|
|
||
| In the **Analytics** under **Overview** section, you can get an overview of your app's usage, engagement, and other insights. For more information, see [how to analyze your app's usage](analyze-your-apps-usage-in-developer-portal.md). | ||
| In the **Analytics** under **Overview** section, you access insights into your app's usage, engagement, and other metrics. For more information, see [how to analyze your app's usage](analyze-your-apps-usage-in-developer-portal.md). |
There was a problem hiding this comment.
This change is not necessary, getting an insight is not equal to getting an overview. Also, don't change insights into metrics.
| ## Configure | ||
|
|
||
| To install and render your app in Teams, you must include a set of configurations that Teams recognizes. To upload your apps in Teams, you need to have app manifest, which contains all the app details to display your app in Teams. This can be achieved with the help of components and tools that are available in Developer Portal. | ||
| To install and render your app in Teams, you must include a set of configurations that Teams recognizes. To upload your apps in Teams, you need an app manifest that contains all the details required to display your app in Teams. You achieve this with the components and tools provided in Developer Portal. |
There was a problem hiding this comment.
"You achieve this with the components and tools provided in Developer Portal." to be changed to "You can achieve this with the components and tools provided in Developer Portal."
| :::image type="content" source="../../assets/images/tdp/configure.png" alt-text="The screenshot is an example that shows how to configure features to manage and access your app in Developer Portal."::: | ||
|
|
||
| In the **Configure** section, you can see the following components to manage and access your app: | ||
| In the **Configure** section, you find the following components to manage and access your app: |
There was a problem hiding this comment.
This change is not required.
| > [!NOTE] | ||
| > Connector is available in Government Community Cloud (GCC) but isn't available in GCC High, Department of Defense (DoD), and Teams operated by 21Vianet environments. | ||
| * **App package editor**: This section allows you to create, manage, and customize app packages for Teams. Similar to Visual Studio Code, it enables you to seamlessly edit your app’s components, including the manifest, icons, Copilot agent files, scenes, JSON, and YAML files. You can also add a declarative agent and its related files into your app package. | ||
| * **App package editor**: This section enables you to create, manage, and customize app packages for Teams. Similar to Visual Studio Code, it allows seamless editing of your app’s components, including the manifest, icons, Copilot agent files, scenes, JSON, and YAML files. You can also add a declarative agent and its associated files to your app package. |
There was a problem hiding this comment.
The change of enables to allows is not required "it enables you to seamlessly edit". It can be "enables seamless editing" of..
| :::image type="content" source="../../assets/images/tdp/package-editor.png" alt-text="Screenshot shows you the App package editor in Teams developer portal." lightbox="../../assets/images/tdp/app-package-editor.png"::: | ||
|
|
||
| After you edit or add new files to your app package, you can either discard or update the package. If you select **Update**, the Developer Portal reviews the files and identifies errors. You can save the package with errors, but you must resolve them before you publish. | ||
| After editing or adding new files to your app package, you can either discard or update the package. If you select **Update**, Developer Portal reviews the files and identifies any errors. You can save the package with errors, but you must resolve them before you publish. |
| * **Owners** | ||
|
|
||
| Each app includes an **Owners** page, where you can share your app registration with others in your org. You can add **Administrator** and **Operative** role to manage who can change the settings of your app. The **Operative** role has a permission, such as updating an app's configuration. The **Administrator** role has the permissions, such as updating an app's configuration, adding or removing owners, and deleting an app. If there are no active owners for an app, admins can own the apps by entering the app ID in Teams Developer Portal. | ||
| Each app includes an **Owners** page, where you share your app registration with others in your organization. You can add **Administrator** and **Operative** roles to control who can change the settings of your app. The **Operative** role permits actions such as updating an app's configuration. The **Administrator** role permits actions such as updating an app's configuration, adding or removing owners, and deleting an app. If there are no active owners for an app, admins can claim the app by entering the app ID in Developer Portal. |
There was a problem hiding this comment.
Retain "manage". Retain both cases of "has the/a permission".
| 1. Before downloading your app package (for example, when preparing to publish to Microsoft Teams Store), select the environment you want to use. Your app configurations update automatically based on the environment. | ||
|
|
||
| * **Plan and pricing**: You can link a Software-as-a-Services (SaaS) offer that you've created in the Partner center for your app. | ||
| * **Plan and pricing**: You can link a Software-as-a-Services (SaaS) offer created in Partner center for your app. |
There was a problem hiding this comment.
Change not required.
SukanyaDas-MSFT
left a comment
SukanyaDas-MSFT
left a comment
There was a problem hiding this comment.
Please have a look at the comments and make the changes. Thanks!
| :::image type="content" source="../../assets/images/tdp/app-validation-in-progress.png" alt-text="Screenshot shows you the App validation in progress." lightbox="../../assets/images/tdp/app-validation-in-progress.png"::: | ||
|
|
||
| The app validation status is updated as follows: | ||
| The app validation status updates as follows: |
| |**Success**| Complete | Pass | No issues. | | ||
| |**Warning** | Complete | Pass | Fixing this issue is optional but recommended. | | ||
| |**Error** | Complete | Fail | Fixing the issue is required to successfully publish the app. | | ||
| |**Skipped**|Incomplete |NA | We weren't able to continue the validation check. This may be a temporary issue. We recommend you rerun the test later.| |
There was a problem hiding this comment.
The result message is changing. Revert to original.
| * **Bot ID**: If you selected Bot-based, provide the ID of your registered Teams bot. | ||
| * **Backend URL**: If you selected API-based, provide the URL of your back-end service endpoint. | ||
| * **Bot ID**: If Bot Based, provide the ID of your registered Teams bot. | ||
| * **Backend URL**: If API Based, provide the URL of your back-end service endpoint. |
There was a problem hiding this comment.
Redundant change, revert to original.
This PR updates the content of the file: msteams-platform/concepts/build-and-test/manage-your-apps-in-developer-portal.md.
Submitted by: @yashy797