On 1 November 2026, the AI Builder credits that come bundled with your premium licences stop existing. Not reduced. Removed.
Microsoft's own wording on this is unusually blunt. "There isn't a transition to Copilot Studio Credits." And separately, "There's no automatic conversion of AI Builder credits to Copilot Studio Credits."
The part people miss is the scope. This isn't a new customer thing. From the FAQ: "After November 1, 2026, these seeded credits will be removed for all new and existing customers, including those with an Enterprise Agreement."
If you have anything running on AI Builder right now, form processing, prediction models, document extraction, category classification, it's on borrowed time and the clock is short.
What you actually lose
Seeded credits per month, by licence. This is the table people get wrong, so it's worth being precise:
- Power Automate Premium: 5,000
- Power Automate Process: 5,000
- Power Automate Hosted RPA add-on: 5,000
- Power Automate Unattended RPA add-on: 5,000
- Power Apps Premium: 500
- Power Apps per app: 250
- Dynamics 365 Finance and Operations: 20,000
- AI Builder add-on tiers: 1,000,000
So do the arithmetic on your own licence mix before you panic or relax. Two hundred Power Automate Premium seats is a million credits a month vanishing. Two hundred Power Apps Premium seats is a hundred thousand, which is still real but it's a different conversation.
The exemption worth checking
If your contract started before 1 November 2025, you keep your AI Builder entitlement for the full duration of that contract. Microsoft states it directly: it will honour the terms of AI Builder entitlements for contracts that started prior to 1 November 2025, and those customers retain the entitlement commitments defined in their agreement for the full contract term.
This is the first thing to look up, because it decides whether you have nine weeks or three years. Go find your contract start date before you do anything else.
Worth noting that Microsoft's own FAQ puts the blanket removal sentence and the honour the contract sentence on the same page without reconciling them. I'm reading it as removal applies unless a pre November 2025 contract covers you. If you're in that window, get it confirmed in writing rather than taking my word or theirs.
What replacing it costs
AI Builder capacity add-ons went end of sale to new customers on 1 November 2025, and 1 November 2026 is end of life for the add-ons themselves. After that date, only AI Builder add-on credits stay active. Everything seeded is gone.
The replacement is Copilot Studio Credits, and there are two ways to buy them. Prepaid packs are $200 for 25,000 credits, which works out to $0.008 per credit. Pay as you go through an Azure subscription is $0.01 per credit.
The prepaid route is twenty percent cheaper per credit and it's also the one with the enforcement cliffs, so it's not a free win.
The two enforcement walls
These are separate and people conflate them.
On prepaid Copilot Studio capacity, enforcement triggers when a tenant hits 125 percent of prepaid capacity. At that point custom agents are disabled. An ongoing conversation isn't cut off, but every subsequent attempt to invoke the agent gets rejected until you add capacity or the month resets.
Agent flows are different. When prepaid capacity is fully consumed, so at 100 percent rather than 125, new agent flow runs get blocked. The parent agent keeps working normally for everything that isn't a flow. In progress runs finish. Test runs are exempt, and so are runs triggered by Microsoft 365 Copilot licensed users through the agent calls the flow trigger. Pay as you go environments aren't subject to this at all.
So agent flows stop before your agents do. If you've built anything where a flow does the actual work and the agent is just the front door, the flow is what fails first.
One more thing about the numbers
AI Builder consumption reporting can lag five days or more. Microsoft admits this in the docs.
That matters right now, because if you're trying to size your Copilot Studio purchase based on current AI Builder usage, the number you're looking at is stale and probably low. Pull a few weeks of history rather than reading yesterday's figure and multiplying.
What to do in the next nine weeks
Find your contract start date. If it's before 1 November 2025 you have breathing room and should confirm that in writing.
Then inventory what's actually consuming AI Builder credits today. Not what somebody built once, what's running. The consumption reporting is the place to look, allowing for the lag.
Then price the replacement both ways, prepaid and pay as you go, and decide which enforcement behaviour you can live with. If you've got agent flows doing real work, the 100 percent block matters more than the 125 percent one.
And if the answer comes back as a number nobody budgeted for, you've found it in September instead of November, which is the whole point.
Our Copilot credit estimator does the arithmetic if you'd rather not do it by hand. Every rate on it links back to the Microsoft page it came from and shows the month we last checked it, because these figures move more than anyone would like.