microsoft / microsoft/CopilotStudioSamples
[Implementation Guide] Multi-Tenant Deployment & Budget Separation
@HenryJammes is already working on this.
Since Dec 7, 2025.
- Dominant language
- TypeScript
- Stars
- 797
- Forks
- 491
- PR merge metrics
- No merged PRs in 30d
Description
Template version: v1.0 (from first slide – bottom left)
Slide number(s): Deployment, Architecture
Detail your feedback and suggestions:
Thank you for the great implementation guide, it is very helpful.
I have two questions related to a common multi-tenant use case:
-
Deployment across tenants
If we develop an agent (including child agents, tools, and connections) in the Test Environment of Tenant-A, is there a recommended approach to deploy this agent into the Production Environment of Tenant-B?
If yes, what is the supported pattern? -
Budget / cost separation per department within the same tenant
In the same tenant (Tenant-A), there may be separate departments (HR, Finance, Logistics, etc.) with independent budgets.
What is the recommended approach to separate costs per agent?
- Should each department have its own environment (e.g., HR-Environment, Finance-Environment)?
- If so, what is the recommended deployment model from Dev → these environments?
Any guidance or documentation would be appreciated.
Thank you very much!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.