Prepare for AppSource submission

To be listed on AppSource, your app must go through an approval process. This is a free service provided by the Microsoft Teams group that verifies that your app works as described, contains all appropriate metadata, and provides content that would be valuable to an end user. To help you achieve rapid approval, ensure your app meets the following requirements and guidelines:

Once you have completed all of the above requirements, submit your package to AppSource through Partner Center.

Teams App Validation Tool

The app validation tool consists of an app validator and a preliminary checklist. The tool replicates the same test cases used by AppSource to evaluate your app submission. Therefore, it's crucial to pass all the test cases prior to submitting your solution to AppSource for approval.The tool can be found in several areas within the Teams platform:

Teams app validator

The Validate page allows you to check your app package before submission to AppSource. Simply upload your app package and the validation tool will check your app against all manifest-related test cases. For each failed test, the description provides a documentation link to help you fix the error.

Validation tool

Preliminary checklist

For test scenarios that are difficult to automate, the preliminary checklist surfaces seven of the most commonly failed test cases.

Preliminary checklist

Privacy policy, terms of use and support URLs

Privacy policy

Privacy policy guidelines:

  • The privacy policy can be specific to your app and/or an overall policy for all of your services.
  • If you use a generic privacy policy, it must reference "services", "applications", and "platforms" to include your Teams app as well as your website.
  • It must include how you handle user data storage, user data retention, deletion, and security controls.
  • It must include your contact information.
  • It should not contain broken links, beta URLs, or staging URLs.

Terms of use

Your terms of use statement should be specific and applicable to your app and/or add-in offering.

Support URLs

Your support URLs should not require authentication or login credential to contact you for any issues with your app.

Test notes for validation

Please include the following:

  • You must provide at least two login credentials, one admin and one non-admin.

  • For verification purposes, the accounts you provide should have sufficient pre-populated data.

  • For enterprise apps, apps where a subscription is required, or apps where there is an Office 365 tenant/domain dependency, you must provide a third account in the same domain that is not pre-configured for your app so that we can validate the first-run user experience.

  • If your app has premium/upgraded features, an account with the necessary access must be provided to test that experience.

  • You may choose to upload your test notes to SharePoint. If so, please provide a public link to the file.

  • Test Accounts. A test account is required if your app only allows licensed accounts or whitelisting from the backend. Also, if there is a team/group chat scope allowed in your app, two test accounts in the same tenant are required to validate the team collaboration scenario.

  • Integration steps. If pre-configuration by a tenant admin is required to use the app, include the steps and/or provide configured admin and non-admin accounts for validation. Note: you can sign up for an Office 365 Developer Program subscription. It's free for 90 days and will continually renew as long as you're using it for development activity.

  • Notes regarding the app features in Teams: Detail all of the capabilities the app offers within Teams and steps for testing each feature.

  • Video showing the app functionality (Optional): You can provide a video recording of the product for us to fully understand the functionality of the app.