Workplace AI

Microsoft is appending '(add-on)' to M365 Copilot CSP offer names from 16 October 2026: here's what breaks and what to fix

From 16 October 2026, Microsoft renames M365 Copilot CSP offers to include '(add-on)'. Scripts matching on offer name will silently break.

Microsoft Learn, Partner Center announcements documentation page logo

If you manage Microsoft 365 Copilot licences through CSP, or you have any scripts, catalogue mappings, or licence automation that reference offer names, there is something specific you need to do before 16 October 2026.

Microsoft announced on 14 October 2026 that it is appending “(add-on)” to the display names of two existing CSP offers: the current Microsoft 365 Copilot offer becomes Microsoft 365 Copilot (add-on), and Microsoft 365 Copilot Business becomes Microsoft 365 Copilot Business (add-on). The underlying product and SKU IDs, pricing, renewal terms, and auto-renew settings are not changing. Only the display name changes.

That might sound harmless. It is not, if your systems match on name rather than ID.

Why this creates a silent-break risk

Any PowerShell script, internal catalogue, RMM integration, or licence management workflow that identifies these offers by matching the text of their display name will stop finding them correctly from 16 October 2026. The offer is still there. The product and SKU IDs are identical. But if your code looks for a string called “Microsoft 365 Copilot” and that string now reads “Microsoft 365 Copilot (add-on)”, the match fails.

The problem is described as silent because the subscription itself keeps running. Renewals, billing, and the actual Copilot service are unaffected. What breaks is anything in your tooling that uses the name to identify, report on, or act on the licence. You might not notice until an automated report returns zero results, or a seat-count adjustment fails, or a customer quote pulls the wrong offer.

Microsoft’s explicit ask to partners is to update any scripts or automations that reference offer names so that they use product or SKU IDs instead, and to do so before 16 October 2026.

What you should do now

The fix is straightforward in principle: swap any name-based matching in your scripts and tooling for product ID or SKU ID matching instead. Microsoft will publish the new product and SKU IDs for the upcoming standalone offers ahead of the price list preview on 1 November 2026, but the existing add-on offers retain their current IDs, so you can make that change today.

A practical checklist:

  • Search your PowerShell scripts for any string matching on “Microsoft 365 Copilot” as an offer name filter.
  • Check your PSA, RMM, or licence management platform for catalogue entries that reference the offer by display name rather than by product or SKU ID.
  • Review any internal documentation, quoting templates, or approval workflows that might pull offer names from Partner Centre.
  • Do not migrate existing subscriptions or reassign licences. There is nothing to migrate. Existing customers are unaffected and no action is required on their behalf.

What happens on 1 December 2026

The name change on 16 October is a precursor to a more significant commercial change arriving 1 December 2026. On that date, the existing add-on offers reach end of sale in CSP. No new purchases will be possible through those offer IDs from 1 December onwards.

Replacing them are new Microsoft 365 Copilot and Microsoft 365 Copilot Business offers that do not require a qualifying Microsoft 365 base subscription. These standalone offers will be available across all CSP channels, including commercial, education, government, and nonprofit segments. The pricing is the same as the current add-on offers. They will carry their own product and SKU IDs, which Microsoft will share ahead of the 1 November 2026 price list preview.

End of sale is not end of life. Existing customers on add-on subscriptions can continue to renew and adjust seat quantities as normal. They do not need to move to the new standalone offers. The “(add-on)” label simply stays in the name of their subscription indefinitely.

The usage-based billing change worth noting

From 1 December 2026, new Microsoft 365 Copilot Business licences purchased through CSP will have usage-based billing enabled by default. This applies to both standalone licences and bundles. Each new licence will include the Azure subscription setup needed for pay-as-you-go billing. If you manage Copilot Business deployments for customers, this is worth flagging in your onboarding process.

Microsoft is opening Partner Centre sandbox environments on 2 November 2026 for partners who want to test usage-based billing before it goes live.

The bigger picture

The “(add-on)” label reflects what these offers have always been: licences that required a qualifying Microsoft 365 base subscription. The December standalone offers remove that dependency, which makes Copilot easier to position for customers who are not already on a qualifying M365 plan.

For partners, the commercial opportunity is broader from 1 December. But the immediate task is purely operational: check your name-matching code before 16 October 2026, replace it with ID-based matching, and you will not have anything to worry about when the names change.

The Partner Centre October 2026 announcements page has the full detail, including the specific announcement titled “Copilot offers and name updates” dated 14 October 2026.