Common app review failures
This section covers the most frequent failures that Microsoft finds during Teams app reviews.
Important
Microsoft extensively tests apps submitted for the Microsoft Teams Store for bugs and Microsoft Commercial Marketplace policy violations. Most apps fail the Teams Store app review initially. Apps are only approved for publishing on the Teams Store once it is found to be fully compliant to Microsoft’s Commercial Marketplace Certification policies and bug free. This section aims to equip you with an understanding of the most common reasons that apps fail the initial app review so that you can take care of these issues during app development itself and increase the likelihood of your app passing app review.
App description
A great description can make your app stand out in the Teams Store and help encourage customers to download it. You must avoid the following mistakes in your app description:
| # | Avoid the following |
|---|---|
|
Way forward information for new users such as, Sign Up or Get Started, or Help and Contact Us links aren't included in the manifest and AppSource full description. |
|
|
Region specific app name or functionality isn't called out in manifest and Partner Center app descriptions. |
|
|
Limitations or account dependency on external accounts or services to complete Sign-In, Sign-Out, and Sign-Up experience aren't called out in app manifest and long description. |
Violation of Microsoft trademark and brand guidelines
When referring to Microsoft trademarks, products names, and services, you must follow Microsoft Trademark and Brand Guidelines. You must avoid the following common violations that lead to a rejection during app review:
| # | Avoid the following |
|---|---|
|
|
Abbreviating Microsoft as MS or MSFT in the app listing, referencing the first instance of Microsoft Teams in the offer listing as Teams instead of Microsoft Teams. |
|
|
Using Microsoft brand assets in the offer content without an express license from Microsoft. |
|
|
Creating an app listing (including the offer description, title, icon, screenshots, and videos) that impersonates or provides an impression that it's an official Microsoft app for the Teams Store. |
Testability
Detailed test instructions and credentials help you with a successful and fast review of your app.
Ensure that you provide all the details required to review your app in the Notes for Certification Information section of Partner Center, valid demo credentials for features that require sign in and instructions to set any special configuration, a demo video or hardware for features that require an environment that is hard to replicate and complete.
Microsoft 365 App Compliance Program
The Microsoft 365 App Compliance Program helps organizations assess and manage risk by evaluating security and compliance information about an app. You must complete Publisher Verification before you submit your app for review to publish on the Teams Store.
App name
You must avoid the following violations in your app's name that result in rejection during app review:
| # | Avoid the following |
|---|---|
|
|
Inconsistent usage of app name throughout the app. |
|
|
App names appended with Beta, Dev, and Prod to indicate app isn't production ready. |
Support link
Support links must not ask users for authentication and must lead directly to appropriate support information. You must ensure that your app includes a valid support link for users to contact.
Manifest schema
The Teams app manifest describes how the app integrates into the Microsoft Teams product. Your app manifest must conform to a publicly released manifest schema. If your app supports localization, ensure that you use a localization manifest schema version 1.5 or later.
App UI
Your app’s UI must not look incomplete and should be intuitive to use. Apps that have truncated or overlapping content and apps that display broken images fail app review.
Valid domains
Your app submission must adhere to the external domains guidelines under Microsoft’s Commercial Marketplace Certification Policy. For your app to pass review, ensure that the valid domains listed in the app manifest are under your organization's direct control. If you're declaring any domain under the messageHandler link unfurling section of the manifest, you must ensure that the domain listed is under your organization’s direct control.
Privacy policy
Your app listing must include a valid privacy policy link. Apps with invalid, unsecured, and broken privacy policy links fail app review. Your privacy policy must follow the privacy policy guidelines.
Terms of use
Your app listing must include a valid Terms of use link. Apps with invalid, unsecured, and broken Terms of use links fail app review. You must follow the Terms of use guidelines.
Bots
If your app includes a bot, you must declare at least one supported bot command in the commandList section of the manifest. Bots must provide value in their installed scope. Bots must respond to supported user commands across all installed scopes. For apps with a complex configuration experience, bots must provide a welcome message that meets the Teams Bot Welcome Message design guideline. Bots must respond to generic commands and fail gracefully.