Publish your app to the Microsoft Teams store
You can distribute your app directly to the store inside Microsoft Teams and reach millions of users around the world. If your app is also featured in the store, you can instantly reach potential customers.
Apps published to the Teams store also automatically list on Microsoft AppSource, which is the official marketplace for Microsoft 365 apps and solutions.
Understand the publishing process
When you feel your app is production ready, you can begin the process of getting it listed on the Teams store.
Following the pre-submission steps closely can increase the possibility that Microsoft approves your app for publishing.
Review the Teams store validation guidelines to ensure your app meets Teams app and store standards.
Prepare your store submission, which includes running automated tests, compiling test notes, creating a store listing, among other important tasks to help expedite the review process.
Submit your app through Partner Center.
If your submission fails, work with Microsoft directly to resolve the issues and resubmit your app.
What to expect after you submit your app?
Deep functional and experience tests
Your app is thoroughly reviewed by a validator to ensure compliance with the Microsoft Commercial Marketplace certification policies with 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 a detailed test report in 24 working hours post submission.
Guided app publish through concierge service
If there are no issues observed with your app, your app will be approved and published to the Teams store. If there are issues, you'll 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 will send you a personalized email from our concierge service email@example.com that includes the following information:
Summary of all issues
Details of failures or issues with policy links and categorization:
Mandatory fix: These issues must be fixed prior to app approval.
Suggested fix: These issues can be fixed post app approval as these are recommendations to improve your app’s experience.
Blocker: These issues prevent the validation team from testing your app functionality further and must be resolved for validation to continue.
Query: These queries can be shared to get answers to specific questions related to your app.
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 re-validate your app thoroughly. If you've any queries related to the reported issues, contact the validation team at firstname.lastname@example.org.
If there are issues remaining or regression issues observed in your app, the validation team will share 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 re-submissions to close all the issues for an app 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 will approve and publish your app. Allow at least one business day for the app to be available in the Teams store.
Analyze app usage
After your app is approved and published, you can track your app usage in the Teams app usage report 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.
Tips for rapid approval to publish your app
During design phase
Review the store validation guidelines early in your app's life cycle (design phase) to ensure that you build your app in alignment with the store requirements. If you build your app in line with these guidelines, this will prevent any rework due to non-adherence to store policies.
Prior to app submission
Review the store validation guidelines again to ensure that your app is in alignment with the store requirements. This helps reduce the number of issues observed in your app and consequently, the time taken to approve your app.
Test and re-test your app:
Validate your app package using the Teams Developer Portal to identify and fix any package errors.
Self-test your app thoroughly prior to app submission to ensure it adheres with store policies. Sideload the 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.
Test your app across desktop, web, and mobile clients. Ensure that the app is responsive across different form factors.
As you prepare for app submission, follow the checklist and include the following details as part of your submission package:
Thoroughly verified app package.
Working admin and non-admin user credentials to test your app functionality (if your app offers a premium subscription model).
Test instructions detailing app functionality and supported scenarios.
Setup instructions if your app requires additional configuration to access app functionality. Alternately, if your app requires complex configuration, you can also provide a provisioned demo tenant with admin access so that our validators can skip the configuration steps.
Link to a demo video recording key user flow for your app. This is highly recommended.
Post app 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 additional support to resolve the reported issues.
Ensure that you've adequate developer bandwidth to resolve any reported issues till the app is approved.
Ensure that you've resolved all issues reported to you by the concierge service email@example.com before sharing your app package for further testing. This helps reduce the number of iterations required to validate your app and consequently, the time taken to approve your app.
Avoid changing app functionality during the validation process. This might lead to discovery of new issues and increase the time it takes to approve your app.
Additional tips for rapid approval to publish your app linked to a SaaS offer
During design phase
Review the store validation guidelines specific to apps published with linked SaaS offers early in your app's life cycle (design phase) to ensure that you build your app in alignment with the store requirements and Microsoft Commercial Marketplace policies applicable to Teams apps linked to SaaS offers. If you build your app in line with these guidelines, this will prevent any rework due to non-adherence to store policies.
Prior to app submission
As you prepare for app submission, ensure the following:
Your app is linked to a live (already published) SaaS offer on AppSource with at least one plan with pricing information.
You have correctly mentioned the
subscriptionOfferdetails in your app manifest in the format
You must ensure your linked SaaS offer is designed to support licenses assigned on a named per user model. Linked SaaS offers that support other pricing models such as flat rate are currently not accepted for publishing to the Teams store.
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.
You must thoroughly self-test the end to end purchase and license management workflows before you submit your app linked to a SaaS offer for validation, ensure the following:
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.
The Manage Subscriptions section in Microsoft Admin Center shows the correct details of the subscriptions brought by your test users. Subscription status, number of licenses, and other details must be accurate.
Buying and removal of license workflows are working as expected. Ensure purchasers can increase the number of licenses from Microsoft Admin Center. Ensure license count and assignment on your SaaS application reflects respective licenses and the right assignees. Also, ensure your SaaS application provides a way to take away a license from an user. Post removal of a license, ensure remaining assignments and count remain intact on your SaaS application and the correct details are reflected in the Microsoft Admin Center.
Subscription cancellation is working as expected. Purchasers can cancel a subscription. Post cancellation, check if the correct subscription status is reflected in the Microsoft Admin Center and your SaaS application. Verify that the purchaser has lost access to the subscription after successful cancellation.
Re-purchasing a subscription is seamless. After cancellation of an active subscription, thoroughly test to ensure purchasers can repurchase the subscription.
Purchasers can change their subscribed plan. After the plan is modified, users can access the upgraded or downgraded plan features.
Your SaaS application contains license management features. Purchasers must be able to assign, modify, and re-assign available licenses to users. Check if purchasers can add or remove users to manage the licenses.
You must test and ensure both minimum and bulk license purchase flows are working as expected.
You must ensure users who are assigned licenses have access to the accurate purchased plan features described in your plan’s listing.
Submit and view feedback for