Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
There are two ways to distribute your Microsoft Teams agent or app:
- Publish to your organization: Make your agent or app available to people within your organization. Requires your Teams admin's approval.
- Publish your agent or app to the Teams Store: Make your agent or app available to everyone on the Teams Store. Requires Microsoft approval.
How you publish depends on several factors including users' needs, business, technical requirements, and your goals for the agent or app.
Publish to your organization
Teams agent or apps can be distributed privately within an organization and do not need to be published to the Teams Store for tenant-internal use. Availability to users can be controlled through Teams admin policies and app setup controls in the customer tenant. For more information, see manage your apps in the Teams admin center.
Government Community Cloud (GCC) organizations
In GCC Teams environments, compliant Microsoft agent or apps are enabled by default. Before publishing an agent or app, however, make sure that all the agent or app's endpoints comply with your GCC organization's requirements. For more information, see Government Community Cloud.
Important
If your agent or app includes a bot or message extension, you must select the Microsoft Teams for Government option when setting up a channel between your bot and Teams in Azure. For more information, see connect a bot to channels.
Publish your agent or app to the Teams Store
You can publish your agent or app directly to the Microsoft Teams Store inside Microsoft Teams and reach millions of users around the world. If your app is also featured in the Teams Store, you can instantly reach potential customers. For more information, see publish to the Teams Store.
Enable customization for your Microsoft Teams agent or app
You can allow customers to customize some aspects of your Microsoft Teams agent or app in the Teams admin center. This feature is supported only for apps published to the Microsoft Teams Store. For more information, see Enable customization for your Microsoft Teams app
Before you publish
Before you publish your agent or app, complete the following steps to ensure your agent or app is ready for distribution.
Configure default install options
You can configure default install options. For example, if your agent or app's primary capability is a bot, you can make the bot the default capability when a user installs your agent or app to a team. For more information, see Configure default options for Teams app
Create Teams agent or app package
To publish your Teams agent or app, you must have a valid app package. An app package is a zip file that contains an app manifest and app icons. For more information, see Teams app package
Upload your agent or app in Teams
Upload a custom agent or app for personal use, collaborating with your team, or testing and debugging. This kind of distribution doesn't require a formal review process.
Important
Uploading custom agent or apps are available in Government Community Cloud (GCC) but aren't available in GCC High, Department of Defense (DoD), and Teams operated by 21Vianet.
For more information, see upload your app in Teams.
Next step
See also
Collaborate with us on GitHub
The source for this content can be found on GitHub, where you can also create and review issues and pull requests. For more information, see our contributor guide.
Platform Docs