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.
[This article is prerelease documentation and is subject to change.]
Make your multitenant agent available in Teams or Microsoft 365 Copilot by updating your manifest file and submitting it to the Teams Store.
Important
The multitenant feature in Copilot Studio is in public preview and is clearly marked in Copilot Studio for makers. It has terms that are referenced in the product. Public preview features aren't supported for use in a generally available capacity. However, you can trial public preview agents on the Teams/Agent Store under specific guidelines. Partners should highlight to their end users that their agents use preview functionality by including a Preview banner in the icon.
Note
When you publish your Copilot Studio agent and select multitenant mode, you're responsible for the terms and privacy for the published multitenant agent. This responsibility includes where those terms and any related privacy notices are shown to your end user admins and end users, such as the Teams and Agent stores. Additionally, the Microsoft Teams and Agent Stores have Terms and Publishing Agreement requirements on Partner Center, which you should review fully.
Submit to Microsoft 365 Store
The following sections describe how to make your agent available in the Microsoft Teams and Microsoft 365 Copilot client. The sections cover exporting the manifest from Copilot Studio, updating the manifest file, and submitting it to the Teams Store via the Partner Center.
Export the manifest from Copilot Studio
When you're ready to test the agent in the Microsoft Teams or Microsoft 365 Copilot client in another tenant, you need to make the agent available in the second tenant. For testing, a MAC admin or a user with permissions to sideload the agent in their client (granted by a MAC admin in the second tenant) must sideload the agent into the other tenant.
The Power Platform Admin Center tenant isolation policy can restrict host tenant access. You can add your test client tenant information when testing across your own specific tenants as you move through the application lifecycle management process.
To export the manifest .ZIP file, go to Channels in Copilot Studio, select the Teams and Microsoft 365 Copilot channel, and then select Edit Details.
You can edit the name, description, and other details in the manifest file required by Microsoft Teams and Microsoft 365 Copilot. The manifest file contains important metadata about your agent, which the client tenant sees when reviewing your agent for use on their tenant.
After you edit the details, select Availability Options to export the .ZIP file.
This action downloads a local .ZIP file to your machine. The .ZIP file contains the icon color and manifest files. You can also edit the manifest manually. While the feature is in public preview, makers need to edit the manifest, specifically in the Valid Domains node. For more information, see Update valid domains.
Update valid domains
In the manifest file, there's a node called ValidDomains. This section of the manifest specifies what domains the agent can access.
Add the correct geography for your host agent based on the Dataverse environment geography:
unitedstates.token.botframework.com// include only if host geo is United Stateseurope.token.botframework.com// include only if host geo is in Europeindia.token.botframework.com// include only if host geo is Indiatoken.botframework.com// include if the host geo is any other location
Always include the following domain:
api.botframework.com// must be included
Avoid using wildcard domains (such as *.example.com) unless you own them, as their use poses security risks.
Avoid using Microsoft-owned domains (including domains associated with Microsoft Copilot Studio) in the domain configuration.
Submit to the Teams Store via the Partner Center
To submit your agent to the Teams Store, review and follow the process described in Publish your app to the Teams Store. The partner needs to review and agree to the expected terms and conditions based on the program the agent is being submitted under.
The same export and import process applies. The .zip package exported from Copilot Studio should contain the following items to help the end user understand what your agent does, including providing documentation and troubleshooting information:
- Host organization's terms and conditions
- Privacy policy
- Other required documentation
Select the regions in Partner Center to match the host Dataverse environment geography (Optional)
When addressing data residency requirements, keep in mind that both the host and client might be located in different regions. If data residency is a goal, choose only those countries and regions in Partner Center that match the Dataverse geography where the agent is hosted (refer to the table below). Additionally, ensure that you consider any communication between the agent and non-Microsoft tools or services. The responsibility for fulfilling data residency requirements falls on the host or hosting organization, not on Microsoft.
Note
Available regions in Dataverse are based on the Microsoft Entra tenant's home location. From that location, you can create Dataverse regions in various other regions around the globe. You can create a database for an environment in one region (for example, United States) even if the Microsoft Entra tenant is in another region, as explained in Power Platform regions overview. Environments are created in different regions and are bound to that geographic location. When you create an app in an environment, you deploy that app in datacenters in that geographic location.
| Host Dataverse Geo | Valid Domain | Partner Center Countries/Regions |
|---|---|---|
| United States | unitedstates.token.botframework.com |
United States |
| Europe | europe.token.botframework.com |
47 countries/regions: Åland Islands, Albania, Andorra, Austria, Belarus, Belgium, Bosnia and Herzegovina, Bulgaria, Croatia, Cyprus, Czechia, Denmark, Estonia, Faroe Islands, Finland, Gibraltar, Greece, Guernsey, Hungary, Iceland, Ireland, Isle of Man, Italy, Jersey, Latvia, Liechtenstein, Lithuania, Luxembourg, Malta, Moldova, Monaco, Montenegro, Netherlands, North Macedonia, Poland, Portugal, Romania, Russia, San Marino, Serbia, Slovakia, Slovenia, Spain, Svalbard, Türkiye, Ukraine, Vatican City |
| Asia | Generic: token.botframework.com |
45 countries/regions (excluding India, Japan, and Korea; see their dedicated rows): Afghanistan, Armenia, Azerbaijan, Bahrain, Bangladesh, Bhutan, Brunei, Cambodia, China, Cyprus, Georgia, Hong Kong SAR, Indonesia, Iraq, Israel, Jordan, Kazakhstan, Kuwait, Kyrgyzstan, Laos, Lebanon, Macao SAR, Malaysia, Maldives, Mongolia, Myanmar, Nepal, Oman, Pakistan, Palestinian Authority, Philippines, Qatar, Russia, Saudi Arabia, Singapore, Sri Lanka, Taiwan, Tajikistan, Thailand, Timor-Leste, Türkiye, Turkmenistan, Uzbekistan, Vietnam, Yemen |
| Australia | Generic: token.botframework.com |
Australia |
| India | india.token.botframework.com |
India |
| Japan | Generic: token.botframework.com |
Japan |
| Canada | Generic: token.botframework.com |
Canada |
| United Kingdom | europe.token.botframework.com |
United Kingdom |
| South America | Generic: token.botframework.com |
12 countries/regions: Argentina, Bolivia, Brazil, Chile, Colombia, Ecuador, Guyana, Paraguay, Peru, Suriname, Uruguay, Venezuela |
| France | europe.token.botframework.com |
France |
| United Arab Emirates (UAE) | Generic: token.botframework.com |
United Arab Emirates |
| Germany | europe.token.botframework.com |
Germany |
| Switzerland | europe.token.botframework.com |
Switzerland |
| Norway | europe.token.botframework.com |
Norway |
| Korea | Generic: token.botframework.com |
Korea |
| South Africa | Generic: token.botframework.com |
South Africa |
| Sweden | europe.token.botframework.com |
Sweden |
Users must select the related countries and regions relevant to the Dataverse geo and schema mapping. United States and India are straightforward. Europe can contain more than 40 countries and regions, and the Dataverse environment could be Europe, Germany, France, Sweden, Norway, Switzerland, or United Kingdom.