Contents
- Fast answer
- Quick facts
- What this covers
- Why it matters
- Where to go next
- Outcomes
- Step by step
- The two dates that matter
- Dual-mode consumption and the block at the end of it
- Why there is no conversion ratio, and what to do about it
- The overage that is never billed, and the five-day blind spot
- Microsoft's own licensing table still says 5,000 a month
- What to do before November
- At a glance
- Mistakes to avoid
- FAQ
- Related guides
Fast answer
Microsoft is retiring AI Builder credits on a published two-date calendar. On 1 November 2025 the AI Builder capacity add-ons stopped being sold to new customers. On 1 November 2026 two things happen at once: existing add-on customers can no longer renew or buy add-ons, and seeded AI Builder credits are removed from premium licences. Microsoft's wording is that after that date seeded credits are removed for all new and existing customers including those with an Enterprise Agreement, and that Copilot Studio Credits will be required for continued access. There is no automatic conversion and no published conversion ratio, because Microsoft states rates are different for each scenario. Instead a dual-mode model applies: AI Builder features consume AI Builder credits first, then Copilot Credits, and if both are unavailable or exhausted the feature is blocked. AI Builder features themselves are not being retired. Only the currency that pays for them is.
Facts last verified 2026-09
Quick facts
- End of sale
- 01/11/2025, AI Builder capacity add-ons, new customers only
- End of life
- 01/11/2026, add-ons cannot be renewed or purchased
- Seeded credits removed
- 01/11/2026, from all premium licences
- Enterprise Agreement
- No exemption after the date, per Microsoft
- Contract carve-out
- Contracts started before 01/11/2025 honoured for their full term
- Consumption order
- AI Builder credits, then Copilot Credits, then blocked
- Conversion ratio
- None published. Rates differ for each scenario
- Consumption reset
- Monthly
- Overage computation delay
- Ideally daily, can be delayed five or more days
- Overage billing
- Never billed. Affects the current environment only
- Learn comparison table
- Still lists 5,000 credits/month with no retirement note (2026-09-01)
On this page
What this page covers
A comparison visitor should understand the tradeoff, the best-fit scenario, and the next diagnostic tool to confirm the choice.
- 01The two dates that matter
- 02Dual-mode consumption and the block
- 03Why there is no conversion ratio
- 04The overage that is never billed
- 05Microsoft's own table still says 5,000
- 06What to do before November
Why does this matter now?
This is a currency change dressed as a product note, and it hits a line item most organisations do not track. The 5,000 seeded AI Builder credits a month that come with each Power Automate Premium and Power Apps Premium licence have been free-feeling capacity for years, and on 1 November 2026 they stop existing. The Enterprise Agreement carve-out that usually protects entitlements does not apply beyond the contract term here. And because there is no conversion ratio, nobody can tell you in advance what the replacement Copilot Credit budget should be. The only defensible way to size it is to measure your own consumption before the switch.
Internal path
Where to go next from this page
These links are part of the A8gent learning and conversion path. Use them to move from concept, to diagnosis, to workflow build, to course.
What you should be able to do after this
- Get the two retirement dates straight
- Understand the dual-mode consumption order
- See why no conversion ratio exists
- Plan a Copilot Credit budget before the cutover
How do you do it, step by step?
1. Write both dates in the renewal calendar
1 November 2025: end of sale of AI Builder capacity add-ons to customers who do not already hold one. 1 November 2026: end of life. Existing add-on holders can keep consuming credits on active add-ons until those contracts expire but cannot renew or buy more, and seeded credits are removed from premium licences. Microsoft honours AI Builder entitlements in contracts that started before 1 November 2025 for the full contract duration, which is the only extension published.
2. Find out which currency you are actually on
There are two distinct populations in Microsoft's calendar table: add-on customers who bought AI Builder capacity packs of one million credits, and seeded customers whose credits arrive with Power Apps Premium, Power Automate Premium or Dynamics 365 licences. They have different end states. Check which you are before planning anything, because an add-on holder with a long contract has more runway than a seeded customer does.
3. Understand the consumption order
In a Power Apps or Power Automate context, AI Builder features consume AI Builder credits first. If those are absent or exhausted the system attempts Copilot Credits. If both are unavailable or exhausted, the feature fails. Consumption resets monthly, so an environment holding both currencies goes back to spending AI Builder credits at the start of each month. That reset is why measuring a single week tells you nothing useful.
4. Measure consumption now, while the old currency still exists
Because Microsoft publishes no conversion ratio, the only way to size a Copilot Credit budget is empirical. The Power Platform admin centre now carries daily usage tracking per environment, allocation of prepaid or pay-as-you-go Copilot Studio Credits, and product-level consumption insight. Take a full month of AI Builder usage per environment before the seeded credits vanish, because after November you will be sizing blind.
5. Buy the replacement deliberately, not reactively
Microsoft's stated remedy is to purchase Copilot Credits. Copilot Studio's published capacity pack is $200 a month for 25,000 Copilot Credits, and there is a Copilot Credit Pre-Purchase Plan reservation for committed volume. Both are decisions to make with a measured number in hand. Buying a pre-purchase plan is irreversible, so guessing is expensive in a way that a monthly pack is not.
The two dates that matter
Microsoft announced the progressive end of AI Builder credits in October 2025 and publishes the calendar as a table with two dates on it. The first is 1 November 2025, which was end of sale of AI Builder capacity add-ons to new add-on customers, meaning customers without any active AI Builder capacity add-on. Nothing changed that day for anyone who already held one, or for seeded customers whose credits arrive with a premium licence.
The second is 1 November 2026, and it does two separate things to two separate populations. For existing add-on customers it is end of life of the capacity add-ons: they can still use credits linked to their active add-ons but can no longer renew them or purchase new ones, and Microsoft's table adds that customers with active add-ons continue using those credits until their licences expire. For existing seeded customers it is end of seeded AI Builder credits: they stop receiving them, and Microsoft's wording is that these seeded credits will be removed from their premium licences.
The Enterprise Agreement question is answered explicitly and the answer is not the reassuring one. Microsoft states that after 1 November 2026 these seeded credits will be removed for all new and existing customers, including those with an Enterprise Agreement, and that Copilot Studio Credits will be required for continued access, or an active AI Builder add-on. The one carve-out is contract-based rather than agreement-type-based: Microsoft honours AI Builder entitlements for contracts that started before 1 November 2025 for the full duration of that contract.
It is worth being clear about what is not ending, because the retirement notice is easy to misread as a product retirement. Microsoft's opening line is that the progressive end of AI Builder credits does not impact AI Builder features, which continue to be supported in all contexts using Copilot Credits. Form processing, object detection, text classification and the rest all survive. What ends is the currency they are paid in.
Dual-mode consumption and the block at the end of it
There is no migration event, no switchover flag and no conversion. Instead Microsoft has built a fallback chain, and understanding its order is the whole of the operational story. When an AI Builder feature runs in a Power Apps or Power Automate context, the system consumes AI Builder credits first. If AI Builder credits are exhausted or unavailable, it attempts to use Copilot Studio Credits. If no Copilot Credits are available, usage is blocked.
That third state is a hard stop rather than an overage. The feature fails. Microsoft says so plainly: if both currencies are unavailable or exhausted, AI Builder features fail. For anything sitting in a production process - an invoice extraction step, a document classification gate - that is a process outage rather than a billing line, and it will surface as a broken flow rather than as a finance conversation.
Consumption resets every month, which has a consequence people do not anticipate. An environment holding both currencies restarts consuming AI Builder credits at the beginning of each month. So a tenant that spent the last week of a month on Copilot Credits will spend the first part of the next month back on AI Builder credits, and the shape of your Copilot Credit consumption over a month is therefore back-loaded rather than flat. Sampling a single week to size a budget will mislead you in whichever direction you happened to sample.
The practical consequence for the November cutover is that dual-mode collapses to single-mode overnight for seeded customers. Up to 31 October the chain starts with 5,000 free credits a month per premium licence; from 1 November it starts with Copilot Credits or with nothing. If you have never bought Copilot Credits, the chain has exactly one step and it is the block.
Why there is no conversion ratio, and what to do about it
The question everyone asks is what an AI Builder credit is worth in Copilot Credits, and Microsoft's answer is that the question does not have an answer. Its FAQ states that there is no conversion of entitlement from one currency into the other and that rates are different for each scenario, pointing instead at the AI Builder capability rate table. In other words, the exchange rate depends on which model or capability you are running, so a single number would be wrong for almost every workload.
Microsoft has also introduced a new segmentation - Basic, Standard, Premium and Content Processing - which are tiers of AI capability rather than licence tiers. Existing AI Builder workloads map onto them by the type of model or prompt used. Microsoft's own examples: sentiment analysis maps to text and generative AI tools at the Basic tier, while entity extraction maps to the Standard tier. Two capabilities that felt equivalent under a single credit currency can therefore land in different tiers under the new one.
This makes forecasting an empirical exercise rather than an arithmetic one, and it makes the timing urgent. The only way to know what your Copilot Credit budget needs to be is to observe your real consumption pattern while both currencies exist and the rate tables are live. After 1 November 2026 the seeded credits are gone and you will be sizing a purchase against a workload you have never priced.
Microsoft's stated remedy is direct: customers are invited to purchase Copilot Credits. The published Copilot Studio capacity pack is $200 a month for 25,000 Copilot Credits, and there is a committed-volume route through the Copilot Credit Pre-Purchase Plan. Those are very different commitments, and the difference in reversibility is enormous, which is why measuring first matters more here than in most licensing changes.
The overage that is never billed, and the five-day blind spot
Buried in the FAQ is a detail that explains a class of confusing behaviour and that we have not seen documented anywhere outside Microsoft's own page. AI Builder credit consumption is computed regularly, ideally daily, but Microsoft states it can be delayed up to five or more days. The decision to fall back to Copilot Credits or to block a feature is based on that computation.
The consequence is a blind spot with a specific shape. If the computation does not happen for several days, the last computation still holds, indicating that there is no overage, and AI Builder features continue consuming AI Builder credits you no longer have. Microsoft's own phrasing is that this can lead to important overage. Once the computation catches up, the next runs are blocked or licensed based on the fresh figure, which is why the failure appears suddenly rather than gradually.
The financially interesting half is what happens to that overage: Microsoft states it affects only the current environment and is never billed. So the delay is not a cost exposure. It is a planning exposure, and a monitoring one. An admin looking at a green dashboard during a stale window is looking at a stale figure, and any capacity decision taken on that reading is taken on out-of-date data.
The practical rule is not to trust a single day's consumption reading as a control signal. Treat AI Builder consumption reporting as something that trails reality by up to a week, plan headroom accordingly, and expect the block to arrive as a step change rather than a warning. If a feature stops working with no apparent change in usage, a caught-up computation is the first thing to check.
Microsoft's own licensing table still says 5,000 a month
Here is the part that matters most for anyone budgeting a renewal. On 1 September 2026, two months before the seeded credits are removed, Microsoft Learn's Power Automate licence comparison table still listed AI Builder credits at 5,000 per month against the Premium, Process and Hosted Process licences, with no retirement note, no footnote and no link to the end-of-credits article. The same table's seeded-licence equivalent lists 500 a month against Power Apps Premium on the same terms.
Meanwhile a different current Microsoft Learn article, the AI Builder end of credits page, states that from 1 November 2026 those seeded credits will be removed from premium licences for all new and existing customers including Enterprise Agreement holders. Both pages were live and current on the same day. Both are official documentation. They disagree about an entitlement that a lot of renewal conversations depend on.
We are not reporting this to score a point. It is the practical reason so many organisations will be surprised in November: the page an admin naturally reaches for when checking what a licence includes is the comparison table, and the comparison table is the one that does not mention the change. If your business case for a Power Automate Premium renewal has an AI Builder line in it, that line was sourced from the table, and the table is out of date on this point.
The correct reading is that the retirement page governs, because it is the specific and later statement about the entitlement, and because Microsoft's calendar table there is unambiguous about dates and populations. Treat the 5,000 credits as an entitlement with an expiry of 1 November 2026, and if a Microsoft representative quotes the comparison table back at you, the end-of-credits article is the document to put in front of them.
What to do before November
First, classify yourself. Add-on customer or seeded customer, and if seeded, does your contract predate 1 November 2025? Those three facts determine your actual deadline, which is either the contract end date or 1 November 2026. Organisations frequently turn out to be both, with add-ons in one business unit and seeded credits everywhere else, and the two have different runways.
Second, measure. The Power Platform admin centre now carries daily usage tracking per environment, allocation of prepaid or pay-as-you-go Copilot Studio Credits, product-level consumption insight, and governance features including environment routing, data loss prevention policies and audit logs. Take at least one full calendar month of AI Builder consumption per environment, because the monthly reset makes shorter samples unrepresentative, and remember the reporting can trail by five or more days.
Third, identify the workloads that would break. Any AI Builder step inside a production flow becomes a hard failure point on 1 November if no Copilot Credits are allocated to its environment. Enumerate those, decide which are business-critical, and make sure their environments have credits allocated before the date rather than after the first failure. Environment-level allocation matters here, because the block is environment-scoped.
Fourth, buy deliberately. The monthly Copilot Studio capacity pack at $200 for 25,000 Copilot Credits is reversible in the sense that you can stop buying it. The Copilot Credit Pre-Purchase Plan is not: Microsoft states cancellations and exchanges are not supported and all purchases are final. Start on the reversible instrument, gather three months of real consumption on the new currency, and only then consider a commitment.
At a glance
Microsoft's published AI Builder credit retirement calendar, read from learn.microsoft.com/en-us/ai-builder/endofaibcredits on 1 September 2026
| Date | Event | Who is affected | Impact |
|---|---|---|---|
| 01/11/2025 | End of sale, AI Builder capacity add-ons | Customers with no active AI Builder capacity add-on | Cannot purchase AI Builder capacity add-ons |
| 01/11/2025 | No change | Existing add-on customers | Can still use, renew and purchase add-ons |
| 01/11/2025 | No change | New and existing seeded customers | Premium licences continue to provide seeded AI Builder credits |
| 01/11/2026 | End of life, AI Builder capacity add-ons | Existing add-on customers | Can still use credits on active add-ons, cannot renew or purchase |
| 01/11/2026 | End of seeded AI Builder credits | Existing seeded customers | Seeded credits removed from premium licences |
| After 01/11/2026 | No change | Existing add-on customers | Continue using credits until their licences expire |
| Contract exception | Entitlements honoured | Contracts started before 01/11/2025 | AI Builder entitlements honoured for the full contract duration |
| Conversion ratio | Not published | All customers | No conversion of entitlement. Rates differ for each scenario |
| Fallback order | AI Builder credits, Copilot Credits, block | All customers | Features fail when both currencies are exhausted or unavailable |
| Overage delay | Five or more days | All customers | Stale computation lets consumption continue. Overage is never billed |
| Learn licence comparison table | 5,000 AI Builder credits per month | Premium, Process, Hosted Process | Still advertised with no retirement note as of 2026-09-01 |
What mistakes should you avoid?
- Assuming an Enterprise Agreement protects seeded AI Builder credits past 1 November 2026
- Waiting for a published conversion ratio that Microsoft has said will not exist
- Reading Microsoft Learn's licence comparison table and budgeting 5,000 AI Builder credits a month indefinitely
- Trusting a green admin-centre status when overage computation can be five or more days stale
- Assuming AI Builder features are being retired, when only the currency is changing
- Sizing a Copilot Credit commitment from a single week of usage when consumption resets monthly
FAQ
- When exactly do AI Builder credits end?
- 1 November 2025 was end of sale of capacity add-ons to new customers. 1 November 2026 is end of life: add-ons can no longer be renewed or purchased, and seeded AI Builder credits are removed from premium licences for all new and existing customers, including Enterprise Agreement holders.
- Will my AI Builder credits convert to Copilot Credits?
- No. Microsoft states there is no automatic conversion and no conversion of entitlement from one currency into the other, because rates differ for each scenario. A dual-mode model applies instead: AI Builder credits are consumed first, then Copilot Credits, then the feature is blocked.
- Do AI Builder features stop working?
- No. Microsoft states the change does not impact AI Builder features, which continue to be supported in all contexts using Copilot Credits. What ends is the AI Builder credit as a currency.
- Why did my environment run a large AI Builder overage without falling back?
- Because the consumption computation is delayed. Microsoft states it is ideally daily but can be delayed up to five or more days, and while it is stale the last computation still holds, indicating no overage, so features keep consuming AI Builder credits. Microsoft also states that such overage affects only the current environment and is never billed.
- Why does Microsoft's licensing table still say 5,000 AI Builder credits a month?
- It does, and on 1 September 2026 the Power Automate licence comparison table on Microsoft Learn still listed 5,000 AI Builder credits a month against Premium, Process and Hosted Process with no retirement note, while a separate AI Builder page documented their removal two months later. Both pages are current Microsoft documentation and they disagree.
Sources & further reading
Done for you
Want this built for your business?
Tell us the workflow. We scope, build, and ship the agent with guardrails and the numbers to prove it worked. The scoping call is free.
Free scoping call. You own the code.
Was this page helpful?

