Message center post MC1458282 announces a new environment group rule reaching general availability on August 26, 2026: Cost controls, Draw from tenant credit pool. Microsoft classifies it as awareness only, no action required. That classification is accurate in the narrow sense that nothing breaks when it ships. It is misleading in the sense that matters, because this is the first rule in environment groups that governs money, and the default it exposes is the permissive one.
If you have Copilot Studio agents running in more than a handful of environments, this is the most consequential admin center change of the month for your budget.
What the rule does
The rule controls a single setting: whether environments can draw from the available capacity in the tenant when they reach their credit allocation, or when they have no allocation set at all.
That setting already existed. It lives at the environment level under capacity overage management, labelled Draw from the available capacity in my tenant, and it has been configurable one environment at a time in the admin center or scriptable through Power Platform API methods. What is new on August 26 is that you can publish it as an environment group rule.
Per the message, the setting is enabled by default at the environment level. Disabling it limits the credits an environment can use each month. When the rule is published for a group, it applies across every environment in that group and can no longer be changed at the individual environment level. To retain per environment control, you either do not apply the rule to that group, or you move the environment outside the group.
Why the default matters more than the feature
Read the qualifying clause again: when they reach their credit allocation or have no allocation set.
Most administrators reason about Copilot Credits the way they reason about licenses. An environment with credits assigned is a consumer. An environment with nothing assigned is not. That intuition is wrong here, and the second half of that clause is why. An environment with no allocation is not a zero spend environment. By default it is an uncapped one, drawing from whatever the tenant has available.
To see why that compounds, it helps to look at the shape of the underlying model. When you purchase a Copilot Studio license, you receive a number of billed Copilot Credits pooled across the tenant, and you assign those credits to environments to enable Copilot Studio features for agents there. Capacity replenishes monthly and unused credits do not carry over. A credit represents a single interaction that prompts a response or action.
So the pool is shared, finite, monthly, and by default every environment has an unmetered straw in it. That is a textbook commons problem, and it behaves the way commons problems always behave. Nothing goes wrong for months. Then one team ships an agent that gets adopted faster than anyone modelled, and the environments that lose access to capacity are not the ones that caused the consumption. They are whichever ones happened to need credits after the pool ran dry.
The strategic shift: environment groups now govern spend
In the previous article on environment groups and rules, I mapped the available rules into four governance domains: security and sharing, AI enablement, ALM and code quality, and operations and maker experience. Every rule fitted one of those four.
This one does not. It opens a fifth domain: cost and capacity.
That is not a taxonomy quibble. It changes who has a stake in your environment group design. Until now, a group’s rule set was a conversation between platform administration, security, and the ALM owner. A rule that determines which environments can consume from a purchased credit pool is a conversation that includes finance, and it makes your group boundaries into cost centre boundaries whether you intended that or not.
It also strongly suggests where the roadmap is going. Agent consumption is the fastest growing variable cost in most Power Platform estates, and it is the one with the weakest per environment controls. Expect more rules in this domain, and design your groups now on the assumption that they will eventually carry budget as well as policy.
The trade-off nobody puts in the release notes
Turning the draw off does not reduce what your agents cost. It converts an unpredictable bill into a predictable stop.
That is only an improvement where a stop is acceptable. When prepaid capacity is exhausted, enforcement is real. Microsoft documents that new agent flow runs are blocked once prepaid capacity runs out, while the parent agent continues to function for interactions that do not involve flows, and flow authors see a design time warning in the Copilot Studio designer. Broader capacity enforcement can extend to service denial where usage exceeds purchased capacity.
So the decision is not cost control versus no cost control. It is which failure mode you prefer in which part of your estate. In a sandbox, an agent that stops mid month is a signal that someone should have asked for capacity. In a customer facing production environment, the same event is an incident.
This is precisely why the group level lock is the right shape for this setting. Cost tolerance is a property of a population of environments, not of the tenant. A single tenant wide answer is wrong for somebody no matter which answer you pick.
A starting posture
The useful reframe is that the shared tenant pool is a scarce resource that should be reserved for workloads that cannot be allowed to stop. Everything else gets a fixed allocation and a hard ceiling. That inverts the default: instead of every environment competing for the pool, only production draws from it, and production draws from a pool that experiments are no longer draining.
Note what the production row does not say. It does not say leave production uncapped and hope. It says pair an enabled draw with a pay as you go overage plan and agent level limits, so that continuity is protected by a billing mechanism rather than by silently consuming everyone else’s capacity. Prepaid credits are consumed first and pay as you go covers the excess, which means a linked plan functions as a safety net rather than a first resort.
Where to configure this
Three surfaces matter, and you will probably touch all three.
The environment group rule
Per the message center post, navigate to Manage, then Environment Group, select the target group, add the Cost controls, Draw from tenant credit pool rule, configure it to enable or disable the setting, and apply the changes.
Per environment capacity allocation
The allocation itself is not part of the rule. In the admin center, go to Licensing, then under Products select Copilot Studio, and use the Summary tab to reach Manage Copilot credits. Select an environment, enter the number of credits to allocate, and the overage behavior appears alongside it.
This distinction is worth stating plainly, because it is the thing most likely to trip people up. The group rule decides whether an environment may exceed its allocation. It does not decide what the allocation is. An environment governed by a group with the draw disabled and no credits allocated to it is an environment where Copilot Studio consumption stops immediately.
Agent level limits
Environment and group controls determine which capacity sources a workload can reach. They do not stop a single runaway agent inside an authorized environment from consuming the whole allocation. For that, the Manage Agents view lets you set monthly limits per agent, with notifications to environment and tenant administrators as usage approaches the limit, and an optional hard stop that turns the agent off when it hits the ceiling.
Use both layers. An agent limit contains a single workload. The environment configuration determines what all workloads in that environment can reach. Neither substitutes for the other.
Find your exposure before you publish anything
Publishing a restrictive rule across a group without knowing current consumption is how you turn a budget concern into an outage. The admin center already holds the data you need. The Copilot Studio licensing area exposes daily consumption at environment level for up to three months, plus monthly data for the past twelve months, and the Environments tab shows credits deducted from prepaid capacity, units billed under pay as you go plans, and whether each environment is within capacity or in overage.
Work through it in this order.
- Open the Environments tab under Copilot Studio licensing and list every environment currently consuming credits.
- Identify which of those have no allocation set. These are your silent consumers and they are the reason this rule exists.
- Cross reference against your environment group membership. Environments consuming credits from outside any group will need handling individually.
- Look at the twelve month trend before choosing allocations, not just the current month. Agent adoption curves are not linear and a month to date figure will understate a growing workload.
- Set allocations first, based on that data. Publish the rule second.
- Start with your lowest risk group, not production. A personal productivity or sandbox group is where a mistake teaches you something cheaply.
- Confirm agent level limits exist for anything business facing before you tighten the environment level ceiling above it.
One caution specific to environment groups. Publishing this rule locks the setting for every member, including environments added to the group later. That is the point of the feature, and it is also how an environment nobody thought about inherits a hard ceiling. If your group is the destination for environment routing, every future maker environment inherits this rule the moment it is created.
The honest summary
Microsoft is right that no action is required on August 26. Nothing changes in how your environments behave, because the underlying setting and its default are not changing. What arrives is a lever.
The reason to act anyway is that the exposure the lever addresses has been there the whole time, and until now the only way to close it was one environment at a time. If you have ever looked at a Copilot Credit consumption figure and been unable to say quickly which environments produced it and which ones could have, this rule is the structural answer to that question.
Start with the environments that have no allocation set. That is where the surprise lives.
Sources
- Microsoft 365 message center post MC1458282, Power Platform admin center, Cost controls, Draw from tenant credit pool, published August 20, 2026
- Manage Copilot Studio credits and capacity, Microsoft Learn
- Manage costs for agents powered by the GitHub Copilot harness, Microsoft Learn
- Rules for environment groups, Microsoft Learn
- Environment groups, Microsoft Learn
- Standard harness licensing, Microsoft Copilot Studio documentation
Capacity, billing, and rule behavior in this area are changing quickly. Verify current behavior in Microsoft Learn and in your own tenant before acting on any configuration guidance here.