Agent Credit Limits and Alerts - Copilot Studio

I build Vaze. One addition to Jamony's answer: check the environment's access to shared capacity, not only the individual agent's limit.

Microsoft's current guidance for agents using the GitHub Copilot harness says that per-agent limits don't cap aggregate environment consumption. For a prepaid boundary it describes allocating a defined amount, turning off 'Draw from the available capacity in my tenant', and not connecting that environment to pay-as-you-go.

https://learn.microsoft.com/en-us/microsoft-copilot-studio/guidance/govern-credit-consumption

That changes the review question from 'did this agent stop?' to 'can this environment keep consuming through other agents or the tenant pool?' Before changing allocation or billing settings, check every workload in that environment, because those settings affect more than the agent being investigated.

I'd include the environment's funding mode and a named cost owner in the incident review, alongside the agent limit and stop setting.