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.
