Docs › Administration › Tenant setup with Microsoft Entra
Tenant setup with Microsoft Entra
Last updated July 2026 · ~4 min read
A MeetCrew tenant is anchored to your organization’s Microsoft Entra tenant. One MeetCrew tenant maps to exactly one Entra tenant, and your existing identity and conditional-access policies govern who signs in and what they can reach.
What onboarding does
Setup begins when a Tenant Administrator authenticates through Microsoft Entra and grants admin consent to MeetCrew’s application. MeetCrew then resolves your Entra tenant region, you execute the deployment agreement, and you select a primary region. Once you confirm, MeetCrew provisions your isolated per-tenant resources in that region.
Identity comes from Entra
You do not provision users in MeetCrew. Every member of your Entra tenant is automatically a User in your MeetCrew tenant, resolved at request time against Entra. Authentication and access follow the identity and conditional-access policies you already run. Administrators are appointed explicitly on top of that inherited membership.
Hard isolation by design
Each tenant receives its own isolated storage, reachable only through tenant-scoped credentials. There is no configuration and no cross-tenant path that lets one customer see another’s data. A consultant working with several customers holds a role in each MeetCrew tenant only through a separate invitation per tenant.
A subsidiary or a separate dev, staging, or production Entra tenant is a separate MeetCrew tenant. Memory is never shared across tenants regardless of corporate relationship.
Was this helpful? Yes · No | Still stuck? Contact support.