Microsoft 365 Copilot Goes Standalone December 1, 2026 as CSP Usage Billing Begins

Here's what changes, what doesn't, and what admins and partners should do before December 1.

The headline change: no base subscription required​

Microsoft announced this through Partner Center in mid-October. The new offers will be available across all channels, including Cloud Solution Provider (CSP), for commercial, education, government, and nonprofit customers. The new offers have their own product and SKU IDs and are priced the same as the current offers.

The new offers do more than sit next to the old ones. Beginning December 1, 2026, the new offers replace the add-on offers for new Microsoft 365 Copilot and Microsoft 365 Copilot Business purchases. Microsoft also says this purchasing change affects how customers purchase Copilot, not the underlying Copilot capabilities.

That point matters. Microsoft's Partner Center announcement says Copilot experiences still depend on the Microsoft 365 apps and services a customer is licensed for. Buying the license without a base plan is now allowed. That doesn't mean Copilot will do the same work in an organization with no Microsoft 365 apps as it does inside Word, Excel, Outlook and Teams. "Can buy it" and "gets the full experience" are different questions.

Section summary: From December 1, both Copilot offers no longer need a Microsoft 365 base plan, prices stay put, and the new SKUs replace the old ones for new purchases. What Copilot can do still depends on the rest of your Microsoft 365 licensing.

The rename: "(add-on)" is now in the offer names​

The first step has already happened. Beginning October 16, 2026, the current offers that require a qualifying Microsoft 365 base subscription include "(add-on)" in their names. For example: "Microsoft 365 Copilot (add-on)" and "Microsoft 365 Copilot Business (add-on)." These add-on offers reach end of sale in CSP on December 1, 2026.

End of sale is not end of life. Microsoft's Partner Center announcement says existing customers can keep renewing and changing seat counts. Existing subscriptions keep their product and SKU IDs, pricing, renewal terms, auto-renew settings and service. Microsoft says no migration or license reassignment is needed.

Partners running automation have one piece of homework. Microsoft told partners to switch scripts, catalog mappings and automations from offer names to product and SKU IDs. Its target date for that was October 16, so anyone who matches catalog entries by display name may already have a broken mapping. Microsoft says it will publish the new product and SKU IDs before the November 1, 2026 price-list preview.

Timeline at a glance​

The second December 1 change: usage-based billing​

This is where it's easy to mix things up. Previously communicated as November 2, 2026, usage-based billing will now be enabled by default for new Microsoft 365 Copilot Business subscriptions purchased through CSP, beginning December 1, 2026.

That policy is much narrower than the purchase change. Microsoft's Partner Center usage-based billing documentation limits it to Copilot Business B-SKUs and says Microsoft 365 Copilot (Enterprise) is out of scope. It also covers only the commercial segment, so education, nonprofit and Government Community Cloud (GCC) low customers are excluded. The standalone offers reach every segment; usage-based billing does not.

Geography is limited too. Microsoft's announcement says usage-based billing will not be available at first in Australia, Belgium, Brazil, France, Germany, India, Italy, Korea, the Netherlands, Poland and Spain. That restriction applies only to usage-based billing, not to the standalone offers.

What gets metered​

At launch, usage-based billing covers Copilot Cowork, Work IQ APIs and GitHub Copilot Harness, and Microsoft says more usage-based agents and services will follow. The documentation lists the Copilot Business SKUs in scope at launch. They include standalone Microsoft 365 Copilot Business and several bundles that pair Business Basic, Standard or Premium with Copilot, including the EEA and "no Teams" variants.

The 4,000-credit question​

Microsoft sets the default spending limit at 4,000 Copilot Credits per user per month, and admins can change it. That number is a limit, not a monthly fee. Microsoft's example: an organization with 100 Copilot Business users could use up to 400,000 credits a month under the default, and it is billed for what it actually uses.

The documentation adds some details that cost-conscious admins should know:

• No opt-in step. Eligible SKUs use the normal add-to-cart checkout. Partner Center can automatically create the Azure Plan, Azure subscription, resource group and default spending policy.
• No duplicate policies. A default policy is created only if the tenant doesn't already have a spending or billing policy from any channel or partner.
• The first cap reached applies. A policy can have a tenant-wide monthly cap, a per-user cap, or both, and whichever is hit first is enforced.
• The least restrictive policy wins. If several policies apply to the same user, the most permissive one applies. If any applicable policy is unlimited, the user is effectively unlimited.
• You can't switch it off completely. Once configured, usage-based billing can't be disabled. Partners can set the spending limit to zero to stop further spend. The documentation also says limits can't go below a platform minimum and that deleting the policy is the only way to stop spend entirely, so check how these interact in Partner Center before relying on either.
• Deleting a policy doesn't erase accrued charges. The tenant still owes for usage before deletion.
• Advanced scoping is done elsewhere. Policies for specific users or groups are managed in the Microsoft Admin Center under Copilot > Cost management. Partner Center only handles the default tenant-wide and per-user limits.
• Charges are billed separately from seats. Consumption shows up in existing Azure reconciliation files, separate from the seat-based subscription charge.

