Microsoft partners need to check AI Builder renewal dates and arrange replacement capacity to keep customers’ apps and automated workflows running.
The company will retire AI Builder capacity add-ons from sale on Nov. 1, 2026, according to an Oct. 22 Partner Center notice. Customers can continue using existing credits through their current subscription term, but partners must turn off auto-renew before the next renewal date.
For distributors, resellers, and managed service providers, the immediate job is to identify affected subscriptions and arrange replacement capacity before customers need it.
What happens on Nov. 1
The Microsoft announcement applies to Cloud Solution Provider distributors, direct-bill partners, and indirect resellers with customers using the add-ons.
Direct-bill partners and indirect providers can disable auto-renew in Partner Center. Indirect resellers should work with their distributor. Microsoft directs partners to plan for Copilot Credits when customers need to continue using AI Builder after existing credits expire.
The retirement follows an earlier restriction: New customers lost the ability to buy AI Builder capacity add-ons on Nov. 1, 2025, while existing customers could still renew or add capacity.
Microsoft’s credit retirement guidance says AI Builder features remain supported. The change concerns the credits used to run them.
An active subscription extending beyond Nov. 1 preserves the customer’s AI Builder credit entitlement until its term ends. Partners should also monitor monthly consumption because workflows can exhaust available credits before that date and need Copilot Credits to continue running.
The renewal work adds to the operational changes outlined in Pax8’s guidance on Microsoft pricing and partner benefits.
Included credits are also changing
The transition extends beyond separately purchased capacity add-ons.
Beginning Nov. 1, new or renewed Power Platform and Dynamics 365 licenses will no longer receive included, or “seeded,” AI Builder credits, Microsoft’s licensing overview states. Customers with eligible licenses purchased or renewed before that date retain those credits through the applicable contract term.
Partners should therefore check both purchased capacity and credits bundled into existing licenses. A review limited to add-on purchases could miss customers whose workflows rely on an included allowance.
Copilot Credits require a fresh usage calculation
Microsoft does not automatically convert AI Builder credits into Copilot Credits. Its retirement guidance also says there is no single conversion ratio: Consumption rates depend on the workload.
For AI Builder features in Power Apps and Power Automate, available AI Builder credits are consumed first, followed by Copilot Credits when needed. Features can fail if neither credit type is available.
Partners should map the customer’s actual workloads to the applicable rates before recommending replacement capacity. A credit total alone does not show how much work the replacement purchase will cover. Consumption resets monthly, and unused credits do not roll over, so partners should estimate capacity around expected peak monthly usage.
Microsoft’s licensing documentation lists prepaid capacity, prepurchase plans, and pay-as-you-go options for Copilot Credits. It also explains that building and testing models does not require credits, while running them does. A successful design-stage test therefore cannot establish that production has sufficient capacity.
This makes usage reviews relevant to the wider shift toward Copilot deployment, consumption management, and ongoing CSP services.
What partners should confirm with each customer
A practical transition review should establish four things:
- The deadline: Record subscription end dates and confirm who will disable auto-renew.
- The dependency: Identify production apps and flows relying on purchased or seeded credits.
- The replacement: Estimate peak monthly capacity from workload volumes and current rates, then confirm that the production environments can access the required Copilot Credits.
- The owner: Agree who monitors consumption, approves spending, and responds when capacity runs low.
These are service recommendations rather than additional Microsoft requirements. They give customers a concrete transition plan and partners a defined scope of work.
Microsoft’s Frontier Partner specialization reflects its broader emphasis on partners that can deploy, govern, and manage AI systems. For existing AI Builder customers, continuity and cost visibility are immediate ways to demonstrate that expertise.
Keep business workflows running through the transition
Customers should leave their next partner conversation knowing when their current entitlement ends, what will fund continued usage, and who owns the change. An invoice showing an active Microsoft subscription is insufficient unless the team also understands which credits its production workflows consume.
Partners can make that discussion useful by connecting capacity to business activity: Which processes depend on it, how much usage is expected, and what happens if demand exceeds the forecast? Prioritize workflows whose interruption would delay customer service, approvals, or other essential work.
The strongest transition plan pairs a confirmed renewal change with verified replacement capacity, a realistic budget, and an escalation contact. That gives the customer something more valuable than a licensing update: a clear path to keeping existing automation available.
Read more: As licensing changes create new support responsibilities, explore how AI is changing the MSP business through automation, customer education, and ongoing change management.