Before you begin
- A Atlas AVD subscription licensed for more than one tenant: Community manages a single tenant
- An administrator role in Atlas AVD
- For each tenant you connect: an AtlasAVD app registration in that tenant with admin consent granted (see App Registration Setup)
- The Tenant Directory ID, Primary Subscription ID, Application (Client) ID, and Client Secret for each tenant
Atlas Command: the MSP console
With MSP Capabilities, Atlas Command appears in the sidebar for administrators, as Command under Atlas Operations. It is the console you use to run every tenant from one place, and it opens from your primary tenant (the one you set Atlas up in). Its tabs are Overview (fleet health, unified alerts, and cost across every managed tenant), Spend & Budgets, Command Center (the Managed Tenants roster), Atlas Reach, Fleet NOC (cross-tenant incidents, alerts, and tenant status), and Branding. Each tenant's Azure resources always stay in that tenant's own subscription. Atlas manages them in place and never moves infrastructure or data into a shared environment.
Atlas AVD and MSP Capabilities: how you manage several tenants
Every Atlas AVD subscription manages several licensed tenants and includes every Azure Virtual Desktop feature on each one. The optional MSP Capabilities upgrade changes how you see them:
- Atlas AVD on its own: license each tenant, switch between them with the Tenant Selector, and keep each one's data isolated. There is no all-tenants view, cross-tenant analytics or white-label branding.
- Atlas AVD with MSP Capabilities: adds Atlas Command, cross-tenant analytics, license usage per tenant and the full white-label package, for +$50 per licensed tenant a month. The upgrade applies to every licensed tenant on your subscription, and technicians and AVD users stay unlimited.
Community manages a single tenant. To manage several tenants, license them on Atlas AVD; to see every tenant at once in Atlas Command, or to put your own brand on the console, add MSP Capabilities. During the 30-day full-access trial, Atlas Command and white-label branding are available so you can evaluate them.
How tenant isolation works
Atlas keeps a central registry of the tenants you manage, and each tenant gets its own dedicated database, provisioned when you add it. Every request in the app is scoped to the currently selected tenant, so one customer's host pools, users, costs, and reports are never visible from another's context. Because Atlas authenticates to each tenant as an app registration you own in that tenant, the customer's Azure infrastructure and data remain entirely within the customer's own Azure environment.
Connecting a customer tenant
Click Add Tenant on the Tenant List page (Administration → Tenants → Tenant List); with MSP Capabilities it is also in the upper-right corner of every Atlas Command tab. It launches the Atlas setup wizard in Add Secondary Tenant mode, which walks through the same steps as your first-run setup, but for the new tenant. On the first step, Azure Setup, you enter:
- Organization Name for the customer
- Azure Environment: Azure Commercial, Microsoft 365 GCC (Azure Commercial), or Azure Government (GCC High)
- Application (Client) ID and Client Secret from the AtlasAVD app registration in that tenant
- Tenant Directory ID and Primary Subscription ID for the customer's Azure environment
Before you start, open Required Permissions on the Tenant List page to see the API permissions and Azure RBAC roles the tenant's app registration needs, and Manual setup script for the Cloud Shell command that creates it. Each tenant uses its own app registration with unique credentials, so you always enter fresh values. Nothing is carried over from another tenant.
How tenants are counted
Atlas AVD is priced per licensed tenant, and your subscription's tenant quantity sets how many tenants you can connect:
- Every tenant your deployment manages counts, including your own primary tenant and a tenant that only uses Atlas Reach
- Community: exactly one tenant
- Atlas AVD: the quantity you license, from one tenant, with no minimum beyond that
- MSP Capabilities, when you add it, is billed for that same quantity: every licensed tenant
- Each licensed tenant adds its included units to one shared pool, and technicians and AVD users are unlimited on every plan
On Community, Add Tenant is disabled and an Upgrade to add tenants option appears beside it. Once you reach your licensed quantity, Add Tenant takes you to the Tenant List, where a banner explains that adding another tenant needs a higher quantity. Nothing you already manage is removed or disabled. To manage more tenants, raise your tenant quantity.
After you connect a tenant
A connected tenant appears in the Tenant Selector in the top header bar. Switch into it to manage that customer's host pools, sessions, and users. With MSP Capabilities, switch back to your primary tenant and use Atlas Command's Overview and Fleet NOC tabs when you need a view across every tenant at once. See Switching Between Customer Tenants for how scoping works.