Before you begin
- An Atlas AVD subscription with room in its licensed tenant quantity for another tenant (see Managing Multiple Customer Tenants)
- An administrator role in Atlas AVD
- A customer administrator who can create an app registration and grant admin consent in their tenant
1. Prepare the customer's app registration
Atlas cannot create the app registration in a tenant it is not yet signed in to, so it is created in the customer's tenant first. Open Administration → Tenants → Tenant List. Required Permissions lists the API permissions and Azure RBAC roles the registration needs, each marked Required or Optional, and Manual setup script links to the Cloud Shell command that creates the registration, grants admin consent, assigns the Azure roles, and prints the Client ID and Client Secret. Review the list with the customer's administrator, then run the script in the customer's tenant (see App Registration Setup).
2. Run the Add Tenant wizard
Click Add Tenant, either on the Tenant List or in the upper-right corner of any Atlas Command tab with MSP Capabilities. The setup wizard opens in Add Secondary Tenant mode and runs the same steps as first-run setup. On Azure Setup, enter the customer's details:
- 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 customer's AtlasAVD app registration
- Tenant Directory ID and Primary Subscription ID for the customer's Azure environment
The remaining steps (Permissions, Confirm, Tenant Config, and so on) apply to the new tenant only. The software step reads Tenant Software here: it sets the winget software and browser extensions installed on this tenant's host pools, not your organization-wide baseline.
3. After you submit
Atlas then sets the tenant up in three stages you can watch on screen: Setting up isolated database (a dedicated database for the tenant), Discovering Azure resources (scanning its subscriptions for host pools and session hosts; most tenants finish within a minute), and Ready. A live log under the current stage shows each step as it happens, and View setup log on the Ready stage lets you review it afterwards. When the tenant is ready, go to its dashboard or back to the tenants page; the tenant also appears in the Tenant Selector and, with MSP Capabilities, in Atlas Command's Managed Tenants list.
If Atlas reports it couldn't read the customer's Azure environment, the tenant is set up but its host pools will not appear yet. Check that the app registration's service principal has the Desktop Virtualization Reader role and an unexpired client secret, then run Sync from the Host Pools page. If database setup fails, use Retry database setup, or Remove this tenant to start over.