The estate position, movement and open findings are composed here before the supporting detail.
Welcome back, Contoso
Here is what is happening across your Microsoft 365 and AI investments.
How these numbers are counted As of 2026-08-29
Platform health
Evidence & data — The pillars behind the score
Comparison
Every pillar behind the score has a counted reading this run, so the outline is closed all the way round.
Source & method
Aristo Frontier Scale over counted Microsoft signals.
Basis: Self-reported
Accessible data
| Pillar | Score | Basis |
|---|---|---|
| Adoption | 78/100 | Self-reported |
| Activation % | 68/100 | Self-reported |
| Security readiness | 88/100 | Self-reported |
Every pillar behind the score has a reading this run.
Evidence & data — The estate, run by run
Comparison
Each point is a run that was counted, not a sampled month, so the gaps between points are the gaps between counts. The axis is banded 50–90, so a five-point move on a hundred-point scale reads as one.
Source & method
Aristo Frontier Scale over counted Microsoft signals.
Basis: Self-reported
Accessible data
| Run | Frontier score | Activation — share of assigned seats active |
|---|---|---|
| 2026-05-01 | 62/100 | 68% |
| 2026-05-31 | 66/100 | 68% |
| 2026-06-30 | 70/100 | 68% |
| 2026-07-30 | 74/100 | 68% |
| 2026-08-29 | 78/100 | 68% |
The axis is banded 50–90; the figures here are the readings themselves, unbanded. Activation is the share of assigned seats with qualifying activity; bought-but-unassigned seats are outside that denominator. Idle spend is persisted per run as well and is deliberately not on this axis — it is dollars, and money drawn on a percentage scale is how a chart starts lying. The basis stated above is this run's; per-run provenance is not persisted, so an earlier point cannot be re-attributed. A run reading “not recorded” did not store that measure, and the line breaks across it rather than being drawn through it.
Top insights
4 raised from counted positions this run.
- 1,280 assigned Copilot seats are cold Savings opportunity $38,400 per month activation opportunity
- The estate moved 4 points up the Frontier Scale Adoption +4 points, now 78/100 (Advancing)
- 416 staff signed into unsanctioned AI apps this month Risk 416 staff, last 30 days
- Activate 1280 cold Copilot seats Roadmap One move recommended next, from your own counted position
Consumption over time
Metered spend per month, with each month carrying its own basis.
Evidence & data — Metered consumption by month
Comparison
A bar is solid when the month’s figure was read or counted, and hatched when it is a model. The hatched bars are the honest picture of when measurement began, and the open bar is this month so far — it is a shorter month, not a smaller one, and should never be read as a fall.
Source & method
Azure Cost Management export where connected; Aristo consumption envelope otherwise.
Basis: Labelled estimate
Accessible data
| Month | Spend | Basis | Complete month |
|---|---|---|---|
| Mar 26 | $229,400 | Labelled estimate | Yes |
| Apr 26 | $238,650 | Labelled estimate | Yes |
| May 26 | $246,780 | Labelled estimate | Yes |
| Jun 26 | $258,420 | Labelled estimate | Yes |
| Jul 26 | $269,760 | Labelled estimate | Yes |
| Aug 26 | $278,540 | Labelled estimate | No — month to date |
A month-to-date figure is a shorter month, not a smaller one, and must not be read as a fall.