From 0d868e95e32534d96d030fd75b65f7a4532e3410 Mon Sep 17 00:00:00 2001 From: SirajShaik-MSFT Date: Fri, 26 Sep 2025 15:09:34 +0530 Subject: [PATCH] Update publish.md --- .../deploy-and-publish/appsource/publish.md | 112 +++++++++--------- 1 file changed, 53 insertions(+), 59 deletions(-) diff --git a/msteams-platform/concepts/deploy-and-publish/appsource/publish.md b/msteams-platform/concepts/deploy-and-publish/appsource/publish.md index 7129cdd79ec..43c0e735470 100644 --- a/msteams-platform/concepts/deploy-and-publish/appsource/publish.md +++ b/msteams-platform/concepts/deploy-and-publish/appsource/publish.md @@ -7,141 +7,135 @@ ms.author: surbhigupta ms.localizationpriority: high ms.date: 12/15/2022 --- -# Publish your app to the Teams Store +# Publish your app and agent to the Teams Store -You can publish your app directly to the Microsoft Teams Store inside Microsoft Teams and reach millions of users around the world. If your app is also featured in the Teams Store, you can instantly reach potential customers. +You can publish your app and agent directly to the Microsoft Teams Store inside Microsoft Teams and reach millions of users around the world. If your app and agent are also featured in the Teams Store, you can instantly reach potential customers. -Apps published to the Teams Store also automatically list on [the Microsoft commercial marketplace](https://appsource.microsoft.com), which is the official marketplace for Microsoft 365 apps and solutions. - -The following video on publish your Teams app to Teams Store outlines the steps involved in the app publishing process: - -
- -> [!VIDEO https://www.youtube.com/embed/cFqAuLy0JaE] +Apps and agents published to the Teams Store also automatically list on [the Microsoft commercial marketplace](https://appsource.microsoft.com), which is the official marketplace for Microsoft 365 apps and solutions. ## Understand the publishing process -If your app is production ready, you can begin the process of getting it listed on the Teams Store. +If your app and agent are production ready, you can begin the process of getting it listed on the Teams Store. > [!TIP] -> Following the pre-submission steps closely can increase the possibility that Microsoft approves your app for publishing. +> Following the pre-submission steps closely can increase the possibility that Microsoft approves your app and agent for publishing. :::image type="content" source="../../../assets/images/submission/teams-app-store-publish-process.png" alt-text="Diagram shows the Teams Store publishing process for Teams apps." lightbox="../../../assets/images/submission/teams-app-store-publish-process.png"::: -1. [Review the Teams Store validation guidelines](~/concepts/deploy-and-publish/appsource/prepare/teams-store-validation-guidelines.md) to ensure your app meets Teams app and Teams Store standards. +1. [Review the Teams Store validation guidelines](~/concepts/deploy-and-publish/appsource/prepare/teams-store-validation-guidelines.md) to ensure your app and agent meets Teams app and Teams Store standards. 1. [Create a Partner Center developer account](~/concepts/deploy-and-publish/appsource/prepare/create-partner-center-dev-account.md). 1. [Prepare your Teams Store submission](~/concepts/deploy-and-publish/appsource/prepare/submission-checklist.md), which includes running automated tests, compiling test notes, creating a Teams Store listing, among other important tasks to help expedite the review process. -1. [Submit your app](/office/dev/store/add-in-submission-guide) through Partner Center. +1. [Submit your app and agent](/office/dev/store/add-in-submission-guide) through Partner Center. -1. If your submission fails, work with Microsoft directly to [resolve the issues and resubmit your app](~/concepts/deploy-and-publish/appsource/resolve-submission-issues.md). +1. If your submission fails, work with Microsoft directly to [resolve the issues and resubmit your app and agent](~/concepts/deploy-and-publish/appsource/resolve-submission-issues.md). -## What to expect after you submit your app? +## What to expect after you submit your app and agent? * **Deep functional and experience tests** - Your app is thoroughly reviewed by a validator to ensure compliance with the [Microsoft Commercial Marketplace certification policies](/legal/marketplace/certification-policies). - There's a focus on deep functional and user experience testing, usability checks, and metadata checks. App validation is performed across desktop, web, and mobile clients. We work hard to provide you with a detailed test report in 24 working hours post submission. + Your app and agent are thoroughly reviewed by a validator to ensure compliance with the [Microsoft Commercial Marketplace certification policies](/legal/marketplace/certification-policies). + There's a focus on deep functional and user experience testing, usability checks, and metadata checks. App and agent validation are performed across desktop, web, and mobile clients. We work hard to provide you with a detailed test report in 24 working hours post submission. -* **Guided app publish through concierge service** +* **Guided app and agent publish through concierge service** - If there are no issues observed with your app, then your app is approved and published to the Teams Store. On the other hand, if the issues are present, then you receive an automated validation report from Partner Center with the failure details. To help you successfully publish your app to the Teams Store and guide you through this process, the validation team sends you a personalized email from our concierge service [teamsubm@microsoft.com](mailto:teamsubm@microsoft.com) that includes the following information: + If there are no issues observed with your app and agent, then your app and agent are approved and published to the Teams Store. On the other hand, if the issues are present, then you receive an automated validation report from Partner Center with the failure details. To help you successfully publish your app and agent to the Teams Store and guide you through this process, the validation team sends you a personalized email from our concierge service [teamsubm@microsoft.com](mailto:teamsubm@microsoft.com) that includes the following information: * Summary of all issues * Details of failures or issues with policy links and categorization: - * Must fix: Issues must be fixed prior to app approval. + * Must fix: Issues must be fixed prior to app and agent approval. - * Good-to-fix: Issues can be fixed post app approval as the issues are recommendations to improve your app’s experience. + * Good-to-fix: Issues can be fixed post app and agent approval as the issues are recommendations to improve your app and agent’s experience. - * Blocker: Issues prevent the validation team from testing your app functionality further and must be resolved for validation to continue. + * Blocker: Issues prevent the validation team from testing your app and agent functionality further and must be resolved for validation to continue. - * Query: Queries can be shared to get answers to specific questions related to your app. + * Query: Queries can be shared to get answers to specific questions related to your app and agent. * Steps to recreate issues through written instructions or video format. * Recommendations to fix the reported issues with links to guidance docs. - After you've reviewed the list of issues, fix all the reported issues and share the updated app package over email, for the validation team to revalidate your app thoroughly. If you've any queries related to the reported issues, contact the validation team at [teamsubm@microsoft.com](mailto:teamsubm@microsoft.com). + After you've reviewed the list of issues, fix all the reported issues and share the updated app and agent package over email, for the validation team to revalidate your app and agent thoroughly. If you've any queries related to the reported issues, contact the validation team at [teamsubm@microsoft.com](mailto:teamsubm@microsoft.com). - If there are issues remaining or regression issues observed in your app, the validation team shares an updated validation report with you. If your app had blockers, you might see new issues reported when your app is validated after the blockers are resolved. Sometimes, the validation team has also noticed regression issues in apps post deployment of fixes. It takes a few resubmissions to close all the issues for an app that consists of bugs, and get it approved to publish to the Teams Store. + If there are issues remaining or regression issues observed in your app and agent, the validation team shares an updated validation report with you. If your app and agent had blockers, you might see new issues reported when your app and agent are validated after the blockers are resolved. Sometimes, the validation team has also noticed regression issues in apps and agents post deployment of fixes. It takes a few resubmissions to close all the issues for an app and agent that consists of bugs, and get it approved to publish to the Teams Store. - After all reported issues are closed and final submission is made in the Partner Center, the validation team approves and publish your app. Allow at least one business day for the app to be available in the Teams Store. + After all reported issues are closed and final submission is made in the Partner Center, the validation team approves and publish your app and agent. Allow at least one business day for the app and agent to be available in the Teams Store. -* **Analyze app usage** +* **Analyze app and agent usage** - After your app is approved and published, you can track your app usage in the [Teams app usage report](/office/dev/store/teams-apps-usage) in Partner Center. Metrics include Monthly, Daily, and Weekly active users, and retention and intensity charts enabling you to track churn and frequency of usage. + After your app and agent are approved and published, you can track their usage in the [Teams app usage report](/office/dev/store/teams-apps-usage) in Partner Center. Metrics include Monthly, Daily, and Weekly active users, and retention and intensity charts enabling you to track churn and frequency of usage. - Data for newly published apps takes about a week to appear in the report. + Data for newly published apps and agents takes about a week to appear in the report. -## Tips for rapid approval to publish your app +## Tips for rapid approval to publish your app and agent * **During design phase** - Review the [Teams Store validation guidelines](~/concepts/deploy-and-publish/appsource/prepare/teams-store-validation-guidelines.md) early in your app's life cycle (design phase) to ensure that you build your app in alignment with the Teams Store requirements. If you build your app in line with these guidelines, then it prevents any rework due to non-adherence to Teams Store policies. + Review the [Teams Store validation guidelines](~/concepts/deploy-and-publish/appsource/prepare/teams-store-validation-guidelines.md) early in your app and agent's life cycle (design phase) to ensure that you build your app and agent in alignment with the Teams Store requirements. If you build your app and agent in line with these guidelines, then it prevents any rework due to non-adherence to Teams Store policies. -* **Prior to app submission** +* **Prior to app and agent submission** 1. [Create your Partner Center account](prepare/create-partner-center-dev-account.md) well in advance. If you run into any challenges with your [Partner Center account](prepare/create-partner-center-dev-account.md), create a [support ticket](/azure/marketplace/partner-center-portal/support). - 1. Review the [Teams Store validation guidelines](prepare/teams-store-validation-guidelines.md) again to ensure that your app is in alignment with the Teams Store requirements. Review helps reduce the number of issues observed in your app and so, the time taken to approve your app. + 1. Review the [Teams Store validation guidelines](prepare/teams-store-validation-guidelines.md) again to ensure that your app and agent are in alignment with the Teams Store requirements. Review helps reduce the number of issues observed in your app and agent and so, the time taken to approve your app and agent. - 1. Test and retest your app: + 1. Test and retest your app and agent: - 1. Validate your app package using the Teams [Developer Portal](https://dev.teams.microsoft.com/home) to identify and fix any package errors. + 1. Validate your app and agent package using the Teams [Developer Portal](https://dev.teams.microsoft.com/home) to identify and fix any package errors. - :::image type="content" source="../../../assets/images/submission/teams-validation-developer-portal.png" alt-text="Teams Store app validation in Developer Portal" lightbox="../../../assets/images/submission/teams-validation-developer-portal.png"::: + :::image type="content" source="../../../assets/images/submission/teams-validation-developer-portal.png" alt-text="Teams Store app and agent validation in Developer Portal" lightbox="../../../assets/images/submission/teams-validation-developer-portal.png"::: - 1. Self-test your app thoroughly prior to app submission to ensure it adheres to Teams Store policies. Upload a custom app in Teams and test the end to end user flows for your app. Ensure the functionality works as expected, links aren't broken, user experience isn't blocked, and any limitations are clearly highlighted. + 1. Self-test your app and agent thoroughly prior to submission to ensure it adheres to Teams Store policies. Upload a custom app and agent in Teams and test the end to end user flows for your app and agent. Ensure the functionality works as expected, links aren't broken, user experience isn't blocked, and any limitations are clearly highlighted. - 1. Test your app across desktop, web, and mobile clients. Ensure that the app is responsive across different form factors. + 1. Test your app and agent across desktop, web, and mobile clients. Ensure that the app and agent are responsive across different form factors. - 1. Complete [publisher verification](/azure/active-directory/develop/publisher-verification-overview) before you submit your app. If you run into any issues, you can create a [support ticket](/azure/marketplace/partner-center-portal/support) for resolution. + 1. Complete [publisher verification](/azure/active-directory/develop/publisher-verification-overview) before you submit your app and agent. If you run into any issues, you can create a [support ticket](/azure/marketplace/partner-center-portal/support) for resolution. - 1. As you prepare for app submission, [follow the checklist](/microsoftteams/platform/concepts/deploy-and-publish/appsource/prepare/submission-checklist) and include the following details as part of your submission package: + 1. As you prepare for app and agent submission, [follow the checklist](/microsoftteams/platform/concepts/deploy-and-publish/appsource/prepare/submission-checklist) and include the following details as part of your submission package: - 1. Thoroughly verified app package. + 1. Thoroughly verified app and agent package. - 1. Working admin and non-admin user credentials to test your app functionality (if your app offers a premium subscription model). + 1. Working admin and non-admin user credentials to test your app and agent functionality (if your app and agent offers a premium subscription model). - 1. Test instructions detailing app functionality and supported scenarios. + 1. Test instructions detailing app and agent functionality and supported scenarios. - 1. Set up instructions if your app requires more configuration to access app functionality. Alternately, if your app requires complex configuration, you can also provide a [provisioned demo tenant](/office/developer-program/microsoft-365-developer-program-get-started) with admin access so that our validators can skip the configuration steps. + 1. Set up instructions if your app and agent require more configuration to access functionality. Alternately, if your app and agent require complex configuration, you can also provide a [provisioned demo tenant](/office/developer-program/microsoft-365-developer-program-get-started) with admin access so that our validators can skip the configuration steps. - 1. We recommend you to link a demo video that demonstrates key user flow for your app. + 1. We recommend you to link a demo video that demonstrates key user flow for your app and agent. -* **Post app submission** +* **Post app and agent submission** * After you’ve reviewed the validation report, reply to the email thread with any queries related to the validation report, or if you need any extra support to resolve the reported issues. - * Ensure that you've adequate developer bandwidth to resolve any reported issues until the app is approved. + * Ensure that you've adequate developer bandwidth to resolve any reported issues until the app and agent are approved. - * Ensure that you've [resolved all issues](/microsoftteams/platform/concepts/deploy-and-publish/appsource/resolve-submission-issues) reported to you by the concierge service [teamsubm@microsoft.com](mailto:teamsubm@microsoft.com) before sharing your app package for further testing. It helps reduce the number of iterations required to validate your app and so, the time taken to approve your app. + * Ensure that you've [resolved all issues](/microsoftteams/platform/concepts/deploy-and-publish/appsource/resolve-submission-issues) reported to you by the concierge service [teamsubm@microsoft.com](mailto:teamsubm@microsoft.com) before sharing your app and agent package for further testing. It helps reduce the number of iterations required to validate your app and agent and so, the time taken to approve your app and agent. - * Avoid changing app functionality during the validation process that might lead to discovery of new issues and increase the time it takes to approve your app. + * Avoid changing app and agent functionality during the validation process that might lead to discovery of new issues and increase the time it takes to approve your app and agent. -## Additional tips for rapid approval to publish your app linked to a SaaS offer +## Additional tips for rapid approval to publish your app and agent linked to a SaaS offer * **During design phase** - Review the [Teams Store validation guidelines specific to apps published with linked SaaS offers](~/concepts/deploy-and-publish/appsource/prepare/teams-store-validation-guidelines.md#apps-linked-to-saas-offer) early in your app's life cycle (design phase) to ensure that you build your app in alignment with the Teams Store requirements and [Microsoft Commercial Marketplace policies applicable to Teams apps linked to SaaS offers](/legal/marketplace/certification-policies#11405-teams-app-linked-to-software-as-a-service-saas-offers). If you build your app in line with these guidelines, then it prevents any rework due to nonadherence to Teams Store policies. + Review the [Teams Store validation guidelines specific to apps and agents published with linked SaaS offers](~/concepts/deploy-and-publish/appsource/prepare/teams-store-validation-guidelines.md#apps-linked-to-saas-offer) early in your app and agent's life cycle (design phase) to ensure that you build your app and agent in alignment with the Teams Store requirements and [Microsoft Commercial Marketplace policies applicable to Teams apps and agents linked to SaaS offers](/legal/marketplace/certification-policies#11405-teams-app-linked-to-software-as-a-service-saas-offers). If you build your app and agent in line with these guidelines, then it prevents any rework due to nonadherence to Teams Store policies. -* **Prior to app submission** +* **Prior to app and agent submission** - 1. As you prepare for app submission, ensure the following details: + 1. As you prepare for app and agent submission, ensure the following details: - 1. Your app is linked to a live (already published) SaaS offer on AppSource with at least one plan with pricing information. + 1. Your app and agent are linked to a live (already published) SaaS offer on AppSource with at least one plan with pricing information. 1. You've correctly mentioned the `subscriptionOffer` details in your [app manifest](../../../resources/schema/manifest-schema.md#subscriptionoffer) (previously called Teams app manifest) in the format `publisherId.offerId`. 1. You must ensure your linked SaaS offer is designed to support licenses assigned on a [SaaS pricing model](/azure/marketplace/create-new-saas-offer-plans). - 1. Include test instructions or setup instructions or link to a demo video detailing app functionality and supported scenarios and any additional information to enable our testers to easily understand your SaaS portal workflows. + 1. Include test instructions or setup instructions or link to a demo video detailing app and agent functionality and supported scenarios and any additional information to enable our testers to easily understand your SaaS portal workflows. - 1. You must thoroughly [self-test](~/concepts/deploy-and-publish/appsource/prepare/test-preview-for-monetized-apps.md) the end to end purchase and license management workflows before you submit your app linked to a SaaS offer for validation, ensure the following details: + 1. You must thoroughly [self-test](~/concepts/deploy-and-publish/appsource/prepare/test-preview-for-monetized-apps.md) the end to end purchase and license management workflows before you submit your app and agent linked to a SaaS offer for validation, ensure the following details: 1. Both admin and non-admin users can place an order and confirm the purchase of your subscription. Purchasers can navigate to the SaaS application landing page by selecting **Setup Now** in the Microsoft Admin Center. Test and ensure that your purchasers can activate and configure their subscription on your SaaS application. Messaging on your SaaS application should provide enough and clear information on the way forward to a purchaser. @@ -163,15 +157,15 @@ If your app is production ready, you can begin the process of getting it listed ## Teams Store search experience -After an app is published to the Teams Store, users can find apps by going to the **Apps** icon from the left pane in Teams. Users can use the search box in the upper left corner or browse by category to see if a particular app or program has a version for Teams. +After an app and agent are published to the Teams Store, users can find them by going to the **Apps** icon from the left pane in Teams. Users can use the search box in the upper left corner or browse by category to see if a particular app and agent or program has a version for Teams. -Teams provides intelligent search experience by matching the user input to the fields provided by the developer across appName, publisher name, short description, long description, specific keywords and category names in app manifest or Partner Center. The search results display apps that are closest match to the user's specified characters. +Teams provides intelligent search experience by matching the user input to the fields provided by the developer across appName, publisher name, short description, long description, specific keywords and category names in app manifest or Partner Center. The search results display apps and agents that are closest match to the user's specified characters. ## Training module | **Training name** | **Description** | |--- | --- | -| [Publish Teams apps in Microsoft Teams Store](/training/modules/microsoft-teams-publish-app-to-store/) | This training module is about publishing your app to Teams Store. It focuses primarily on app validation process. | +| [Publish Teams apps and agents in Microsoft Teams Store](/training/modules/microsoft-teams-publish-app-to-store/) | This training module is about publishing your app and agent to Teams Store. It focuses primarily on app and agent validation process. | ## See also