If you build something in Copilot Studio App “Builder,” Microsoft spins up a dedicated environment for it immediately. If you build an Agent in Copilot Studio instead, nothing comparable happens.
An environment isn’t just a container — it’s the unit Microsoft gives admins to actually govern something: scope a DLP policy to it, apply a capacity allocation to it, set a budget on it, shut it down on its own without touching anything else. Give something its own environment and you get a lever. Don’t, and you don’t.
Get hands on and get control
Copilot Studio agents consume tokens, and those tokens cost money. If each agent landed in its own environment the way an App Builder app does, you could cap token spend per agent, per team, or per environment, the same way you already manage capacity elsewhere in the Power Platform.
Instead, every self-service agent a user creates in Copilot Studio draws from the same undifferentiated pool. There’s no per-agent boundary to attach a budget to.
If you havent’t already, go into M365 Admin Center Cost Management for Copilot and Power Platform admin Center Licensing and see what and who consumes token in your tenant.
Microsoft Ignite is coming!
That being said, I expect some news coming out of Microsoft Ignite with regards to cost management for AI.
Worth flagging also: Grey Matter reported that from 1 December 2026, usage-based billing becomes the default for new Copilot Business licences, with Partner Center auto-provisioning the Azure billing setup and a default spending policy at purchase. I can’t find anything on this in Message Center myself, so my guess is the blogger picked it up from tracking changes to Microsoft Learn articles rather than an official announcement feed. If it lands the way it’s described, this is likely a much better way to actually track and cap token budgets than the single tenant-wide “personal productivity” number — assuming it ends up granular enough to scope per agent rather than just per user.
Leave a Reply