|Service||Microsoft Docs article||Related commit history on GitHub||Change details|
|platform||Add Default Install Scope||https://github.com/MicrosoftDocs/msteams-docs/commits/master/msteams-platform/concepts/deploy-and-publish/add-default-install-scope.md||
-# Add a default install scope and group capability
+# Configure default install options for your Microsoft Teams appItΓÇÖs common for an app to support multiple scenarios in Teams, but you may have designed it with a specific scope and capability in mind. For example, if your app is primarily for team or channel use, you can make sure that the first install option users see in the store is **Add to a team**.
-![Add an app](../../assets/images/compose-extensions/addanapp.png)
+ :::column span="2":::+
+![Add an app dropdown example](../../assets/images/compose-extensions/addanapp.png)+
+ :::column span="2":::
+ :::column-end:::If your app's primary capability is a bot, you can also make the bot the default capability when a user installs your app to a team.
Configure the default capability when your app is installed for a team, meeting,## Next step > [!div class="nextstepaction"]
-> [Choose how to distribute your app](overview.md)
+> [Create your app package](~/concepts/build-and-test/apps-package.md)
|platform||Apps Publish Overview||https://github.com/MicrosoftDocs/msteams-docs/commits/master/msteams-platform/concepts/deploy-and-publish/apps-publish-overview.md||
For more information, see [publish to the Teams store](~/concepts/deploy-and-pub## Next step > [!div class="nextstepaction"]
-> [Create your app package](~/concepts/build-and-test/apps-package.md)
+> [Configure app's default install options](~/concepts/deploy-and-publish/add-default-install-scope.md)
|platform||Application Certification||https://github.com/MicrosoftDocs/msteams-docs/commits/master/msteams-platform/concepts/deploy-and-publish/appsource/post-publish/application-certification.md|| - Title: Microsoft 365 App Certification
-description: Describes the Microsoft 365 App Compliance program from store apps-
-keywords: teams compliance appsource store app certification partner centerPreviously updated : 05/06/2019--
-# Microsoft 365 App Compliance-
-Building a secure and trustworthy app ecosystem is a top priority for Microsoft. Several investments aim to ensure that apps available in the Microsoft store are valid, safe and secure.-
- ![3 Tier Approach to App Compliance](../../../../assets/images/Three_Tiers.png)--- [Publisher Verification](https://docs.microsoft.com/azure/active-directory/develop/publisher-verification-overview) ΓÇô ΓÇ»allows developers with a verified [Microsoft Partner Network](https://partner.microsoft.com/membership) (MPN) account to associate an organizational identity with their apps registered through the [Microsoft identity platform](https://docs.microsoft.com/azure/active-directory/develop/).-- [Publisher Attestation](https://docs.microsoft.com/microsoft-365-app-certification/docs/enterprise-app-attestation-guide) ΓÇô developers complete a self-assessment of their organizationΓÇÖs security, compliance, and data handling practices. This information is made available for IT Admins to review. -- [M365 Certification](https://docs.microsoft.com/microsoft-365-app-certification/docs/enterprise-app-certification-guide) ΓÇô Microsoft employs a third-party assessor to review and validate the security and compliance standards for the organization. This is our highest level of certification and it gives assurance IT Admins that the application and organization that receives it operates in ways that promote safe usage and storage of data.--
-## Program benefits-
-Each tier in the Microsoft 365 App Compliance Program gives a different level of assurance to your customers. By completing the Publisher Verification you are assuring your customers that your company is the publisher of your app. The Publisher Attestation reduces the need to go back and forth with your customers about your appΓÇÖs security practices. We publish your responses to common questions about security and compliance in one location in a consistent format for customers to review. The final tier is the Microsoft 365 Certification. Upon completion your customers will know that you follow secure data handling and security practices. Other benefits of the compliance program include:-- Free ΓÇô Microsoft is currently covering this cost-- Earn a badge in AppSource and on [Compliance Dev Docs](https://docs.microsoft.com/microsoft-365-app-certification/teams/teams-apps)-- Differentiation from other apps in the store-- Reduced time to app adoption for your customers-- Reduce the amount of time you spend filling out RFPs-- Added confidence in the security and compliance measures of your application-
-## Qualifying application types
-### Publisher Verification applies to apps which:-- Using [OAuth 2.0 and OpenID Connect](https://docs.microsoft.com/azure/active-directory/develop/active-directory-v2-protocols) to sign users in and request access to data using service-side APIs such as [Microsoft Graph](https://developer.microsoft.com/graph/). -- Registered in Azure AD as multi-tenant. -
-### Publisher Attestation-- Teams-- Word-- Excel-- PowerPoint-- Outlook-- Coming Soon: SharePoint-
-### Microsoft 365 Certification-- Teams-- Coming soon: will offer same application type coverage as Publisher Attestation-
-## How to start the program-
-Completing the Microsoft 365 App Compliance Program is voluntary, but highly encouraged. You can join the program no matter where if you are a newly added application or if youΓÇÖve been in the store for years.-
-The first step is to complete the [Publisher Verification](https://docs.microsoft.com/azure/active-directory/develop/publisher-verification-overview). The next step is to complete the [Publisher Attestation](https://docs.microsoft.com/microsoft-365-app-certification/docs/attestation). Once you complete the Publisher Attestation, we will reach out to you with the next steps to begin the Microsoft 365 Certification.
|platform||Detail Page Checklist||https://github.com/MicrosoftDocs/msteams-docs/commits/master/msteams-platform/concepts/deploy-and-publish/appsource/prepare/detail-page-checklist.md|| - Title: Create a store listing for your app
-description: Describes how to create a store listing for your Microsoft Teams app.-
-# Create a store listing for your Microsoft Teams app-
-The information that you submit to [Partner Center](https://partner.microsoft.com)—including your name, descriptions, icons, and images—becomes the Microsoft Teams store and Microsoft AppSource listing for your app.-
-A store listing may be someone's first impression of your app. Increase your 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*](~/resources/schem#name)) plays a crucial role in how users discover it in the store.-
-The following example highlights where an app's short name displays in a store listing.--
-### Best practices for names-
-* Choose a simple, memorable name that hints at what your app does.
-* Be distinctive.
-* Avoid typos and grammatical errors.-
-* Use profane or derogatory terms.
-* Use racially or culturally insensitive language.
-* Use generic terms or names similar to existing apps.
-* Include "Teams", "Microsoft", existing/upcoming Microsoft product names, or "app" in the name.-
-> If your app is part of an official partnership with Microsoft, the name of your app must come first (for example, *Salesforce Connector for Microsoft Teams*).-
-## Write descriptions-
-You need a short and long description of your app.-
-### Short description-
-A concise summary of your app that should be original, engaging, and directed at your target audience. Ideally, keep the short description to one sentence.-
-The following example highlights where an app's short description displays in a store listing:--
-#### Best practices for short descriptions-
-* Put the most important information first.
-* Include keywords that customers are likely to search for.-
-* Repeat your app name.
-* Rely on jargon or specialized terminology. (You can't assume users know what to look for.)-
-### Long description-
-The long description can provide an engaging narrative that highlights your app's main features, the problems it solves, and its target audience. While this description can be as long as 4000 characters, most users will only read between 300-500 words.-
-The following example highlights where an app's long description displays in a store listing:--
-#### Usage examples-
-The following phrases are examples of what's allowed when writing long descriptions:-
-* "<*Your app name*> works with Microsoft Teams"
-* "... a <*type of app*> for Microsoft Teams"
-* "<*Your app name*> integrates with Microsoft Teams"
-* "... integrated with Microsoft Teams"
-* "... for users working with Microsoft Teams"
-* "... for <*specific task*> within Microsoft Teams"
-* "... built on ..."
-* "... runs on ..."
-* "... enabled by ..."
-* "... developed for ..."
-* "... designed for ..."-
-#### Best practices for long descriptions-
-* Use [Markdown](https://support.office.com/article/use-markdown-formatting-in-teams-4d10bd65-55e2-4b2d-a1f3-2bebdcd2c772) to format your description.
-* List features with bullet points so it's easier to scan the description.
-* Use active voice and speak to users directly (for example, *You can ...*).
-* Include a help or support link.
-* Identify the following if applicable: limitations, set up information, account dependencies, and release updates.-
-* Exceed 500 words.
-* Include too many keywords. (It's distracting and won't help people find your app.)
-* Use the following language unless the app has gone through an official certification process:
- * "... certified for ..."
- * " ... powered by ..."-
-### Best practices for all descriptions-
-* Reference Microsoft product names only when necessary. For more information on the guidelines, see [Microsoft Trademark and Brand Guidelines](https://www.microsoft.com/en-us/legal/intellectualproperty/trademarks/usage/general).
-* If you need to reference **Teams**, write the first reference as **Microsoft Teams**. Subsequent references can be shortened to **Teams**.
-* Refer to **Microsoft 365** instead of **Office 365**.
-* Avoid typos and grammatical errors.
-* Avoid unnecessary capitalizations (for example, **Users** instead of **users**).
-* Avoid acronyms.-
-* Abbreviate Microsoft as **MS** or **MSFT**.
-* Indicate the app is an offering from Microsoft, including using Microsoft slogans or taglines.
-* Use copyrighted brand names you don't own.-
-## 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 purpose while also adhering to Teams requirements.-
-For more information, see [specific guidance on designing Teams app icons](~/concepts/build-and-test/apps-package.md#app-icons).-
-## Capture screenshots-
-Screenshots provide a prominent visual preview of your app to complement your app name, icon, and descriptions.-
-### Requirements for screenshots-
-* Up to five screenshots per listing.
-* Supported file types include PNG, JPEG, and GIF.
-* Dimensions should be 1366x768 pixels.
-* Maximum size of 1,024 KB.-
-### Best practices for screenshots-
-* Focus on your app's capabilities (for example, how people can communicate with your bot).
-* Include content that accurately represents your app.
-* Use text judiciously.
-* Frame screenshots with a color that reflects your brand and include marketing content, similar to the following [Freshdesk](https://appsource.microsoft.com/product/office/WA104381505?src=office&tab=Overview) example (dimension requirements apply to the whole image and not just the screenshot):
- :::image type="content" source="../../../../assets/images/freshdesk.png" alt-text="Screenshot example of third-party app Freshdesk":::-
-* Show specific devices, such as phones or laptops.
-* Display chrome or UI that isn't in your app.
-* Capture any Teams or browser UI in your screenshots.
-* Include mockups that inaccurately reflect your app's actual UI, such as showing your app in a browser instead of a Teams tab.-
-For more best practices, see [craft effective images for Microsoft app stores](/office/dev/store/craft-effective-appsource-store-images).-
-## Create a video-
-A video can be the most effective way to communicate why people should use your app. You should 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?-
-If you include a video, it appears before your screenshots in the listing.-
-### Best practices for videos-
-* Keep your video between 30-90 seconds.
-* Aim for quality. In a listing, users will see your video before screenshots.-
-## Localize your store listing-
-Partner Center supports [localized store listings](https://docs.microsoft.com/office/dev/store/prepare-localized-solutions). For more information, see [how to localize your Teams app listing](../../../../concepts/build-and-test/apps-localization.md).-
-## See also-
-* [Create effective Microsoft 365 Stores listings](/office/dev/store/create-effective-office-store-listings)
-* Teams app design guidelines for [copy and content](~/concepts/design/design-teams-app-fundamentals.md#copy-and-content) and [brand expression](~/concepts/design/design-teams-app-fundamentals.md#brand-expression)
-* [Microsoft Trademark and Brand Guidelines](https://www.microsoft.com/en-us/legal/intellectualproperty/trademarks/usage/general)-
-## Next step-
-> [!div class="nextstepaction"]
-> [Prepare your store submission](~/concepts/deploy-and-publish/appsource/prepare/submission-checklist.md)
Partner Center supports [localized store listings](https://docs.microsoft.com/of## Complete Publisher Verification
-[Publisher Verification](/azure/active-directory/develop/publisher-verification-overview) is required for Teams apps listed in the store.For more information, see [frequently asked questions](/azure/active-directory/develop/publisher-verification-overview#frequently-asked-questions), [how to mark your app as publisher verified](/azure/active-directory/develop/mark-app-as-publisher-verified), and [troubleshoot publisher verification](/azure/active-directory/develop/troubleshoot-publisher-verification).
+[Publisher Verification](/azure/active-directory/develop/publisher-verification-overview) is required for Teams apps listed in the store. For more information, see [frequently asked questions](/azure/active-directory/develop/publisher-verification-overview#frequently-asked-questions), [how to mark your app as publisher verified](/azure/active-directory/develop/mark-app-as-publisher-verified), and [troubleshoot publisher verification](/azure/active-directory/develop/troubleshoot-publisher-verification).## Complete Publisher Attestation
|platform||Teams Store Validation Guidelines||https://github.com/MicrosoftDocs/msteams-docs/commits/master/msteams-platform/concepts/deploy-and-publish/appsource/prepare/teams-store-validation-guidelines.md||
An app's name plays a critical role in how users discover it in the store. Remem* If your app is part of an official partnership with Microsoft, the name of your app must come first (for example, **Contoso Connector for Microsoft Teams**). * Must not copy the name of an app listed in the store or other offer in the commercial marketplace. * Must not contain profane or derogatory terms. The name also must not include racially or culturally insensitive language.
+* Must be unique. For example, you cannot list multiple apps for different regions with the same name and functionality.See also: [4.0 App package and store listing](#40-app-package-and-store-listing)
|platform||Overview||https://github.com/MicrosoftDocs/msteams-docs/commits/master/msteams-platform/concepts/deploy-and-publish/overview.md|| - Title: Distribute your app
-description: Describes the three options for distributing your app`-
-keywords: teams publish store office distribute AppSource sideload upload app-
-# Distribute your Microsoft Teams app-
-Once you've created your app there are three options for distributing it:-
-1. [Upload your app directly](#upload-your-app-directly).
-2. [Publish your app to your organization's app catalog](#publish-to-your-organizations-app-catalog).
-3. [Publish your app through AppSource](#publish-to-appsource).-
-## Enterprise organizations-
-### Upload your app directly-
-This is the easiest way to test and use your app. If you are the team owner and/or [uploading custom apps is enabled](/microsoftteams/admin-settings), you can [directly upload (or sideload)](./apps-upload.md) the app and start using it right away. However, if you want to share the app with others, you'll have to send them your app package and ask them to upload it independently.-
-If you want to distribute your app more broadly,Teams provides an in-app gallery for users to find or discover high-quality Teams apps. To have your solution available in the gallery, you must either [publish to your organization's app catalog](#publish-to-your-organizations-app-catalog) or [publish to AppSource](./appsource/publish.md).-
-### Publish to your organization's app catalog-
-Your organization's app catalog contains apps unique to your organization and is completely under your organization's control. You can find more information in the article [*Publish apps to your organization's app catalog*](/microsoftteams/tenant-apps-catalog-teams). This feature can only be managed by Teams users with Microsoft Office 365 tenant admin privileges.-
-### Publish to AppSource-
-AppSource (formerly known as Office Store) provides a convenient location for you to distribute your Microsoft Teams app, as well as other Office 365 extensibility types such as Office add-ins and SharePoint add-ins. Follow our guidelines to [submit your app to AppSource](./appsource/publish.md).-
-## Government Community Cloud (GCC) organizations-
-### Upload your custom app directly to Teams-
- As a GCC tenant administrator, you'll decide whether to upload a custom app to your tenant environment and whether to publish it to your tenant app catalog. Microsoft doesn't own or control your custom applications, therefore, you must ensure that all endpoints are compliant with your organization's requirements. Additionally, if the app solution includes a bot or message extension, you'll need to complete the [Bot Framework](https://dev.botframework.com/) registration as follows:-
-1. On the **Connect to channels** page, under **Add a featured channel**, select **Teams**.
-1. Navigate to the **Configure MSTeams** page (*see* below).
-1. Under **Messaging** select the **Microsoft Teams for Government Customers** radio button.
-1. In the lower left corner of the page, select **Save**.-
-> You cannot use the Teams commercial configuration to upload/sideload your custom app to a GCC environment, You must select the **Microsoft Teams for Government Customers** radio button for a GCC compliant configuration.-
-![Teams messaging configuration page](../../assets/images/gcc-configure.png)-
-> * The uploading instructions for GCC environments, presented above, applies to Teams custom apps. </br>
-> * Compliant Microsoft apps are enabled in the GCC environment, by default, in Teams.
-> * Third-party apps are disabled at the tenant level and should be managed via your organization's [app permission policies](/microsoftteams/teams-app-permission-policies). Make certain that you review all third-party apps to ensure that they align with your organization's policies and procedures.-
-> Microsoft 365 developer partners provide security, data handling, and compliance details for their third-party Teams apps through the [Microsoft 365 App Certification Program](/microsoft-365-app-certification/overview). *See also* [Microsoft Teams App Certification](/microsoftteams/platform/concepts/deploy-and-publish/appsource/post-publish/application-certification).