Forum Discussion
MB12345
Oct 05, 2026Copper Contributor
Agent Credit Limits and Alerts - Copilot Studio
Hi everyone, We're evaluating the use of Agent Credit Limits and alert notifications in the Power Platform Admin Center as a way to control unexpected Copilot Credit consumption. Recently, we had a...
sohnash
Oct 18, 2026Iron Contributor
Hello MB12345 , here is what I'd recommend to set tight controls. Of course with time, some of these settings can evolve/change and we'd have to adapt.
Approach
- Set limits at environment level
- Set limits to specific agents (if needed)
1 - Set credit limits to "Production" environments
- Depending on your environment strategy, set X number of credits in the environment capacity. For e.g. if you have Production environments where you know Y number of agents are deployed, based on the estimates, allocate the number of credits.
- Make sure that "Draw from the available capacity in my tenant" is unchecked - this way, you can control that agent(s) don't consume beyond the X number of credits assigned to the environment
2 - Set credit limits to "Developer" environments
- If you don't want Developer environments to use usage based billing elements like GitHub Copilot harness, make sure that you don't assign any credits to these environments & also turn off "Draw from the available capacity in my tenant".
- If you want some Developer environments to use usage based billing elements like GitHub Copilot harness, then assign credits to the selected environments accordingly. I'll still recommend keeping "Draw from the available capacity in my tenant" as off here too
- For this case, I'd additionally recommend checking which agents are using GitHub Copilot harness so you can check with the Makers if this was an intentional choice or an accidental one. Here you can guide your Makers to choose the right harness to build agents. I've seen multiple instances where Makers chose the GitHub Copilot harness because that was the most obvious button on the screen & they didn't have a legitimate use case for this. All they wanted was to build basic agents.
3 - Set credit limits and notification at Agent level
- With (1) and (2), you are sort of already covered. But if you have a case where there are multiple agents running in the same Production environment, you might want to set limits at the "Agent" level so you don't let one Agent use up all credits. This really depends on what agents are live and what they are doing.
- Also, set "overage notification" so you will get notified when the agent is nearing capacity usage. Setting it to 80% is a good number