Prepare your Teams store submission
You've designed, built, and tested your Microsoft Teams app. Now you're ready to list it so people can discover and start using your app.
See the following video to learn more about publishing your app to the Microsoft Teams app store:
Before you submit your app to Partner Center, ensure you've done the following.
Validate your app package
While your app may be working in a test environment, you should check your app package to avoid running into issues during the submission process.
If you have been using App Studio, we recommend that you'd try the Developer Portal to configure, distribute, and manage your Teams apps. App Studio will be deprecated by June 30, 2022.
The Microsoft Teams app validation tool helps you identify and fix issues before submitting to Partner Center. The tool automatically checks your app's configurations against the same test cases used during store validation.
- Go to the Microsoft Teams app validation tool. (Note: The tool is also available in App Studio.)
- Upload your app package to run the automated tests.
- Go to the Preliminary checklist and review the test cases that are difficult to automate.
- Fix issues with your configurations or app in general. These issues occur if the automated tests give you errors or you haven't met all the criteria in the checklist.
Compile testing instructions
Provide instructions and resources to help the reviewers test your app, including:
- Test accounts
- License keys
You can add instructions in Partner Center or upload them to a publicly available location on SharePoint.
Provide details about your app's capabilities in Teams and steps for testing each one.
Provide test accounts if your app requires a license or backend safe listing. All accounts you provide must include pre-populated data to help in testing.
Depending on your app's features, you may need to provide all the following accounts:
- Admin account (required)
- Non-admin account (required)
- An account that isn't pre-configured to properly test the first-run sign-in experience (required)
- An account with access to premium or upgraded features (if applicable)
- Two accounts in the same tenant to test the collaboration experience for apps that work in shared contexts (if applicable)
If you must configure a Teams tenant to use your app, include those instructions and admin and non-admin accounts for validation.
Provide a recording of your app so that Microsoft can fully understand its functionality.
Create your store listing details
The information that you submit to Partner Center—including your name, descriptions, icons, and images—becomes the Teams store and Microsoft AppSource listing for your app.
A store listing may be someone's first impression of your app. Increase installations with a listing that effectively conveys your app's benefits, functionality, and brand.
Specify a short name
Your app's name (specifically, its short name) plays a crucial role in how users discover it in the store.
Make sure your short name adheres to the store validation guidelines.
You must have a short and long description of your app.
A concise summary of your app that should be original, engaging, and directed at your target audience. Keep the short description to one sentence.
Make sure your short description adheres to the store validation guidelines.
The long description can provide a narrative that highlights your apps':
- Main features
- The problems it solves
- Target audience
While this description can be as long as 4,000 characters, most users will only read between 300-500 words.
Make sure your long description adheres to the store validation guidelines.
Adhere to icon design guidelines
Icons are one of the main elements users see when browsing the store. Your icons should communicate your app's brand and purpose while also adhering to Teams requirements.
For more information, see guidance on creating Teams app icons.
Screenshots provide a prominent visual preview of your app to complement your app name, icon, and descriptions.
Remember the following best practices about screenshots:
- You can have up to five screenshots per listing.
- Supported file types include .png, .jpeg, and gif image formats.
- Dimensions should be 1366 x 768 pixels.
- Maximum size of 1,024 KB.
For best practices, see the following resources:
Create a video
A video in your listing can be the most effective way to communicate why people should use your app. Address the following questions in a video:
- Who is your app for?
- What problems can your app solve?
- How does your app work?
- What other benefits do you get from using your app?
You can add a URL for your YouTube or Vimeo video.
Best practices for videos
- Keep your video between 60-90 seconds.
- Aim for quality. In a listing, users will see your video before screenshots.
- Communicate the value of the product in narrative form.
- Demonstrate how the product works.
Select a category for your app
During submission, you're asked to categorize your app. The following table maps Teams Store categories to the categories listed in Partner Center.
|Teams categories||Partner Center categories|
|Analytics and BI||Analytics, Data Visualization, and BI|
|Developer and IT||Developer Tools, IT Admin|
|Human resources||Human Resources and Recruiting|
|Productivity||Content Management, Files and documents, Productivity, Training and Tutorials, and Utilities|
|Project management||Communication, Project Management, Workflow, and Business Management|
|Sales and support||Customer and Contact Management, Customer Support, Financial Management, and Sales and Marketing|
|Social and fun||Image and Video Galleries, Lifestyle, News and Weather, Social, Travel, and Navigation|
Localize your store listing
Complete Publisher Verification
Publisher Verification is required for Teams apps listed in the store. For more information, see frequently asked questions, how to mark your app as publisher verified, and troubleshoot publisher verification.
Complete Publisher Attestation
Publisher Attestation is also required for Teams apps listed in the Store. The process includes completing a self-assessment of your app's security, data handling, and compliance practices. The process can help potential customers make informed decisions about using your app.
If you're submitting a new app, you can't officially complete Publisher Attestation until your app is listed on the Teams store. If you're updating a listed app, complete Publisher Attestation before you submit the latest version of the app for validation.
Submit and view feedback for