An invoice is scanned and processed through a cloud workflow, alongside credit balances and a November 2026 renewal date.
Microsoft will retire AI Builder capacity add-ons from sale on November 1, 2026. Partners who skip the renewal check could end up with automation that stops without warning. The date matters less than the details around it. AI Builder features aren't going away, and not every credit expires that day. The risk is a licensing gap that only shows up when an invoice-processing flow or document-extraction app starts failing.

An invoice is scanned and processed through a cloud workflow, alongside credit balances and a November 2026 renewal date. What Microsoft announced​

Starting November 1, 2026, Microsoft retires AI Builder capacity add-ons from sale. Customers with active subscriptions can continue using their existing AI Builder credits through the end of their current subscription term. The notice was posted in Partner Center on October 22, 2026. It is aimed at Cloud Solution Provider (CSP) distributors, direct bill partners, and indirect resellers with customers using AI Builder capacity add-ons.

The required action is simple. Partners should turn off auto-renew before affected customers' next renewal date. Microsoft's notice says direct-bill partners and indirect providers can do this in Partner Center. Indirect resellers should work through their distributor. Microsoft also tells partners to plan for Copilot Credits for customers who want to keep using AI Builder features once existing credits run out.

Microsoft's tenant-side message for admins (MC1485055, as reproduced by a third-party tracker) says the same thing. The add-ons will no longer be available for renewal or additional purchase. AI Builder capabilities will continue to be supported through Copilot Credits.

What November 1 does and doesn't mean​

The common misreading is that all add-on credits die on November 1. They don't.

  • Active add-on credits keep working. Microsoft's end-of-credits documentation says customers with active add-ons keep using those credits until their licenses expire.
  • What stops is sale and renewal. After the cutoff, partners can't renew an add-on or buy more capacity.
  • Auto-renew is the trap. Partner Center documentation says software subscriptions bought on or after October 14, 2021 autorenew by default. That page is general CSP software guidance, not AI Builder-specific. Still, it is a good reason to check each add-on's renewal setting instead of assuming it is off.

Timeline​

DateChange
November 1, 2025Customers with no active add-on could no longer buy AI Builder capacity add-ons. Existing add-on customers could still renew and add capacity.
November 1, 2026The add-ons retire from sale. Active credits are honored through the current term, and auto-renew must be off.
November 1, 2026A separate change: new or renewed eligible Power Platform and Dynamics 365 licenses stop carrying seeded AI Builder credits.

The second gap: seeded credits​

Add-ons are only one source of AI Builder credits. Microsoft's licensing overview says that starting November 1, 2026, no new or renewed Power Platform or Dynamics 365 licenses will receive seeded AI Builder credits. Customers who bought or renewed eligible licenses before that date keep their seeded credits through the applicable contract term.

Microsoft's credit-management documentation gives examples of seeded amounts. They include 500 credits for Power Apps per-user licensing and 5,000 for Power Automate Premium. The same page says one add-on provides 1,000,000 AI Builder credits. Treat these as clues for finding dependencies. They don't prove what a given customer owns. Verify the actual entitlements and contract end dates in the tenant instead of inferring them from license names.

A review that looks only at add-on purchases can miss a customer whose flows run entirely on a seeded allowance. That customer has no add-on to flag, and the seeded credits quietly stop being replenished at renewal.

Why Copilot Credits aren't a drop-in replacement​

Microsoft says there is no automatic conversion of AI Builder credits into Copilot Credits. There is also no universal ratio, because rates depend on the action.

The published rate table shows how uneven the exchange is:

Capability (unit)AI Builder creditsCopilot Credits
Receipt, invoice, identity document analysis (1 page)328
Custom document processing (1 page)1008
Text recognition, OCR (1 page)30.1
Object detection (1 image)88

These are published unit rates. They are not a conversion formula or a quote. Document-heavy workloads can look cheap in Copilot Credits, while others are priced roughly one-to-one. So a customer's remaining balance of one currency says little about how far the other would stretch.

How the two credit types interact​

Microsoft's documentation describes the consumption behavior this way:

  • Copilot Studio: AI Builder features always consume Copilot Credits.
  • Power Apps and Power Automate: AI Builder features consume AI Builder credits first. If those are absent or exhausted, they try Copilot Credits.
  • Agents and agent flows: these consume Copilot Credits only.
  • Nothing available: if neither credit type is available, model runs are blocked.
  • Monthly reset: consumption resets on the first of each month. Unused credits don't roll over.

