[Implementation Guide] Multi-Tenant Deployment & Budget Separation

Open
#426 0 comments 0 reactions 1 assignee View on GitHub

@HenryJammes is already working on this.

Since Dec 7, 2025.

Assessment

This issue has not been assessed yet.

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:

  1. 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?

  2. 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!

Dominant language
TypeScript
Stars
797
Forks
491
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/CopilotStudioSamples

All issues in microsoft/CopilotStudioSamples

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.