What this is
Traffic Lights — a red/amber/green light on every way you pay for Copilot: pay-as-you-go credits, credit packs, your pre-purchase pool, and the seats themselves. The thresholds are yours, not Microsoft’s fixed credit alert.
What to do here
Create one light for the path you are actually on, set the amber and red percentages you would want to be woken for, and name the leaders who should get the Teams card when it worsens.
Not lit yet
Measured billing (Cost Management export)Connect the read-only export — until then every credit light runs on a labeled estimate →
Someone to tellName the leaders to alert on a policy below →
Real spending limits set at MicrosoftAristo alerts; only the M365 Admin Center can stop billing →
At least one spend policy — in place.
I stop at each section in turn. Press × or Escape to leave.
Your Copilot spend, in three colours
Every way you pay, on one page. Your thresholds, not ours.
You're in the illustrative scenario. These lights run on illustrative data and every control is read-only here — connect your tenant and they watch your real spend.
Aristo
I found one guardrail that needs you today.
65.7%
One spending path needs you today
Seats org-wide: 65.7% of 4,200 paid Copilot seats are genuinely active against your 75% floor
Adjust my thresholds →
4 of 4
Paths watched
each against a floor you named
65.7%
Seats active
Seats — the path that needs you first
4
Your policies
every one of them yours to define
Aristo comes to you
In Teams. The day a light worsens, the leaders you named get the card — you never have to come here to find out.
In Copilot. Aristo Spark is a Microsoft 365 Copilot agent — ask it inside Word, Outlook or Copilot Chat.
Consumption — what the credits are doing
Finance pre-purchase pool
Pre-purchase pool
Finance
estimate
Pre-purchase pool Finance team pacing 1.31×
1.31×
Pace
projected 28,128,540 credits
your amber 85% · red 110%
Sales pay-as-you-go
Pay-as-you-go
Sales
estimate
Pay-as-you-go Sales team pacing 1.06× budget
1.06×
Pace
projected $44,580
your amber 85% · red 110%
Engineering credit packs
Credit packs
Engineering
estimate
Credit packs Engineering team pacing 0.78× allotment
0.78×
Pace
projected 5,090,000 credits
your amber 80% · red 115%
📈 Your spend history
6 months kept
$229,400
Mar
$238,650
Apr
$246,780
May
$258,420
Jun
$269,760
Jul
$278,540
Aug
▩ hatched = envelope estimate
Microsoft's admin report keeps 30 days of credit history — your history lives here.
Licenses — same money, different clock
A seat nobody opens costs exactly as much as a credit you burn. So it gets the same light.
Copilot seat utilization
Seats
Whole org
counted
waste
Seats org-wide: 65.7% of 4,200 paid Copilot seats are genuinely active against your 75% floor
65.7%
Seats active
active of paid seats
your floor 75% active
How you pay
The three ways a Copilot credit bill reaches you
pay-as-you-go · packs · pre-purchase pool — and which portal owns each
💳 Pay-as-you-go
$0.01 per credit, billed in arrears, with no ceiling. Nothing stops it, so the only protection is noticing the run-rate early. This light watches your pace against a monthly budget you set.
Managed in: Billed to your Azure subscription; the billing policy lives in the Microsoft 365 admin center.
📦 Credit packs
25,000 credits for $200 per pack per month, and they do not roll over. Danger on both sides: a standalone credit policy that empties mid-month stops serving your users, and anything unspent evaporates.
Managed in: Bought in the Microsoft 365 admin center, allocated AND monitored only in the Power Platform admin center.
🏦 Pre-purchase pool (P3)
A one-year pool bought upfront. Unused credits expire at term end — so a pool that is drawing too slowly is a real loss, not a saving. This light watches both ends against your term dates.
Managed in: Provisioned and tracked in the Azure portal.
🧭 Four admin surfaces, one question — this page is the single pane those portals don't have.
Requests & approvals
A department asks; the approver sees the chargeback; approval assigns it; the lights track it.
Every request is priced in real dollars before anyone decides.
No pending requests.
Request more for your team
Policies
Set the thresholds — amber, red, and who gets told
your numbers, per spending path
🚦 Define your own colours
Every threshold on this page is yours. Your lights fire where you say they should.
Sales pay-as-you-go
Pay-as-you-go · Sales · amber 85% · red 110% · nobody notified yet
Engineering credit packs
Credit packs · Engineering · amber 80% · red 115% · nobody notified yet
Finance pre-purchase pool
Pre-purchase pool · Finance · amber 85% · red 110% · nobody notified yet
Copilot seat utilization
Seats · Whole org · amber 85% · red 110% · nobody notified yet
What amber, red and waste actually mean
percentages of pace, in plain words
Amber and red are percentages of pace — 100% means "exactly on budget by period end", so 110% means you are projected to finish 10% over. The waste pair works the other way: it is the share of a no-rollover allotment or an expiring pool that you are projected to leave unspent. Teams smaller than 5 people cannot be scoped.
📥 Team scopes above divide the org total by headcount — a labeled estimate. Hand over your Copilot credits report and each billing policy becomes a measured scope you can point a light at directly.
🛡️ The traffic light that can't become surveillance
Aristo governs the aggregate — org and team totals only, never a person. A team smaller than 5 people is never shown here at all.
And this is an alert, not a cap. Aristo watches and tells you; it never stops Microsoft's billing.
Where the real stop lives, portal by portal
M365 admin · Power Platform · Azure
The per-person bill already lives in your Microsoft 365 admin center's Copilot credits report (Reports → Usage → Microsoft 365 Copilot → Credits); that is the right home for it.
The real stop lives with Microsoft, and it lives in a different place for each path: tenant, group and user spending limits in your Microsoft 365 admin center; capacity-pack allocation and monitoring — plus per-agent Copilot Studio limits — in the Power Platform admin center; and your pre-purchase pool in the Azure portal. Knowing which door to walk through is half the job — this page tells you which one, and why, before you go.
Watch your own Copilot spend the same way.
Every threshold on this page is yours to define, per policy and per spending path. Aristo alerts and steers its own recommendations; only Microsoft’s admin-center spending limits stop billing.
Bands are computed from your own thresholds against 2026-08 consumption. Every figure carries its basis: measured from your Cost Management export, counted from your Microsoft licence records, or a labeled estimate that under-counts.
Aristo · enterprise AI estate control plane. Care, not surveillance — every number is aggregate. Sample data.