Subscriptions and Billing Basics

Understand Azure subscription boundaries, billing basics, cost visibility, and budget controls at a practical starter level.

What is it? (Simple Explanation)

A subscription is both a billing container and an access boundary for Azure resources.

Why do we need it?

• Separate costs by team/project.
• Apply access and policies cleanly.
• Track usage and control spending.
• Support governance and reporting.

Real-world Analogy

Subscriptions are like separate corporate expense accounts. Teams can spend within assigned limits and reporting stays clear.

How it works (Technical)

Resources are created inside subscriptions. Cost analysis aggregates usage. Budgets trigger alerts at thresholds. Tags improve showback/chargeback-style reporting.

Visual Representation

Commands / Syntax

az account list --output table
az account set --subscription "My Subscription"
az consumption usage list --top 5

Example (Real-world Use Case)

A company runs separate subscriptions for Dev, Test, and Production so spending and access are isolated and easy to audit.

Hands-on

1. List all subscriptions available to your account.
2. Switch active subscription context.
3. Open Cost Management and view last month trend.
4. Create a budget alert threshold (for practice).
5. Compare tagged vs untagged cost visibility.

Try It Yourself

Create a basic cost governance checklist for a new project subscription.

Debugging Scenario

Issue: Unexpected cost spike. Approach: identify top resource contributors, check recent deployments, verify autoscaling or misconfigurations.

Interview Questions

Real-world Usage

Subscription strategy is a practical governance lever that impacts both security boundaries and cloud cost management quality.

Summary

Treat subscriptions as organizational building blocks. Combine them with budgets and tagging for predictable cloud operations.