Managing multiple Microsoft tenants
Connect several Entra and Intune tenants to one ITOps360 account, manage identities and devices across them, and add members or guests to many tenants at once.
Online version, always current: https://cloudvision360.com/docs/itops360/multi-tenant/
A managed service provider — or any organization that runs more than one Microsoft tenant — can connect several Entra ID and Intune tenants to one ITOps360 account and manage identities and devices across all of them from one place. You no longer need a separate account per tenant, and tickets, SLAs, reporting and the audit trail stay together.
One app registration for every tenant
ITOps360 authenticates to each tenant with the standard Microsoft multi-tenant application model, so you register one app once and reuse it everywhere:
- Register an app in your home tenant and mark it multi-tenant.
- In each customer or subsidiary tenant, an administrator grants admin consent once — this creates the service principal in that tenant.
- Add a connection in ITOps360 for each tenant, reusing the same client ID; only the directory (tenant) ID changes.
The read-only and (optional) write permissions are the same ones a single-tenant connection asks for. For least privilege and a smaller blast radius, use one app per product rather than sharing one secret across CloudVision360, ITOps360 and AgentVision360.
Connect the tenants
Open Admin → Settings → Integrations → Connected tenants and add an Entra or Intune tenant. Each connection has:
- A display name, so the tenant is easy to recognize (for example Contoso — contoso.onmicrosoft.com).
- Its own directory (tenant) ID, client ID and secret, and optional separate write app.
- A primary marker. One connection of each kind is the primary — the tenant that single-tenant features (outbound and inbound mail, Microsoft 365 backup) use.
Each tenant is synced on its own schedule. Users and devices are tagged with the tenant they came from, so every action — a password reset, enable or disable, MFA reset, license change, group membership change, or any device action — routes back to the right tenant automatically, and so does its verification. Disconnecting a tenant removes only the records it brought in; the other tenants are untouched.
Create members or invite guests across tenants
From People → Joiners → Create across tenants, provision the same person into several tenants in one action — replacing the scripts teams used to run by hand:
- New member — create an account in each selected tenant, each with its own user principal name (pre-filled from the mail nickname). A one-time password is returned per tenant to deliver securely.
- Guest invite — send a Microsoft B2B guest invitation of one external e-mail to every selected tenant; Entra sends each invitation.
Licenses and groups can be applied in each tenant. Every tenant is independent — one failing does not stop the rest — and every outcome is recorded in the hash-chained audit trail.
Which plan
Managing multiple Microsoft tenants and bulk cross-tenant provisioning are Enterprise features, and a fit for MSPs running many customer tenants. Single-tenant connection, sync and actions are available on Professional.