Tenant
How it works
Each tenant is assigned a unique identifier and a logical boundary (an account, subscription, directory or namespace) to which its resources, access policies and data are tied. The authentication and authorization layer (e.g. an identity directory) maps users to a specific tenant and enforces that requests operate only within it. Isolation is implemented at various levels — from fully shared instances with row-level data separation to dedicated per-tenant resources — depending on the isolation model chosen for security and cost requirements. Billing, quotas and configuration are also bound to the tenant identifier. The correctness of these boundaries is critical: a flaw in isolation or in cross-tenant access control leads to data leakage or resource takeover (a cross-tenant incident).
Problem solved
Cloud providers must serve many independent customers on shared infrastructure while guaranteeing that one customer's data and configuration are invisible and inaccessible to others. The tenant concept provides a clear boundary around which isolation, access control, billing and compliance are built.