Azure tenant

As explained in Microsoft Azure in Action

A Microsoft Entra ID tenant is a dedicated identity and access management instance that provides an organizational boundary for users, resources, and applications.

An Azure tenant is a dedicated Microsoft Entra ID instance: the identity boundary for an organization’s users, groups, applications, and policies. Creating an Azure account gives you a tenant. Think of it as the place Azure checks who someone is before deciding what they can access. section 6.6.1 section 6.3

A tenant is not the same as a subscription. Subscriptions contain resources such as storage accounts and virtual machines, and each subscription is tied to one tenant. A tenant can have several subscriptions—for example, separate development and production subscriptions—under the same identity boundary. The subscription is also the billing entity. section 6.6.1

Figure 6.29 Relationship between an Entra ID tenant, users, subscriptions, and resources. Users and groups belong to the tenant. Subscriptions exist within the tenant, and each subscription contains resource groups, which in turn contain Azure resources.

Use this hierarchy to locate each piece: users and groups belong to the tenant; subscriptions sit beneath it; resource groups and Azure resources sit beneath subscriptions. section 6.6.1

When someone signs in, Entra ID checks their identity and tenant, whether they can access the subscription, and what they are allowed to do. Users can be people in the organization or external collaborators invited as guests. Applications and processes can have identities too. Being in the tenant is therefore a starting point, not a free pass to every resource; permissions are handled through role-based access control (RBAC). section 6.6.1 section 6.3

Keeping local files and cloud files together

A business that needs more file storage can connect its on-premises directory to its Entra ID tenant using Entra Cloud Sync. Its users and processes can then authenticate across the local and Azure environments, while Azure File Sync keeps local files and Azure file shares synchronized. The tenant supplies the identity side of this hybrid setup; the storage account holds the cloud file shares. section 1.2.2

How Microsoft Azure in Action covers it

How deep it goes

Defines the tenant and maps its users, subscriptions, and resources, while leaving detailed RBAC permission setup for later.

Examples

Illustrates separate development and production subscriptions and a hybrid file setup using Entra Cloud Sync and Azure File Sync.

What it assumes

Introduces tenants from the basics of creating an Azure account and distinguishes them from subscriptions without assuming familiarity with their relationship.

What you can do after

Evaluate/understand where identities belong, how subscriptions relate to a tenant, and why tenant membership alone does not grant resource access.

How it connects

Connects Microsoft Entra ID with subscriptions, guest users, RBAC, service principals, and managed identities.

liveBookmanning.com

Read Microsoft Azure in Action on liveBook Get the book at manning.com

Related concepts

• Azure subscriptionhas part · An Azure subscription is a management and billing boundary that provides access to Azure services and organizes the resources created within it.
• userhas part · A user is a person or other entity that interacts with, or is represented within, a system to access or use its functions.
• Microsoft Entra IDpart of · Microsoft Entra ID is Microsoft's cloud-based identity and access-management service for authenticating users, applications, and services and controlling their access to resources.
• identity and access managementconfigures · Identity and access management is the discipline and set of policies and systems for managing digital identities and controlling their authentication, authorization, and access to resources.
• fine-tuningused by · Fine-tuning is adapting a pretrained machine-learning model by training it further on targeted data or objectives for a task, domain, or behavior.

This explainer was generated by Manning's knowledge graph from the text of Microsoft Azure in Action. The section links point to the parts of the book it draws on.