Traffic Lights · your thresholds, not ours
Two lights are red. Seats first: 65.7% are active against the 75% floor you set.
counted from Microsoft license records · as of 24 September 2026
65.7%
floor 75%
active of 4,200 paid seats · your floor 75%
counted from Microsoft license records
as of 24 September 2026
1.31×
0.851.10
of pace · your red line 1.10× · the pool empties early
estimate — may under-count
as of 24 September 2026
1.06×
0.851.10
of budget pace · projected $44,580 this month
estimate — may under-count
as of 24 September 2026
0.78×
0.700.801.15
of allotment · under 0.70, 30% of the packs would expire before use
estimate — may under-count
as of 24 September 2026
Every month, keptMicrosoft's report keeps 30 days · hatched = estimate
AprMayJunJulAug
When a light turns worse
Connect the measured bill
The people you named get one card in Teams, that day. Aristo watches and warns. Hard limits stay in your Microsoft 365 admin center.
How this is measured
The measured dollars come from your Azure Cost Management export; until it is connected these lights run on a labeled estimate.
Estimates use Aristo-mediated consumption and may under-count. Seats are counted from Microsoft license records and the Copilot usage report.
Consumption source: Illustrative consumption scenario.
🗄️ History — every month since you connected
Microsoft's report keeps 30 days; Aristo keeps all of them.
No uploaded history has been measured yet. The spend chart below carries its recorded months and their own basis. Connect the Cost Management export or hand over a credits report in Settings.
📈 Your spend history
5 complete months of spend
$229,400
Apr
$238,650
May
$246,780
Jun
$258,420
Jul
$269,760
Aug
▩ hatched = estimate
Microsoft's admin report keeps 30 days of credit history — your history lives here.