Microsoft's guidance is to size capacity to the maximum you expect to consume in a single month. An annual average is the wrong yardstick.

Building and testing models, including prompts, doesn't consume credits. Running them does. A flow that passes every test in a dev environment therefore proves nothing about whether production has funded capacity.

Acquiring Copilot Credits​

Microsoft lists three routes: pay-as-you-go meters, prepurchase plans, and prepaid pack subscriptions that provide monthly capacity. The documentation's cost footnotes assume pay-as-you-go pricing of $0.01 per Copilot Credit. That figure is for rough estimating only, so confirm current partner pricing before quoting a customer. Also note that Microsoft's end-of-credits page sometimes calls them "Copilot Studio Credits." That is the same currency in different wording.

A practical checklist for partners​

These steps are service recommendations built from Microsoft's documented controls. They are not Microsoft requirements.

  1. Inventory add-on subscriptions. Record the customer and tenant, subscription ID, term end, next renewal date, current auto-renew status, and who is responsible for changing it.
  2. Switch off auto-renew. In Partner Center, go to Customers, pick the customer, select the subscription, switch Auto-renew off, and submit. Indirect resellers should get written confirmation from their distributor.
  3. Find seeded dependencies. Identify Power Apps, Power Automate and Dynamics 365 licenses that supply AI Builder credits, and note their renewal dates.
  4. Map production workloads. List which apps, flows, agents and environments run AI Builder actions, and at what volume.
  5. Forecast the peak month. Apply the published Copilot Credit rates to those volumes. Use the highest expected month.
  6. Decide where capacity lives. Prepaid pack credits can be allocated to a specific environment in the Power Platform admin center or left at tenant level. Confirm production environments can actually reach them.
  7. Assign an owner. Agree who monitors consumption, who approves spend, and who is called when capacity runs low.

Monitoring caveats​

Admins can view tenant-level AI Builder consumption in the Power Platform admin center under Licensing, then Capacity add-ons, then the Summary tab. A consumption report breaks usage down by day, user and environment.

Don't treat those numbers as live. Microsoft says consumption is computed periodically, ideally daily, but it can lag by five or more days. The decision to fall back to Copilot Credits or block a feature rests on that computation. A stale reading can therefore delay the fallback, and overage in that window isn't billed. When AI Builder actions are blocked, Microsoft's documentation says they fail with errors such as EntitlementNotAvailable or QuotaExceeded.

Analysis: who should worry most​

Customers with a hard-to-spot workflow are most exposed. Examples are a quiet accounts-payable flow, an approval process with an AI extraction step, or a customer-service routing app. Nobody watches these daily, and a block after capacity runs out looks like a bug rather than a licensing event.

There is a counterpoint. Several workloads are cheaper in Copilot Credits per unit, so the move won't always raise costs. The reverse can also happen, since the rate tables differ by capability. Prepaid packs and pay-as-you-go also bill differently from a flat monthly add-on. That makes a workload-based forecast better than a straight swap.

Channel Insider's coverage frames this as a service opportunity for partners, and Microsoft's own announcements emphasize Copilot Credits. Both have a commercial angle. The compliance steps are still real: auto-renew will keep an add-on that Microsoft has retired in the renewal queue unless someone turns it off. The risk of inaction is a failed renewal or a surprise capacity gap at the customer's expense.

Bottom line​

  • AI Builder capacity add-ons retire from sale on November 1, 2026, so auto-renew must be off before each customer's next renewal date.
  • Active add-on credits last until the end of the current term.
  • Seeded credits in new or renewed eligible Power Platform and Dynamics 365 licenses end separately on November 1, 2026.
  • Copilot Credits are not a one-for-one swap, so forecast by workload and by peak month.
  • Do the audit before the renewal date, not after a flow fails.
 

References

  1. Microsoft Retires AI Builder Add-Ons: What Partners Need to Check - Channel Insider Channel Insider 2026-10-23T18:40:22+00:00
  2. End of AI Builder credits | Microsoft Learn learn.microsoft.com
  3. October 2026 announcements - Partner Center announcements | Microsoft Learn learn.microsoft.com