Governance and cost
Azure Policy
Evaluates resources against rules at create/update time and continuously (≈ AWS Config rules + SCP-like guardrails):
| Effect | Behaviour |
|---|---|
| Deny | Block non-compliant creates/updates (e.g. disallowed regions, public IPs) |
| Audit | Allow but report non-compliance |
| Append / Modify | Add or change properties (e.g. add tags, enforce settings) |
| DeployIfNotExists | Deploy a related resource if missing (e.g. diagnostic settings, Defender agents) |
| AuditIfNotExists | Report when a related resource is missing |
| Disabled | Off |
- Initiatives (policy sets) group policies (e.g. CIS benchmark, "allowed locations + required tags").
- Assigned at management group level they act as organisation-wide guardrails — the Azure answer to AWS SCPs (with deny effects), e.g. "allowed regions: Central India, South India".
- Tags: "Require a tag on resources", "Inherit a tag from the resource group" policies enforce cost-centre tags.
Resource locks
CanNotDelete (can modify, can't delete) and ReadOnly locks on subscriptions, RGs or resources prevent accidents — even Owners must remove the lock first. Use on production RGs, DNS zones, Key Vaults.
Landing zones
The Cloud Adoption Framework / Azure Landing Zones describe the reference enterprise setup: management group hierarchy, policy baseline, hub-and-spoke or Virtual WAN networking, centralised logging, identity — deployable via Terraform/Bicep modules (≈ AWS Control Tower + landing zone).
Cost management
Azure Cost Management + Billing: cost analysis by subscription/RG/tag, budgets with alerts, anomaly detection, Advisor recommendations. Savings: Reservations and Savings Plans (≈ RIs/Savings Plans), Spot VMs, auto-shutdown for dev VMs, right-sizing, deleting idle resources, Azure Hybrid Benefit for Windows/SQL licences.