Copilot Cost Management is the dashboard every Microsoft 365 admin relies on to keep Copilot Credits under control, and starting July 22, 2026, Microsoft is shipping a set of updates that change how it behaves. If you manage spending policies for Cowork or Work IQ APIs, this is not a change you can skip past in your inbox. Some of it fixes real bugs. Some of it requires you to take action before your existing safeguards silently disappear.
This article breaks down what is changing in Copilot Cost Management, who is affected, what you need to do this week, and why the change matters more than the message center summary lets on.
What and Why: The Problem Microsoft Is Fixing in Copilot Cost Management
Since the initial release of Cost Management, Microsoft has collected feedback and bug reports from tenants running usage-based billing for Copilot Credits. The result is a bundle of enterprise-ready fixes rolling into Copilot Cost Management starting July 22, 2026, expected to complete by the end of July.
Four things are changing:
- Increased reliability of spending alert emails
- Updated spending policy selection logic for users assigned to multiple policies
- Improved overage handling for per-user and group spending limits
- Clarified Copilot Credit availability from capacity packs across admin centers
Each one on its own sounds minor. Together, they close a set of gaps that made Copilot Cost Management unpredictable for admins running more than a handful of spending policies.
Spending Alerts in Copilot Cost Management Were Not Saving Reliably
The first fix addresses something admins have quietly been fighting for weeks: spending-alert thresholds that would not save, or that reset after being entered. If you configured an alert on a spending policy and never got notified when it triggered, this bug is almost certainly why.
Here is the part that matters most. As part of this update, existing spending-alert values are cleared and cannot be restored. Spending limits and per-user limits are not touched, only the alert values themselves. Admins must go back into every spending policy where alerts matter and recreate them from scratch.
Rollout Schedule for Copilot Cost Management
| Phase | Date | What happens |
|---|---|---|
| Rollout begins | July 22, 2026 | Updates start deploying to Copilot Cost Management across tenants |
| Rollout complete | End of July 2026 | All four fixes expected to be live for every tenant |
| Overage change effective | July 22, 2026 | Per-user overage stops drawing from the shared group pool going forward only |
There is no separate Preview phase for this update. Microsoft is rolling it directly to general availability across admin centers.
Policy Selection Logic: What Happens When a User Sits in Multiple Policies
If you have users assigned to more than one spending policy for the same service, Copilot Cost Management now applies a clear, predictable order instead of a mixed or unclear result:
- The policy with the highest per-user limit wins
- If tied, the policy with the largest overall policy limit wins
- If still tied, the most recently created policy wins
Once a user is assigned this way, the full policy applies, billing setup and limits included. Settings from the other policies the user technically belongs to are not blended in. And once a user hits their limit, they stay on that policy rather than getting silently reassigned somewhere else mid-month.
Why Policy Selection Logic Was a Governance Headache
Before this fix, admins had no reliable way to predict which policy actually governed a given user when multiple applied. That made budgeting and chargeback reporting a guessing game. The new deterministic order means you can now audit exactly which policy is active for any user, which matters if finance is asking why Copilot spend does not match expectations.
Overage Handling: Per-User Spend No Longer Hits the Group Pool
This is arguably the most consequential change in the whole update. Previously, if a user was within their per-user limit when a task started, the task was allowed to finish even if it pushed them past that limit during execution. That overage then drew against the shared pool at the group level, quietly consuming capacity meant for the rest of the team.
Starting July 22, 2026, at Microsoft’s discretion, per-user overages no longer draw against the shared group pool. These overages are not billed and will not appear as consumed credits in the Copilot Cost Management dashboards. This applies going forward only. Any per-user overage incurred before July 22 remains billable up to the spending policy’s configured monthly limit.
Capacity Pack Visibility Gets Clearer
The fourth change targets admins who purchase Copilot Credits through capacity packs and manage usage across both the Microsoft 365 Admin Center and Power Platform Admin Center. Three specific tweaks are rolling out:
- The Prepaid capacity pack credits used tile in the Overview tab will show only the amount used, not the total purchased
- A new tooltip on that tile will point admins toward reviewing capacity allocation and usage in other admin centers
- On the Billing Method page, the number of credits available from capacity packs will reflect what is actually available for use, excluding anything pre-allocated in Power Platform Admin Center to environments or agents
Copilot Credits from capacity packs can be consumed by multiple services managed across both admin centers, so this update is about giving admins an honest number instead of a total that does not reflect what is really left.
Action Required: What to Do This Week in Copilot Cost Management
Microsoft’s message center post lists four recommended actions. Here is the practical version.
1. Recreate Every Spending Alert (Required)
This is not optional. Go into each spending policy where you rely on alerts, re-enter the threshold, and confirm it saves. Do not assume your old configuration survived the update.
2. Audit Users in Multiple Spending Policies
Check where users overlap across policies for the same service, then confirm the resulting assignment under the new selection order matches what you actually intended. If it does not, adjust the per-user limits or restructure the policies.
3. Re-Check Group and Per-User Limit Configurations
No action is strictly required for the overage change to take effect, but this is a good moment to confirm your per-user and group spending limits still reflect the guardrails you actually want going forward.
4. Reconcile Capacity Pack Usage Across Admin Centers
Because Copilot Credits from capacity packs are consumed in both the Microsoft 365 Admin Center and Power Platform Admin Center, check Power Platform Admin Center to see how much prepaid capacity is already allocated to environments or agents before you assume Copilot Cost Management is showing you the full picture.
Admin Tips for Copilot Cost Management
These are the practical habits worth building around Copilot Cost Management now that this update is live.
- Set a calendar reminder to check spending alerts again in early August, after rollout completes, in case any policy was missed
- Document which policy wins for each overlapping user before the new selection logic kicks in, so you have a baseline to compare against
- Loop in whoever manages your Power Platform Admin Center capacity allocations, since Copilot Cost Management now depends on that data being accurate
- Treat this as a trigger to review your overall Copilot Credits governance model, not just a bug fix to acknowledge and forget
License Check
This change applies to any Microsoft 365 tenant using Copilot Credits through usage-based billing for Cowork and Work IQ APIs, whether funded through prepaid capacity packs or pay-as-you-go billing. No additional license or add-on is required to see these Copilot Cost Management updates. If your organization has not enabled usage-based billing, none of this affects you yet, but it is worth understanding before you do.
The Paul-Take
Copilot Cost Management is still young, and this update proves it. Microsoft is fixing real bugs here, not just polishing the UI, and the fact that spending alerts were silently failing to save is the kind of thing that should worry any admin who assumed their guardrails were working. The overage fix is the quiet win in this release. Letting per-user overage drain the group’s shared pool without billing for it was never sustainable, and closing that gap protects budgets that were being eaten by edge cases nobody was watching.
My advice: do not treat this as a routine message center item to skim and archive. Block twenty minutes this week, go through every spending policy with an alert configured, and recreate the thresholds by hand. Microsoft is clear that old values cannot be restored. If you skip it, you will not find out your alerts are broken until the spend already happened.
This should be rolling out from July 22, 2026 according to Microsoft, with full rollout expected by end of July 2026.
If you are already deep into Copilot governance, this pairs well with what we covered in Agent 365 Dashboard: Smart New View for Managers, and if you have not yet handled the OpenAI subprocessor action item, read Copilot OpenAI Subprocessor: Action Needed by July 24 before your deadline passes.