Microsoft 365 Message Center ID: MC1458282
General Availability: 26 August 2026
If your organisation is using Power Platform, Copilot Studio or AI-powered workloads, keeping control of capacity and consumption is becoming increasingly important.
Microsoft is introducing a new Cost controls – Draw from tenant credit pool rule in the Power Platform admin center, giving administrators more control over how environments consume available tenant capacity.
And while Microsoft has classified this update as awareness only, it is worth understanding before it reaches general availability.
🔹 What is changing?
The new Draw from tenant credit pool capability allows administrators to decide whether an environment can use capacity from the organisation’s wider tenant credit pool when:
- The environment reaches its allocated credit limit, or
- The environment doesn’t have a specific credit allocation.
By default, the setting:
Draw from the available capacity in my tenant
will be enabled at the environment level.
This means an environment can potentially consume available capacity from the wider tenant pool once its own allocation has been exhausted.
Microsoft is now giving administrators the ability to change that behaviour.
🔹Why does this matter?
This is fundamentally about cost and capacity governance.
As organisations increasingly deploy Copilot Studio agents, Power Platform automation and other AI capabilities, consumption can become harder to predict.
Without appropriate controls, an individual environment could potentially consume additional capacity from the tenant pool once its allocated credits have been used.
The new control gives organisations a choice:
Allow the environment to draw from the tenant pool
This provides greater flexibility and helps workloads continue operating when their allocated capacity is exhausted.
Prevent the environment from drawing from the tenant pool
This provides tighter cost control by limiting the credits that the environment can consume each month.
Neither option is universally “right”.
The important thing is that the decision becomes part of your Power Platform governance model.
🔹Environment-level control
Administrators will be able to manage the capability for individual environments through the Power Platform admin center.
This provides a useful level of granularity where different environments have different requirements.
For example, you might decide:
Development environments
Don’t draw from the tenant pool.
Test environments
Don’t draw from the tenant pool unless specifically approved.
Critical production environments
Allow access to the tenant pool to reduce the risk of service disruption.
This is where the feature becomes particularly interesting from a governance perspective.
Rather than treating every environment identically, organisations can make decisions based on business criticality, consumption and risk.
🔹But there is an important catch with Environment Groups
If you’re using Environment Groups, pay particular attention to this part.
When the rule is published for an Environment Group, the setting will apply across all environments within that group.
The individual environments will then no longer be able to change the setting themselves.
That means you need to think carefully about your group structure.
For example:
Production Environment Group
↓
Cost control rule enabled
↓
All environments inherit the setting
If you need individual environment-level control, Microsoft states that you should not apply the rule to that Environment Group, or alternatively move the environment outside the group.
🔹This is more than a cost-control setting
For me, the interesting part of this announcement isn’t simply the new toggle.
It’s another example of Microsoft giving organisations increasingly granular controls over the AI and Power Platform estate.
As organisations move from experimenting with Copilot and agents to running them as production services, governance needs to evolve.
You need to start asking questions such as:
- Which environments are allowed to consume tenant capacity?
- Which environments should have hard consumption boundaries?
- Who owns the consumption?
- Which environments are business critical?
- How much capacity should each environment receive?
- What happens when an environment reaches its allocation?
- Are Environment Groups being used appropriately?
- Are we monitoring consumption closely enough to identify unexpected growth?
These are no longer simply Power Platform administration questions.
They’re becoming part of AI governance, financial governance and operational governance.
🛠️ What should administrators do?
Microsoft says no action is required for this update.
However, I’d recommend using the announcement as an opportunity to review your current capacity governance.
1. Review your environments
Understand which environments are:
- Development
- Test
- Production
- Business critical
- Experimental
- No longer required
2. Review your Environment Groups
If you’re using Environment Groups, understand which environments inherit configuration from group-level rules.
3. Review your consumption model
Consider whether environments should be able to draw from the wider tenant pool when their allocation is exhausted.
4. Consider your governance policy
Don’t make the decision purely from a technical perspective.
Consider business criticality, cost, risk and user impact.
🛠️ How do you configure it?
Microsoft states that administrators can configure the rule from:
Power Platform admin center → Manage → Environment Group
Select the relevant Environment Group and add:
Cost controls – Draw from tenant credit pool
You can then configure whether the setting is enabled or disabled and apply the changes.
Microsoft also states that Power Platform API methods can be used to manage the capability at scale.
💡 The Jim Talks takeaway
The Power Platform is increasingly becoming an enterprise AI platform, not simply a collection of low-code tools.
As Copilot Studio agents and AI-powered workloads become embedded into everyday business processes, capacity management becomes governance.
The question is no longer simply:
“Can we build this agent?”
It’s increasingly:
“Can we govern what happens when thousands of people start using it?”
This new control is a small but important piece of that puzzle.
📅 General Availability: 26 August 2026
Microsoft 365 Message Center: MC1458282
Leave a Reply