Governance and Compliance notes on Azure Subscriptions, Accounts, Regions, and Cost Management:

1. Azure Regions

• Definition: A geographical area containing at least one, often multiple, datacenters connected via low-latency networks.

• Examples: West US, Canada Central, West Europe, Australia East, Japan West.

• Coverage: 50+ regions in 140 countries.

• Purpose:

  • Bring applications closer to users.

  • Ensure compliance and resiliency.

  • Preserve data residency requirements.

• Deployment: Most Azure resources require you to select a region; some services (Azure AD, Traffic Manager, Azure DNS) are global and region-independent.

Regional Pairs

• Two regions within the same geography, e.g., West US + East US.

• Benefits:

  • Physical isolation (typically 300+ miles apart).

  • Platform-provided replication (e.g., Geo-Redundant Storage).

  • Sequential updates to reduce downtime during maintenance.

  • Recovery priority: One region is prioritized in case of outages.

  • Compliance: Ensures data residency laws are met.

• Exception: Brazil South pairs with a region outside its geography.

References:

• Azure Regions Map

• Region Pairs List

2. Azure Subscriptions and Accounts

Azure Account

• Identity in Azure AD or trusted directory (work, school, or Microsoft account).

• Used to authenticate before accessing Azure resources.

Azure Subscription

• Logical container for Azure services.

• Billing and usage tracked per subscription.

• Can be organized by department, project, or region.

• Each subscription has a unique subscription ID.

Acquiring Subscriptions

1. Enterprise Agreement: Upfront monetary commitment, 99.95% SLA.

2. Reseller/Open Licensing: Buy via Microsoft reseller.

3. Microsoft Partners: For design and implementation support.

4. Personal Free Account: Free trial with $200 credits for 30 days.

Common Subscription Types

3. Cost Management

• Purpose: Monitor, analyze, and optimize Azure spending.

• Tools & Features:

  • Cost Analysis: Explore usage, identify trends, estimate monthly/quarterly/yearly costs.

  • Budgets: Set thresholds, monitor spending, send notifications (does not stop resources).

  • Recommendations: Identify idle/underutilized resources and cost-saving options.

  • Export Data: Export daily usage data (CSV) for external systems.

Cost-Saving Options

• Reservations: Pre-pay 1-3 years for VMs, SQL, Cosmos DB, etc., saving up to 72%.

• Azure Hybrid Benefit: Use existing on-prem licenses to save on Windows Server & SQL Server.

• Azure Credits: Monthly credits for development/testing (e.g., Visual Studio subscriptions).

• Regional Pricing: Azure prices can vary by region—check multiple regions.

• Budgets & Pricing Calculator: Plan, monitor, and estimate costs.

4. Resource Tags

• Purpose: Logically organize resources by categories (e.g., Environment=Production).

• Use Cases: Retrieve related resources across groups; group billing data by tags.

• Constraints:

  • Max 50 tags per resource or resource group.

  • Tags on a resource group are not inherited by resources.

✅ Key Takeaways

• Regions and regional pairs are critical for resilience, compliance, and disaster recovery.

• Subscriptions are central for access, billing, and resource organization.

• Cost management tools help optimize spending, plan budgets, and enforce accountability.

• Resource tagging provides flexible organization and cost tracking.