When you save, every seat dollar in the three reports and the Traffic Lights is re-priced the same minute, and the "assumption" marks turn into "counted". Reports already frozen, decks already exported and cards already delivered keep the figures they were made with.
set by your organization 4still the platform default 8
Your dollars stand on the $30 assumption until you save your own seat price above; the rest of the money dials are here.
Copilot seat price$30 a seat · the $30 assumption until you save yours
Monthly Cowork budget and enforcement$320,000 a month · Nudge near the cap · Budgets & requests
Measured billingnot connected — every credit dollar is a labeled estimate · Connections
Copilot renewal daterenews 31 December 2026 (the sample’s illustrative date)
Renewal “still need it?” surveyoff
Adoption goalno goal set
This is the illustrative organization, so nothing here is saved — in your own tenant each of these saves right here, in place, and the History tab keeps who changed it and when.
🎯 Adoption goal
A mirror to aim at, never a scoreboard. The Credit-readiness page tracks current-vs-goal.
% of paid seats active
📅 Copilot renewal date
The date every Frontier Firm run counts down to — the report frames the work as the before/after you walk into renewal with. Provided by you, always labeled as such.
counting down
📨 Renewal “still need it?” survey
Opt-in. Inside the window before your renewal, Aristo asks each seat-holder — on your existing one-a-day proactive cap — whether they still use their Copilot license. Answers are counted only as team totals (five-or-more), never per person, and the control-group is never asked. Feeds the Renewal-prep right-sizing number.
windowdays before renewal
🧢 Safe Cowork budget
Your organization’s funded monthly cap for metered Cowork — Aristo steers and alerts on it; the real spending stop lives in your M365 Admin Center. Surfaced on the Credit-readiness page. Set 0 to clear it.
$/ mo cap
🚦 Budget enforcement
What Aristo does when a team reaches the safe Cowork budget above. Steer at the cap sends new heavy asks to the route already included in your seat and alerts you — it never blocks Microsoft billing (hard spending limits live in your M365 Admin Center). Nudge near the cap only alerts you as a team nears it.
📊 Measured credit billing
Your IT person makes a read-only link to your Azure cost export; Aristo reads it to replace credit-dollar estimates with measured billing.
not connected — every credit $ is a labeled estimate
For your IT person: the steps and the paste box
Three steps:1. In the Azure portal → Cost Management → Exports, create a scheduled daily export of your actual cost to a storage container. 2. On that container, generate a read-only SAS URL — permissions Read and List only. 3. Paste it below. What that SAS grants: list + read on that one container and nothing else — no write, no delete, no other resource, no access to your tenant. Aristo only ever performs a GET. A write-capable or non-HTTPS URL is refused, not stored. It carries the expiry chosen for that link, it is revocable any time (regenerate the key in Azure, or Disconnect below), and Aristo never logs or displays it back to you. Nothing changes for anyone until it is connected — and if a read ever fails, every dollar falls back to the labeled estimate rather than showing a wrong number.
Give this link to an organization leader to paste in Settings › Money › Measured credit billing.
Pasted values are write-only — the SAS is never shown again after you save it.
📥 Measured group credits
Turn your per-group credit lights from a labeled estimate into a measured number. Two steps:1. In the Microsoft 365 admin center, go to Reports → Usage → Microsoft 365 Copilot → Credits and export the report. 2. Paste it below, or choose the file. What Aristo keeps: the billing-policy and agent totals — groups and things. What Aristo throws away: every person-level row in that file, discarded as it is read, before anything is stored. Aristo governs the aggregate; the per-person view already lives in your admin center, which is the right home for it. An unrecognized file is refused, not stored — every credit figure then stays on its labeled estimate rather than becoming a wrong number. Once measured, the organization light on Traffic Lights prices against the report's total, and the month is stamped from the report's own date; per-policy lights follow when a counted membership proves each policy's five-person floor.
no credits report handed over yet — group lights run on a labeled estimate
The file is read in your browser and sent once; Aristo stores only the group totals it parsed out of it.
⏱️ Month-to-date so far (optional)
Adds one extra line to Money: your Cowork spend month-to-date so far, refreshed intraday. Paste your Azure subscription id and grant the Aristo service principal the read-only Cost Management Reader role on it. This is not real-time and never replaces the export above — Azure cost data lags roughly 8–24 hours and reconciles at month end, so this figure under-states and can still move. The reconciled monthly export stays the record of truth. If the role is missing, Aristo shows the exact ask instead of a number.