Copilot Studio Multi-Tenant Support is one of the most exciting new capabilities introduced by Microsoft for organizations building AI agents. This feature allows a Copilot Studio agent hosted in one Microsoft Entra tenant to be accessed by users from another tenant. For enterprises, partners, ISVs, and managed service providers (MSPs), this opens up entirely new possibilities for sharing and deploying AI agents without creating separate copies for every customer.

In this article, you’ll learn everything about Copilot Studio Multi-Tenant Support, including what it is, how it works, how to enable it, supported scenarios, current limitations, and best practices.

What is Copilot Studio Multi-Tenant Support?

Copilot Studio Multi-Tenant Support is a new Public Preview feature that allows a Copilot Studio agent to be accessed from a different Microsoft Entra tenant than the tenant where the agent is hosted.

Before this feature was introduced, users could only access an agent if they belonged to the same tenant as the agent. If users from another tenant attempted to use the agent, access was denied.

With Multi-Tenant Support in Copilot Studio, organizations can now build an agent once and securely make it available to users from other Microsoft Entra tenants through supported Microsoft channels.

Why is Copilot Studio Multi-Tenant Support Important?

Many organizations develop Copilot Studio agents for multiple business units, subsidiaries, customers, or partner organizations.

Without multi-tenant capabilities, makers often had to:

• Maintain separate agents for different tenants
• Deploy updates individually
• Duplicate configurations
• Increase maintenance effort

With Copilot Studio Multi-Tenant Configuration, Microsoft enables a more centralized deployment model where a single hosted agent can be consumed across multiple tenants, reducing operational overhead.

How Does Copilot Studio Multi-Tenant Support Work?

The feature introduces two important concepts:

Host Tenant

The Host Tenant is where:

• The Copilot Studio agent is created
• The agent is managed
• Billing occurs
• Updates are published
• ALM processes are performed

Everything continues to be managed from this tenant.

Client Tenant

The Client Tenant is where users access the agent.

Users authenticate through supported Microsoft clients such as:

• Microsoft Teams
• Microsoft 365 Copilot

The client tenant doesn’t host the agent—it simply consumes it from the host tenant.

How to Enable Copilot Studio Multi-Tenant Configuration

Enabling Copilot Studio Multi-Tenant Configuration is straightforward.

Step 1

Open your Copilot Studio agent.

Step 2

Navigate to:

Settings → Security

Step 3

Enable:

Multi-Tenant Support

Step 4

Publish your agent.

Once published, supported users from external Microsoft Entra tenants can access the agent through supported Microsoft channels, provided the necessary administrative policies allow it.

Supported Channels

Currently, Copilot Studio Multi-Tenant Support works only with:

• Microsoft Teams
• Microsoft 365 Copilot

Other publishing channels are not currently supported during Public Preview.

Supported Features

Although the feature is in Preview, Microsoft already supports several capabilities across tenants.

These include:

• Dataverse uploaded knowledge
• Public website knowledge sources
• Prompt actions
• REST API connectors
• Limited standard connectors

This allows organizations to build useful cross-tenant AI experiences while Microsoft continues expanding feature support.

Current Limitations of Multi-Tenant Support in Copilot Studio

Since the feature is currently in Public Preview, several limitations still exist.

Some of the important limitations include:

End-user authentication

End-user authentication isn’t currently supported.

This means agents cannot use an external user’s identity when accessing downstream services.

Custom Connectors

Custom Connectors aren’t supported in Multi-Tenant mode.

MCP Tools

MCP Tools are currently unavailable.

Agent Flows

Agent Flows cannot be used when Multi-Tenant mode is enabled.

Conversation Transcripts

Conversation transcripts are disabled to help protect the privacy of users across different tenants.

Analytics

Several analytics features remain unavailable, including:

• Session download
• Transcript data
• Satisfaction reports
• Aggregated analytics

Other Limitations

Currently, Multi-Tenant mode also doesn’t support:

• OAuth authentication
• Guest users
• Group conversations
• Multi-Geo deployments
• GCC and GCC High environments

Microsoft notes that if a capability isn’t explicitly listed as supported, you should assume it isn’t supported in the current Public Preview.

Security Considerations

One of the most important points Microsoft highlights is Maker Authentication.

If your agent uses Maker Credentials when connecting to downstream services, carefully review your implementation.

Because the same hosted agent serves users across multiple tenants, improperly configured maker credentials could expose tenant-specific information through downstream systems.

Organizations should carefully validate their authentication model before deploying Multi-Tenant agents in production scenarios.

Administrative Controls

Power Platform administrators remain in control of Multi-Tenant access.

Using the Power Platform Admin Center (PPAC), administrators can:

• Disable Multi-Tenant Support
• Configure tenant isolation
• Allow only approved tenants
• Restrict inbound and outbound tenant communication

If tenant isolation is enabled, Multi-Tenant Support becomes unavailable for Copilot Studio agents.

Best Practices for Copilot Studio Multi-Tenant Setup

Before enabling Multi-Tenant Support, consider these recommendations:

• Test your agent in separate development and test tenants.
• Validate authentication behavior across tenants.
• Review supported connectors before deployment.
• Monitor capacity and billing because the host tenant is responsible for all consumption.
• Clearly inform users if your agent uses Preview functionality.
• Perform thorough testing before production deployment.

These practices help reduce deployment risks while the feature continues to evolve.

Frequently Asked Questions (FAQ)

Is Copilot Studio Multi-Tenant Support Generally Available?

No. It is currently available as a Public Preview feature.

Which channels support Multi-Tenant agents?

At present, only Microsoft Teams and Microsoft 365 Copilot are supported.

Can I use Custom Connectors?

No. Custom Connectors aren’t supported during the current Public Preview.

Who pays for the agent?

The Host Tenant is responsible for licensing, billing, and capacity consumption.

Can users from another Microsoft Entra tenant access my agent?

Yes. That’s the primary purpose of Copilot Studio Multi-Tenant Support, provided the feature is enabled and tenant policies permit access.

Copilot Studio Multi-Tenant Support YouTube Video Tutorial

If you prefer learning through videos, I’ve created a quick tutorial covering how to enable multi-tenant support in Copilot Studio.

Conclusion

Copilot Studio Multi-Tenant Support is a significant step toward making AI agents easier to share across organizations. Instead of maintaining separate copies of the same agent for different tenants, organizations can now build once and allow supported users from other Microsoft Entra tenants to access the same centrally managed agent.

Although the feature is still in Public Preview and includes several limitations, it provides an exciting foundation for partners, enterprises, and software vendors looking to deliver AI-powered experiences across tenant boundaries.

As Microsoft continues enhancing Multi-Tenant Support in Copilot Studio, we can expect broader channel support, improved authentication capabilities, and additional enterprise features in future releases.

If you’re planning to build cross-tenant AI solutions, now is an excellent time to explore Copilot Studio Multi-Tenant Configuration in a test environment and understand how it fits into your organization’s AI strategy.

Official Microsoft Documentation: Overview of multitenant mode in Copilot Studio (preview)

See Also

• Copilot Studio Tutorial — Articles Hub (Beginners to Advanced)

About Post Author