Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124

Learn how subscriptions connect to Azure Active Directory, why the trust relationship matters, and how to spin up a new subscription in minutes.
An Azure subscription is the logical entity that gives you entitlement to deploy, consume, and be billed for Azure resources. Think of it as the contract between you and Microsoft Azure.
Understanding the relationship between subscriptions, directories, and resources is the foundation of Azure governance.

A subscription can only trust one directory, but a directory can be trusted by many subscriptions. This asymmetry is fundamental to Azure governance design — organize your subscriptions per billing or environment boundary, all pointing at a single corporate directory.
Azure offers multiple subscription types to match different organizational needs, budgets, and use cases. Each comes with its own pricing model and service availability.
Creating a new Azure subscription and associating it with your Azure AD directory takes only a few minutes in the Azure Portal.
Before you move or reassign subscriptions, understand these behaviors that catch many Azure administrators off guard.
Always document and export all RBAC role assignments and Azure Policy definitions before transferring a subscription to a new directory. These are not automatically migrated and must be manually recreated post-transfer.
Microsoft will attempt to contact you before disabling an expired subscription, but resources enter a “disabled” state quickly. Ensure billing information is always current to avoid unexpected access loss to production workloads.
Azure subscriptions are the billing and entitlement backbone of your Azure environment. Understanding how they relate to Azure AD directories — and what happens when you move or expire them — is foundational knowledge every Azure administrator and architect must have.