1. Make the bill readable in Cost Management
Group spend by subscription, resource group and tag. Agree a tag standard for client, project and environment, and use Azure Policy to require it on new resources. Review Azure Advisor cost recommendations as a starting list, not a final answer.
2. Apply Azure Hybrid Benefit
If you own Windows Server or SQL Server licences with Software Assurance or qualifying subscriptions, Azure Hybrid Benefit lets you use them in Azure and pay a lower base rate. For Microsoft-stack agencies this is often the single largest saving, and it requires no technical change.
3. Move non-production to Dev/Test pricing
Eligible Visual Studio subscribers can use Dev/Test subscriptions with discounted rates for many services. Combine this with auto-shutdown schedules on development VMs to remove most out-of-hours cost.
4. Consolidate App Service plans
You pay for App Service plans, not apps. Many agencies create one plan per client site. Grouping low-traffic sites onto shared, correctly sized plans, while keeping busy or sensitive apps separate, often halves App Service spend.
5. Right-size virtual machines
Compare VM utilization against size. B-series burstable VMs suit low-average workloads; newer Dv5 and Ev5 families offer better price-performance than older generations. Use scale sets with autoscale for variable load.
6. Choose the right Azure SQL model
Place several low-utilization databases in an elastic pool to share capacity. Use serverless with auto-pause for databases used intermittently. Review DTU versus vCore models and remove geo-replication from non-critical databases.
7. Reserve what is stable
After right-sizing, buy one- or three-year reservations for steady VMs, SQL databases and other eligible services, or use an Azure savings plan for compute where flexibility matters more.
8. Fix storage redundancy and tiers
Match redundancy to need: not every backup requires geo-redundant storage. Move infrequently accessed blobs to Cool, Cold or Archive tiers with lifecycle management, and clean up old managed disk snapshots.
9. Keep it down with budgets and policy
Set budgets per subscription with alerts, enforce tags with Azure Policy and review the top movers monthly. Savings that are not governed tend to return within two quarters.
Where Azure savings typically come from
| Lever | Typical saving on that line | Effort |
|---|---|---|
| Azure Hybrid Benefit | Significant on Windows/SQL workloads | Low |
| Dev/Test pricing and auto-shutdown | 40–70% of non-production | Low |
| App Service consolidation | 30–50% | Low–Medium |
| VM right-sizing | 20–45% | Medium |
| SQL elastic pools and serverless | 25–40% | Medium |
| Reservations and savings plans | Varies by term and service | Low |
Checklist
- Tags enforced with Azure Policy
- Hybrid Benefit applied to eligible VMs and SQL
- Non-production on Dev/Test pricing with auto-shutdown
- App Service plans consolidated
- VMs right-sized to current generations
- Azure SQL in pools or serverless where appropriate
- Reservations sized after right-sizing
- Storage redundancy and tiers reviewed
