Which Azure budget needs action? A pace check you can do by hand

HosheBartar — Sun, 25 Oct 2026 14:15:33 +0000

Azure budget alerts tell you when a budget crosses a share of its amount: 50%, 80%, 100%. That is useful, but a 50% alert on day 25 of the month and a 50% alert on day 6 mean very different things. The second one is a problem; the first one is fine.

Here is a simple pace check you can do by hand for any budget, and then how we automated it.

1. List your budgets and their scopes

In the Azure portal, open Cost Management > Budgets. A budget is set on a scope (a subscription, a resource group, a management group or a billing scope), has an amount and a reset period, and sends alerts on actual or forecasted cost at the thresholds you set. A budget never stops anything: it measures and notifies.

Write down, for each budget: the scope, the amount, the period and the spend so far this period.

2. Compute two shares

For each budget:

Share used = spend so far / amount
Share of the period elapsed = days gone / days in the period

Example: a monthly budget of 1,000, day 12 of 30, spend so far 550.

Share used: 55%
Share of the period elapsed: 40%

The budget is not over, and it may not even have fired its first alert yet if you set it at 80%. But it is spending faster than the calendar: at an even pace it would be at 400, not 550.

3. Grade them

A grading that is easy to explain to a team:

Over: 100% or more of the amount spent.
At risk: 50% or more spent, but not all.
On track: less than 50% spent.
Ahead of pace: share used larger than share of the period elapsed, while the amount is not yet spent.

Sort the list with the worst first, and you know which budget to look at.

4. Keep the traps in mind

Cost arrives late. Azure cost data is usually a day or two behind, so "spend so far" is spend up to a day or two ago.
Currencies. If your subscriptions are billed in different currencies, never add the amounts together without an exchange rate you trust.
Do not prorate the amount. Compare the full amount with the spend so far; the pace check is a separate signal, not a forecast.

The automated way

I build CostGuard, an Azure cost tool for small SaaS teams on Azure Marketplace, and its Budgets page does this check for every budget. (Disclosure: I build CostGuard, so take this part as the maker's description.)

Each budget covers the whole workspace, a subscription, a resource group or a service, per day, week, month, quarter or year (calendar periods in UTC).
The This period column shows the spend, a bar of the share used with a mark at the share of the period elapsed, what remains or by how much it is over, and the day of the period ("Day 12 of 30").
Every budget is graded over, at risk or on track with the 50% and 100% rule above, and "Ahead of the period's pace" is shown when it applies. The list puts the most urgent first.
When no figure can be stated (no cost import yet, cost only in another currency), the row says why instead of showing zero.

CostGuard only reads your Azure data with the Reader role; it never changes anything in Azure.

Honest limits

Email alerts run against one budget only: the enabled monthly budget of the whole workspace. Every other budget shows its usage on the page and raises no alert.
"Ahead of the period's pace" compares two shares; it is not a forecast.
Each budget has one currency, and nothing is converted: cost in another currency is named, not added.
Budgets are on the Starter plan and up (5 on Starter, 20 on Growth, unlimited on Pro). There is a Free plan on Azure Marketplace, where the page shows a labelled sample.

The whole page, section by section: Budgets: see which budget needs action

How to see when your Azure Sponsorship credit will run out

HosheBartar — Fri, 23 Oct 2026 00:20:46 +0000

Azure Sponsorship credit doesn't end with a warning. It lasts until usage consumes the whole grant or until its end date, whichever comes first, and Azure doesn't publish the remaining balance to apps. If your startup runs on it, the useful question isn't "how much is left?" but "on what day does it run out at our current rate, and is that before the end date?"

Here is how to answer that by hand, and how we automated it.

1. Read the balance in the Sponsorships portal

The Azure Sponsorships portal shows the balance, but only to a person who is signed in. There is no app access, so no tool (ours included) can read that number for you.

Two things to keep in mind when you read it:

It is a snapshot. It tells you what is left, not when it will be gone.
Azure reports usage to apps about a day and a half late, so any estimate built from reported usage trails the portal slightly.

2. Work out the run-out day yourself

Three numbers are enough: the grant (its starting amount), the usage so far, and the number of days since the grant's first day.

average per day = used / days since the first day
days left       = (grant - used) / average per day
run-out day     = today + days left

Then compare the run-out day with the grant's end date:

Before the end date: you will start paying before the sponsorship ends. Time to look at what is growing.
After the end date: the grant will expire with credit unused. The unused amount is roughly the remaining credit minus the average per day for each day left until the end date.

A since-start average is simple and stable, but it reacts slowly: a cost jump last week moves the run-out day only a little. Redo the math regularly, and again after any new deployment.

3. Decide when someone should look

The moments that matter are 50%, 75% and 90% used, the day the run-out date moves before the end date, and 30 days before the end date if credit is still left. A spreadsheet and a calendar reminder will do, as long as someone owns them.

The automated way: CostGuard

(I build CostGuard, an Azure cost tool for small SaaS teams, sold on Azure Marketplace.)

Because the balance isn't available to apps, CostGuard estimates it. It reads the usage Azure reports for your connected Sponsored subscriptions from the grant's first day and prices it at the Sponsorship offer's rates. For each grant you track it shows:

the estimated run-out day at the current rate, and whether that is before the end date
estimated used and remaining, and the average use per day
the unused amount expected at the end date, if any

Workspace owners and admins get one alert when a grant reaches 50, 75 or 90% estimated used, is estimated fully used, will run out before its end date at the current rate, or ends within 30 days with credit unused.

Setup takes three steps: record the grant with its starting amount in USD and its end date, choose "Track usage" and enter the sponsorship's first day, then read the grant's outlook after the next check.

Honest limits

It is an estimate, not a balance read from Azure. Because of the reporting lag, the portal can show a little more usage.
Usage that has no Sponsorship price isn't counted, so the estimate can run low.
Only grants recorded in USD are estimated.
It needs only the Reader role on each Sponsored subscription and never changes anything in Azure.
Credit tracking is on the Growth plan and up.

The full walkthrough, with every field and state explained, is in the Azure credits help article.

DEV Community: HosheBartar

Which Azure budget needs action? A pace check you can do by hand

1. List your budgets and their scopes

2. Compute two shares

3. Grade them

4. Keep the traps in mind

The automated way

Honest limits

How to see when your Azure Sponsorship credit will run out

1. Read the balance in the Sponsorships portal

2. Work out the run-out day yourself

3. Decide when someone should look

The automated way: CostGuard

Honest limits