Revisit a 2020 Azure cost response with today's controls

The original September 2020 article responded to sudden changes in cloud use and budget pressure during COVID-19. Its context is historical. The cost-management questions remain useful, but Azure features, prices, and recommendations have changed.

Use current Microsoft documentation and current billing data before making a cost decision. Microsoft’s Cost Management best-practices guide is a starting point for scopes, budgets, alerts, ownership, and review routines.

Start with a defined cost scope

Specify the billing scope, currency, time period, and services included. Compare like periods and separate expected growth, pricing changes, commitment effects, and unusual usage.

A total bill does not identify a safe action. Map each material cost to a workload, owner, service level, and business purpose.

Review recommendations with the workload owner

Azure Advisor can identify cost opportunities for resources such as virtual machines. Microsoft’s Advisor cost-recommendation documentation explains the current recommendation types and their inputs.

Treat a recommendation as evidence for review, not an instruction to apply automatically. Check performance, resilience, reservation or savings-plan commitments, licensing, maintenance windows, and future demand.

Schedule only workloads that can stop safely

Development, test, and other noncontinuous workloads may support scheduled shutdowns. Before applying one, confirm:

• the service supports the planned stop and start behaviour;
• data and queued work remain safe;
• dependencies restart in the correct order;
• monitoring distinguishes a schedule from an outage;
• an owner can override the schedule when needed.

The saving depends on the resource and billing model. Measure the result rather than retaining a generic percentage from an old article.

Turn alerts into an operating routine

A budget alert is useful only when someone owns the response. Define who reviews it, how quickly they respond, which evidence they need, and who approves a change that affects service.

Track accepted actions with an owner, expected effect, implementation date, and validation date. Recheck the cost and workload after the change. This makes cost control part of operations instead of a one-time cleanup.