If you’ve held back on letting staff build agents in Copilot Studio because nobody could tell you what it would cost, this one’s for you.
Microsoft has added an item to the Microsoft 365 roadmap that brings Copilot Studio cost management into the Microsoft 365 admin center. Admins will be able to put supported Copilot Studio environments and agents under spending policies for Copilot Credits.
What’s actually changing
Copilot Studio cost management stays in the Power Platform admin center. The change is that it also appears in the Microsoft 365 admin center, as part of a wider Cost Management area for usage-based AI.
The first policies will apply to resources. Microsoft plans to let admins set spending limits on environments and on individual agents. Support for user and group policies for these resources is planned for a later phase.
Microsoft also says cost data for AI services and agents built on its platforms will feed into cost management and the agent registry. That should help you see what an agent costs alongside the inventory of agents you already have.
The roadmap lists general availability for October 2026 on the worldwide cloud. The entry still says “In development”, so treat that date as a target. Check your own admin center before building a pilot around it.
What this means for a pilot
If your pilot uses pay-as-you-go billing, a surprise invoice in March has to come out of something else. A head of IT might see the potential of an agent that answers policy questions or drafts parent letters. The business manager still needs an answer to “What’s the worst case?”
A spending policy could help you give one. Show the business manager which resources the limit covers and what the service does when the agent reaches it. Check that behaviour before promising a ceiling on the whole bill.
What a cap won’t do
A spending policy can limit usage. What an agent can see and say needs its own checks.
An agent connected to the wrong SharePoint site can surface the wrong documents, however small its budget. Before the pilot, check access using a staff account with the permissions your users will have. Ask your data protection lead whether the proposed use needs a data protection impact assessment, and name someone to review the output.
If you want different limits for the curriculum team and the business office, check which agents or environments each team will use. Don’t assume the first release will let you set a limit against the team itself.
What to do next
- Check who can create agents in your tenant. If it’s everyone, decide whether that’s what you want.
- Consider a dedicated environment for the pilot so you can identify its use and apply the relevant policy when it’s available.
- Agree a monthly limit with your business manager and write it down.
- Name an owner for every agent. If nobody owns it, it shouldn’t be live.
- Check the Microsoft 365 admin center for the new settings before switching on usage-based billing.
For trusts, there’s a decision to make before the first invoice arrives. Does each school carry its own agent costs, or does the central team hold the budget?