Required for the site to work (login, preferences, security). Always on.
Org ≠ tenant: the MSP vocabulary that stops wrong isolation
In multi-tenant identity models, a tenant is typically the hard isolation boundary for a customer (directory / control-plane scope). An organization (or similar soft grouping) can nest inside a tenant for teams, brands, or billing units — without becoming a second customer boundary.
In multi-tenant identity models, a tenant is typically the hard isolation boundary for a customer (directory / control-plane scope). An organization (or similar soft grouping) can nest inside a tenant for teams, brands, or billing units — without becoming a second customer boundary.

Org ≠ tenant: the MSP vocabulary that stops wrong isolation
Cite: Microsoft Learn — Multitenant identity considerations; secondary FAQ framing on user vs tenant vs membership.
Users and workloads are not tenants. Access is via membership (and roles) that the application must re-verify — including when a principal belongs to multiple tenants. Collapsing “org” into “customer tenant” in MSP vocabulary is a common source of wrong isolation designs.
One customer → one hard tenant; many soft orgs may live inside.
Soft land: Auris models customer = tenant with soft orgs inside. Sovereign-mode language here means operational posture (isolation + evidence), not a certification seal.