Tenant setup with Microsoft Entra

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. You then attest to the country your organization is established in and execute the deployment agreement. Once you confirm, MeetCrew provisions your isolated per-tenant resources in Microsoft Azure’s US East region, where every tenant is hosted today. Nothing detects where your organization is; the region is assigned, not resolved from your directory.

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.