Partners should also know that adding seats through the Partner Center portal can turn on usage-based billing for the whole tenant. Microsoft's documentation says this can cause consumption charges to appear even when only some seats triggered it.

Microsoft also says that about three out of four Copilot Business customers sold through CSP currently have no Azure footprint. For many small businesses, their first Copilot Business purchase after December 1 may also be the first time they get an Azure subscription, which their partner will need to monitor.

Section summary: Usage-based billing covers only CSP Copilot Business B-SKUs for commercial customers in supported markets. The 4,000-credit figure is an adjustable limit, and most of the risk comes from controls that are easy to overlook.

Having the Copilot app is not having the license​

It's tempting to assume that installing the Copilot app means a user has Copilot. Microsoft's support guidance shows the tiers. Work or school users can check the label under their name on the Microsoft 365 home page:

1. Copilot Chat (Basic): no Copilot add-on license and no Copilot in Word, Excel, PowerPoint or OneNote.
2. M365 Copilot (Basic): no add-on license, but standard access to Copilot in the apps.
3. M365 Copilot (Premium): a full license with priority access to the complete Copilot experience in those apps.

NeoTeo also describes the Premium tier as grounding responses in organizational data through Microsoft Graph and Work IQ. The new standalone SKUs change who can buy that Premium license. They don't make an app download equal to a license.

Pricing context and the strategic angle​

Microsoft says the new SKUs keep current pricing. For reference, Velosio's pricing guide lists Microsoft 365 Copilot costs $30 per user per month as the enterprise add-on (annual term, and says for organizations up to 300 users, Microsoft 365 Copilot Business is $18 per user per month promotionally (standard price $21) through December 31, 2026. Those are third-party figures. Check them against the November 1 price-list preview before quoting anyone.

So why change this now? Microsoft hasn't said, so the rest of this paragraph is my analysis. There's an obvious market to win: organizations on other productivity suites that want to try Copilot without moving to Microsoft 365. A Japanese explainer on note.com suggests the change gives companies that say, "We use Google Workspace but want to try Copilot" another option. That's a reasonable reading. Buyers should still remember Microsoft's own caveat that Copilot's experience depends on the Microsoft 365 apps a customer is licensed for. FourWeekMBA connects the timing to UK regulators putting AI-assistant choice inside the bundle on their roadmap. That's that outlet's interpretation, not something Microsoft has said.

It's also notable that the standalone license launches on the same day as default-on metering for Copilot Business. Seat-based licensing is becoming the entry point, with consumption billing layered on top. That's good for flexibility. It also means finance teams can no longer treat the per-seat price as the total cost.

One caution about coverage: at least one outlet, Cloud Expo, published a summary giving the date as December 2023. Microsoft's announcement says December 1, 2026.

What to do before December 1​

For IT admins at existing Copilot customers:

1. Do nothing about migration. Add-on subscriptions renew as they are, and seat changes still work.
2. Have users with unexpected Copilot behavior check their account label (Basic vs. Premium) on the Microsoft 365 home page before opening a ticket.
3. If you buy Copilot Business through CSP, ask your partner whether new seats will turn on usage-based billing for your tenant. Then review the spending policy in Microsoft Admin Center under Copilot > Cost management.

For CSP partners:

1. Replace any automation that matches on offer names with product and SKU IDs.
2. Review the new SKUs in the November 1 price-list preview and prepare side-by-side quotes.
3. Test usage-based billing provisioning in the sandbox when it becomes available on November 2. Microsoft says parts of the purchase and management API are preliminary and may change before general availability.
4. Check each customer's market and segment. Usage-based billing doesn't apply to education, nonprofit or GCC low, or to the markets excluded at launch.
5. Explain to customers that the 4,000-credit default is a limit, not a fee, and that usage-based billing can be capped but not removed once configured.

For organizations without Microsoft 365: the new standalone offer lets you buy Copilot. Before you do, find out which Copilot features you'll actually get without the Microsoft 365 apps, which Microsoft says still shape the experience.

The purchase rule is simpler from December 1, but billing has more parts. Watch the Copilot Business usage meter as closely as the seat count.