Skip to content
Tutorials Center
My learning

Topics

Lesson 3 of 57 ยท Cloud and Azure Basics

Accounts, Tenants and Subscriptions

Understand how Azure organizes access and billing: the free account, Microsoft Entra tenants, subscriptions, management groups, quotas and billing scopes.

New Azure users often mix up three words that sound alike: account, tenant and subscription. They are different things with different jobs. A tenant is your organization's identity directory, a subscription is a billing and resource container, and a management group is a folder that organizes subscriptions. Once you see how they nest, permissions, budgets and policies become much easier to reason about.

This lesson explains the hierarchy and where limits and bills attach to it. Everything about the real portal is described read-only, because it needs an account. The runnable examples are JavaScript stand-ins that walk the hierarchy and answer "which scopes sit above this resource?".

The free account

You can start with an Azure free account. At the time of writing it offers a credit for the first 30 days, a set of services that are free for 12 months, and a list of services that are always free up to a monthly limit. You need a Microsoft account (or a work account), a phone number and a payment card for identity verification. Terms change, so read the current offer on the sign-up page rather than relying on a tutorial.

Signing up creates two things at once:

  1. A Microsoft Entra tenant (if you did not already belong to one), which holds your users.
  2. A subscription inside it, which is where you create resources and where charges accumulate.

A common beginner worry is cost. The safe habits are the same as in any cloud: create a budget before you build (see Pricing, Cost Management and Budgets), group experiments in one resource group and delete it when you finish.

Tenants: who you are

A tenant is a dedicated instance of Microsoft Entra ID (formerly Azure Active Directory) that represents one organization. It holds users, groups and applications, and it is the authority that signs people in. Every tenant has a unique ID (a GUID) and a default domain such as contoso.onmicrosoft.com; you can add your own custom domain.

Two points are important:

  • A tenant is about identity, not about resources or bills. Users live in the tenant.
  • A subscription trusts exactly one tenant at a time. People who sign in to that tenant can be given access to the subscription's resources. Details of identities are in Microsoft Entra ID.

A person can belong to several tenants, for example their employer's and a client's (as a guest). The portal's directory switcher changes which tenant you are working in.

Subscriptions: where resources and bills live

A subscription is a logical container for resources and the unit of billing and of many limits. All resources belong to exactly one subscription (through a resource group, see Resource Groups and Azure Resource Manager). People use subscriptions to separate things:

  • Environments: one for production, one for development and testing.
  • Teams or products: each team gets its own spending and access boundary.
  • Limits: quotas apply per subscription, so a runaway test cannot consume production's capacity.

Subscriptions also come with an offer type: free trial, pay-as-you-go, an Enterprise Agreement, a Microsoft Customer Agreement, or a monthly credit for Visual Studio subscribers. The offer decides prices and billing arrangements, not the features you can use.

Quotas and limits

Each subscription has quotas: the number of vCPUs per region and VM family, the number of public IP addresses, storage accounts per region and so on. Quotas protect both you and Azure from accidents. A common surprise is a deployment failing with a message like "quota exceeded" for a VM family in a region. You then request an increase in the portal's Quotas page, or choose a different size or region. There are also service limits, fixed technical maximums of a service that apply regardless of quota. Check them before designing something huge.

Management groups: organizing many subscriptions

Once you have more than a handful of subscriptions, you want to apply the same rules to many of them. Management groups are containers above subscriptions. You can nest them up to six levels deep (not counting the root and the subscription level). Policies and role assignments applied to a management group are inherited by every subscription below it.

Every tenant has one root management group, which every other management group and subscription sits under. The picture of the whole hierarchy:

flowchart TB
    T["Tenant root management group"] --> MG1["Management group: Corp"]
    T --> MG2["Management group: Sandbox"]
    MG1 --> S1["Subscription: Prod"]
    MG1 --> S2["Subscription: Dev"]
    MG2 --> S3["Subscription: Experiments"]
    S1 --> RG1["Resource group: web-prod"]
    S1 --> RG2["Resource group: data-prod"]
    RG1 --> R1["Resource: web app"]

Scopes nest: management group, subscription, resource group, resource. Access and policy flow downward.

This four-level idea of scope returns constantly. Role-Based Access Control assigns roles at a scope and children inherit them; Azure Policy, Locks and Tags assigns policies the same way.

Billing scopes

Billing has its own hierarchy, separate from the resource hierarchy, which depends on your agreement type. In general:

  • A billing account is the top-level relationship with Microsoft, owning invoices.
  • Billing profiles and invoice sections group charges and decide how they are invoiced (for example, one invoice per department).
  • Each subscription is assigned to a billing arrangement, so its charges land on a particular invoice.

For a single learner with a pay-as-you-go account, all of this collapses into one billing account, one profile and one subscription. Large organizations use the extra layers for chargeback. Tags (covered later) also help break a bill down by project or owner.

Walking the hierarchy: a stand-in

The first example models the tree above and finds, for any resource, the chain of scopes that govern it. This is how Azure decides which policies and role assignments apply. The names are invented.

JS Which scopes govern a resource?

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Quota checks: a stand-in

The second stand-in checks a deployment request against per-region vCPU quotas, the way the platform refuses a deployment that would go over. The numbers are invented.

JS A quota check

Press Run (or Ctrl + Enter) to see the console output here.

No output.

The real quota system works per VM family and per region, and increases are requests to Microsoft, which can be approved quickly or not. Treat the stand-in as the idea only.

What the real commands look like

The following commands are read-only here. They show your tenant and subscription from the CLI:

Terminal
az login
az account show --output table
az account list --output table
az account set --subscription "Prod"

az account set selects the default subscription for later commands, which is a common source of "I deployed to the wrong subscription" mistakes. Run az account show before you create anything.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What does a Microsoft Entra tenant primarily represent?

    A tenant is a dedicated Entra ID instance holding identities. Resources and bills live in subscriptions.
  2. 2. How many tenants can a single subscription trust at one time?

    A subscription is associated with one Entra tenant, which authenticates the users who can be granted access.
  3. 3. Where do you assign a policy so that it applies to every subscription of a department?

    Policies and role assignments are inherited downward, so a management group applies them to all subscriptions below it.
  4. 4. A deployment fails with a quota error for a VM family in a region. What is a reasonable fix?

    Quotas are per subscription, region and family. You can ask for more capacity or deploy elsewhere.

Summary

  • A tenant is the identity directory (Microsoft Entra ID); a subscription is the container for resources, limits and billing.
  • A subscription trusts one tenant; a tenant can have many subscriptions.
  • Management groups sit above subscriptions, and access and policy flow down through management group, subscription, resource group and resource.
  • Quotas and limits are per subscription and region; request increases or change sizes.
  • Always check which subscription is active before deploying.

Next: Portal, Azure CLI and PowerShell.