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.]
When you use Microsoft Copilot Studio to build and host agents for different tenants in multitenant mode, follow these best practices. If you plan to publish your agent in the store, ensure your agent meets all the listed criteria. Some of these best practices are mandatory for store publication.
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.
Provide a direct path to submit support tickets
Consider providing a direct path for your end users to submit support tickets. For example, you can add this path via the description of your agent or even as an integrated topic you create in Copilot Studio.
Preview icon
Add the preview icon on the agent or in your agent description to help your end users understand that your agent is using public preview functionality.
Tenant isolation admin control
If you get an error when publishing or trying to switch on multitenant mode, speak with your admin to check if tenant isolation is turned on. Multitenant mode isn't available when tenant isolation mode is on unless your admin adds exceptions in your tenant.
Follow standard software development lifecycle practices
Always follow standard practices for development, from testing locally to testing in multitenant mode in the target client before submitting to the Teams Store or distributing your agent.
Billing
Ensure host tenant organizations have adequate measures in place to protect the business from unexpected charges and from not having enough credits to manage demand from the agent. Use the existing features of the platform to plan and manage your production environment spending and capacity. Customers are limited to the maximum Copilot Studio credits and sessions as currently available in Power Platform admin center.
Analytics in Copilot Studio
Limited analytics are available in public preview. Dataverse transcripts and the analytics API are disabled when multitenant mode is on.
If you publish to the global Teams Store via Partner Center, you might be able to access analytics relating to store downloads and usage.
Teams Store analytics
If you publish to the global Teams Store via Partner Center, you might be able to access analytics relating to store downloads and usage.
Purview integration and third-party app usage
Note
Organizations that install third-party apps have their own privacy and terms which you should review before use.
There's standard Purview integration for the host tenant for maker behavior in Copilot Studio and usage.
Additionally, there's Microsoft Purview integration on the client tenant for being an integrated application installed in the client Microsoft 365 tenant that uses the agent on the host tenant. Users from the client tenant show up as "anonymous" in the host tenant Purview and don't show a User GUID. There could be data shared from the client tenant using the agent to the host tenant Purview as a third-party application.
Known issues
- Makers can't unpublish an agent from the Microsoft Copilot channel.
- You can't separately manage Teams and Microsoft Copilot channels as independent channels outside of the checkbox in Copilot Studio Channel page.
- If you turn off your agent in the Teams channel, this action disrupts service for your agent. You can turn your agent on again as its agent ID isn't changed. However, you might have to complete the publish process again.