Microsoft Azure
Cost Management & the Well-Architected Framework
Cut Azure spend without cutting capability — lead with licences the organisation already owns, then commitments, dev/test pricing and enforced tagging.
The Azure Well-Architected Framework has five pillars, and they do get asked by name.
Moving into a furnished flat and paying rent on its furniture while your own sits in storage. Hybrid Benefit is bringing your own sofa — and auto-shutdown is remembering to turn the heating off when nobody is home.
Key Concepts
1
Reliability recover from failure, meet demand
Security identity, data protection, detection
Cost Optimisation avoid unnecessary spend
Operational Excellence deploy and monitor well
Performance Efficiency use the right resources2
Pricing levers, roughly in order of saving.
pay-as-you-go no commitment, highest rate
Reservations a specific VM size or service for 1 or 3 years
savings plan commit $/hour across compute services
Spot VMs spare capacity, deep discount, evictable
Azure Hybrid Benefit reuse Windows Server and SQL Server licences
the organisation already owns3
Hybrid Benefit is the Azure-specific answer, and worth leading with. Organisations moving from on-premises often already pay for Windows Server and SQL Server licences with Software Assurance; applying them removes the licence portion of the Azure price, which for Windows and SQL workloads is a large share of the bill.
4
Dev/Test pricing is the other Azure-only lever. Non-production subscriptions on a Dev/Test offer pay no Windows licence charge and discounted rates on several services — provided they really hold no production workloads.
5
Reservations and the savings plan answer different questions. A reservation is the deeper discount for something you know will not change size or region; the savings plan is shallower but follows the spend across VM families, regions and services.
6
Where Azure spend leaks.
oversized VMs Advisor rightsizing
managed disks with no VM the VM was deleted, the disk kept
public IPs and NICs left behind small, and they add up
Premium SSD under idle data cheaper disk tiers exist
dev and test running all night auto-shutdown fixes it7
Make the tags mandatory, then let them flow. Azure Policy can deny resources created without costCenter or env tags, and Cost Management's tag inheritance applies subscription and resource-group tags to usage records — so even resources that cannot be tagged are attributed.
costCenterenv
8
Budgets can act, not just email. A budget alert can trigger an action group — an automation runbook or a Logic App — when forecast spend crosses a threshold.
9
What the interviewer is probing.1. "What is the largest Azure-specific saving for an organisation migrating from on-premises?" Probing: Hybrid Benefit. Stalls: "Reserved instances." Moves up: Azure Hybrid Benefit — applying the Windows Server and SQL Server licences they already own, which removes the licence part of the price.
10
2. "Reservation or savings plan?" Probing: the trade between the two. Stalls: "Whichever is cheaper." Moves up: a reservation when the size and region are stable, for the deeper discount; the savings plan when the estate keeps changing shape, accepting a smaller discount for flexibility.
11
3. "How do you make sure every resource can be charged back to a team?" Probing: enforcement. Stalls: "Ask people to tag things." Moves up: an Azure Policy assignment that denies untagged resources, plus tag inheritance in Cost Management so usage is attributed even where tags were missed.
12
4. "How would you cut the cost of development environments without hurting developers?" Probing: Azure's non-production levers. Stalls: "Use smaller VMs." Moves up: move them to Dev/Test subscriptions, schedule auto-shutdown outside working hours, and use Spot for disposable build agents.