A weekly Azure cost-review checklist for small teams

Choose one owner and a recurring review time. Each week, check whether the data is current enough to compare, identify the largest changes, and give each unexplained change an owner and follow-up date. You can do this with Azure Cost Management and a shared note; no CostRadar account is required.

A weekly review is a baseline, not protection against rapid spending. Microsoft recommends checking costs more frequently after resource changes. Use service monitoring and an incident process for urgent operational problems; delayed cost data is not a substitute.

1. Confirm what you are reviewing

Open Cost Management → Cost analysis with permission to view the intended scope. Record the subscriptions or billing scope, currency, filters, and cost basis. Use the same settings each week or explain why they changed.

Check the latest available data before comparing periods. Prefer equal-length periods with similar weekdays and sufficiently reported usage. Recent dates can still change after the review. Keep missing or delayed data marked as unknown, not zero.

If you use CostRadar, inspect the latest usage date covered and import status. A recent export check does not prove that Azure published newer data or that an import completed. See why cost data can be delayed.

2. Review the changes, not just the total

• Review the current month's reported cost and any forecast separately. A forecast is not an invoice or a guaranteed outcome.
• Group costs by service, then investigate the largest changes by resource group, resource, or meter where available.
• Ask whether a change was expected from a deployment, usage increase, tier change, or purchase.
• Review newly appearing costs and unexplained decreases too. A decrease can be delayed reporting, not a saving.
• Keep Actual cost and Amortized cost comparisons separate. Use finalized billing records for invoice reconciliation.

Do not limit investigation to a percentage alone. A large percentage on a tiny amount may be unimportant, while a smaller percentage on a major workload can matter. Agree on significance with the people responsible for the budget.

For an unexplained increase, follow the Azure bill investigation guide.

3. Check who will respond to alerts

Confirm budget scope, filters, thresholds, expiration, recipients, and the backup owner. Record whether any expected alert was actually received rather than assuming configuration proves delivery.

Azure budget alerts do not stop spending. Decide who investigates a warning and who has authority to approve a production change. Do not silently assign that responsibility to a dashboard or an email inbox.

4. Make one accountable follow-up per issue

For each issue, record an explanation or a concrete investigation step, an owner, and a review date. Review service recommendations against workload needs rather than applying them solely because a cost-saving estimate is displayed.

Before stopping, resizing, or deleting resources, check dependencies, availability requirements, data protection, and recovery. Later, verify the result in updated billing data on the same comparison basis. Record observed changes, not promised savings.

Copy this review note

• Review date and owner:
• Scope, currency, cost basis, and filters:
• Comparison periods and data-freshness limitations:
• Current reported cost; forecast if used, labeled separately:
• Significant change and supporting cost view:
• Explanation confirmed, or question still open:
• Budget and notification checks:
• Approved next action, owner, and follow-up date:
• Prior action result, with evidence or a pending-data note:

Keep this note in your team's private workspace. Redact account identifiers and billing details before sharing screenshots or exports outside the team; never include secrets.

When another tool may help

If the review is consistent and Azure's built-in views meet your needs, keep using them. If collecting the information and following up is being missed, CostRadar's overview describes its monitoring workflow. It does not replace ownership, Azure billing records, or safe change approval.

Source

• Microsoft: Start using Cost Analysis, including its weekly review and post-change monitoring guidance.