Subscriptions as Billing and Access Boundaries
An Azure subscription is a logical container that groups resources together for billing and access management, tied to one Azure Active Directory (Microsoft Entra ID) tenant. Every resource group, and every resource within it, belongs to exactly one subscription, and subscriptions are the unit at which Microsoft generates an invoice. Larger organizations frequently use multiple subscriptions — for example, separating Production, Development, and Sandbox environments — because subscriptions also act as a hard boundary for resource quotas (like maximum VM cores per region) and role-based access control, meaning access granted at the subscription level cascades down to every resource group and resource inside it unless explicitly overridden.
Cricket analogy: A subscription is like a franchise's overall budget account in the IPL auction — every player (resource) purchased draws from that one team's purse, and the team's total spending is what gets reported at season's end.
Cost Management and Budgets
Azure Cost Management + Billing lets you analyze spend by resource, resource group, tag, or service, and set budgets that trigger email alerts or automated actions (via Action Groups) when spending crosses a threshold, such as 80% or 100% of a monthly limit. Cost analysis relies heavily on resource tags — key-value pairs like CostCenter: Marketing or Environment: Dev — applied consistently across resources, since without tagging it becomes very difficult to attribute shared subscription costs back to individual teams or projects. Azure also offers Azure Advisor cost recommendations, which flag underutilized resources such as an oversized VM running at 5% CPU, and reservation or savings-plan options that trade a one- to three-year commitment for a discount of up to roughly 70% compared to pay-as-you-go pricing.
Cricket analogy: Setting a budget alert is like a franchise's finance team getting notified the moment auction spending crosses 80% of the team's salary cap, well before the full purse is exhausted.
Tagging and Budget Automation
# Tag a resource group for cost attribution
az group update \
--name myFirstRG \
--tags CostCenter=Marketing Environment=Dev
# Create a monthly budget with an alert at 80% of the limit
az consumption budget create \
--budget-name monthly-dev-budget \
--amount 500 \
--category cost \
--time-grain monthly \
--start-date 2026-07-01 \
--end-date 2027-06-30 \
--notifications '{"Actual_GreaterThan_80_Percent":{"enabled":true,"operator":"GreaterThan","threshold":80,"contactEmails":["finance@example.com"]}}'Reservations and savings plans require an upfront one- or three-year compute commitment in exchange for a substantial discount versus pay-as-you-go pricing, and are best applied to steady-state workloads whose baseline capacity is predictable — not to spiky or short-lived workloads.
Subscription Types and Support Plans
Azure offers several subscription types, including Free (a limited-time trial with credit), Pay-As-You-Go (billed monthly for actual consumption), and Enterprise Agreement (a negotiated contract for large organizations with committed annual spend). Separately from the subscription type, customers choose a support plan — Basic (free, included by default), Developer, Standard, or Professional Direct — which governs response time SLAs for support tickets and access to proactive guidance; a production-critical workload typically warrants at least a Standard plan, since the free Basic plan offers no guaranteed response time for technical issues.
Cricket analogy: Choosing a subscription type is like a cricket academy picking between a free trial session, pay-per-lesson coaching, or a season-long enterprise contract with a professional academy — the commitment level determines both cost and the level of dedicated support received.
The free Basic support plan, included by default with every subscription, offers no guaranteed response-time SLA for technical support tickets — it covers billing and subscription questions only. Production workloads should use at least a Standard support plan.
- A subscription is a logical container for billing and access, tied to one Microsoft Entra ID tenant.
- Every resource group and resource belongs to exactly one subscription, which is the unit of invoicing.
- Resource tags like CostCenter or Environment are essential for attributing shared costs to teams or projects.
- Budgets in Cost Management can trigger email alerts or automated actions at spending thresholds like 80%.
- Reservations and savings plans trade a 1-3 year commitment for discounts up to roughly 70% versus pay-as-you-go.
- Subscription types include Free, Pay-As-You-Go, and Enterprise Agreement, each suited to different scales.
- Support plans (Basic, Developer, Standard, Professional Direct) are separate from subscription type and govern support SLAs.
Practice what you learned
1. What identity boundary is every Azure subscription tied to?
2. What is the primary purpose of applying tags like CostCenter or Environment to resources?
3. What do Azure reservations or savings plans require in exchange for a discount?
4. What does the free Basic support plan cover?
5. What happens when spending crosses a configured budget threshold in Azure Cost Management?
Was this page helpful?
You May Also Like
What Is Microsoft Azure?
An introduction to Microsoft Azure as a public cloud platform, covering its core service models and why organizations adopt it.
Azure Global Infrastructure
How Azure organizes its worldwide data centers into regions, availability zones, and region pairs to deliver performance and resilience.
The Azure Portal and CLI
A practical comparison of the Azure Portal's graphical interface and the Azure CLI for managing resources, including when to use each.