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.
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.
You can also validate your app using Developer Portal for Teams.
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
Depending on your app functionality, you're required to provide Teams tenant configurations, a set of test accounts, and test notes. Ensure that you meet all requirements listed in this section to avoid app testability failures and delay in the app publishing process.
Tenant configurations: You must configure a Teams tenant to test your app and provide test accounts. This section shares the details for configuring a tenant for your app's testing. For more information about creating a demo tenant, see Prepare your Microsoft 365 tenant. Ensure your app is configured for this demo tenant. If applicable, safe-listing or connection to external services for this tenant should be done before submission of the app.
Test Accounts: Depending on your app's features, you need to provide the following accounts:
Admin account (required)
Non-admin accounts (required)
- Ensure that test accounts are safe-listed or configured with license keys, if applicable.
- If your app requires users to log in or connect to external services, provide the required credentials to complete the login or connection with the external service.
- Ensure that phone-based 2-way authentication is disabled for test accounts.
- If the app provides a collaborative experience, provide a non-admin account for each user persona. For example, if your app is used by teachers and students, provide credentials for both user personas.
- Ensure that at least one account has access to premium or upgraded features, if applicable.
- All accounts you provide must include pre-populated data to help in testing. For example, if your app helps to provide market insights based on the user profile, ensure that market data is pre-populated along with a few user profiles.
- Provide at least one account that isn't pre-configured to test the first-run sign-in experience properly.
These accounts must be utilized only for validation requirements. The validation team will test your app fully, including first-run user experience. If your app is free for all users and anyone who intends to use your app can sign up to use it, indicate the same in the test notes. The validation team will use the sign up process as described.
Test Notes: The notes provide details about your app's capabilities in Teams and the steps for testing each one. It helps the validation team to understand your app better and complete the testing for all functionalities in your app. If your app functionality includes event-based notifications, list the instructions to trigger these events. For time-based notifications, indicate the expected time for receiving these notifications.
The functional testing of the app is initiated based on the test notes you provide. However, the validation team won't restrict the testing only to the test instructions.
Demo Video: Provide a recording of your app so that Microsoft can fully understand its functionality.
You can find the following sample test instructions for your reference.
- Sample 1: Educational app
- Sample 2: ERP Data transfer
- Sample 3: Collaborative app
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. You can categorize your app based on the following categories:
|Images and video galleries|
|Files and documents|
|Workflow and business management|
|Human resources and recruiting|
|Meetings and scheduling|
|Data visualization and BI|
|Training and tutorial|
|News and weather|
|Sales and marketing|
|Look and feel|
|Customer and contact management (CRM)|
|Maps and feeds|
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.