MC1508148: Microsoft 365 Copilot Renames Add-on Subscriptions and Introduces Standalone Plans

MWPRO IMPACT SCORE
OPERATIONAL IMPACT
35
0 25 50 75 100
MODERATE IMPACT • ASSESS BUSINESS IMPACT
Recommended Action:
Take a look and decide whether this affects your tenant, users or support teams.
▶ What is MWPro Impact Score? Watch our 60‑second explainer

Primary Audience

Microsoft 365 AdminsTenant AdminsIT ManagersService Owners
Why this score?
AI Confidence
HIGH
Enough detail is available to trust this assessment.
Assessment Reasoning
This update changes Microsoft 365 Copilot subscription names to include ‘(add-on)’ where a qualifying Microsoft 365 base license is needed, beginning mid‑October 2026. No service or capability changes occur, but admins may need to update PowerShell scripts, automated license tools and internal documentation before the change date. User experience remains unaffected, making this mainly an administrative awareness and minor configuration update.
45
🛡️ Admin Impact
15
👥 User Impact
35
⚡ Urgency
30
🔧 Effort
ℹ️ WHAT YOU NEED TO KNOW
📌

AT A GLANCE

Microsoft 365 Copilot subscriptions that require a base licence will show “(add-on)” in their names from 16 October 2026. New standalone subscriptions arrive in December 2026.
👥

END USERS

No major end-user change expected.
🛡️

IT ADMINS

Review and update any scripts or internal documentation referencing old Copilot names before 16 October 2026.
📅

ROLLOUT TIMELINE

Start:
October 2026

📢 Official Microsoft Message Center Announcement


Microsoft 365 Copilot offer and name updates
Message ID: MC1508148

[What and Why:]

We’re updating Microsoft 365 Copilot subscription names to make purchasing requirements clearer.

Beginning October 16, 2026, existing Microsoft 365 Copilot subscriptions that require a qualifying Microsoft 365 base subscription will include “(add-on)” in their names. Examples include Microsoft 365 Copilot (add-on) and Microsoft 365 Copilot Business (add-on).

The “(add-on)” designation reflects the qualifying Microsoft 365 base subscription requirement for these existing subscriptions. Beginning December 1, 2026, new Microsoft 365 Copilot and Microsoft 365 Copilot Business subscriptions can be purchased without a qualifying Microsoft 365 base subscription. 

[Rollout Schedule:]

  • October 16, 2026: Microsoft 365 Copilot subscriptions that require a qualifying Microsoft 365 base subscription will include “(add-on)” in their names.
  • December 1, 2026: New Microsoft 365 Copilot and Microsoft 365 Copilot Business subscriptions can be purchased without a qualifying Microsoft 365 base subscription and will not include “(add-on)” in their names.
  • December 1, 2026: Existing add-on subscriptions will reach end of sale for new purchases. This is not end of life: You can continue to renew your subscriptions and add or reduce seats as you do today.
  • Existing subscriptions will retain “(add-on)” in their names.

[Impact on Your Organization:]

Who is affected:

  • Organizations with Microsoft 365 Copilot or Microsoft 365 Copilot Business subscriptions that require a qualifying Microsoft 365 base subscription.

Platforms/Services:

  • Microsoft 365 Copilot and Microsoft 365 Copilot Business subscriptions.

What will happen:

  • Existing subscriptions that require a qualifying Microsoft 365 base subscription will be renamed: 
  • Microsoft 365 Copilot (add-on)
  • Microsoft 365 Copilot Business (add-on)
  • Your subscription, service, pricing, licensing rights, and renewal eligibility remain unchanged.
  • No migration or license reassignment is required.
  • The name update does not change Copilot capabilities, which continue to depend on the apps and services you’re licensed for.
  • Self-service purchase (SSP) and end-user trials within Microsoft 365 products will continue to be available with this update.
  • Beginning December 1, 2026, new subscriptions without the qualifying Microsoft 365 base subscription requirement will be available without “(add-on)” in their names.

[Action Required/Recommendations:]

No action is required for most organizations.

  • Do not migrate subscriptions or reassign licenses solely because of the name update.
  • If you use PowerShell scripts or license management processes that reference product names, update them to use product or SKU IDs before October 16, 2026.
  • Consider updating internal documentation that references the current subscription names.

[Compliance considerations:]

No compliance considerations identified, review as appropriate for your organization.

Source: Microsoft Message Center • Analysed by MWPro

Share This Update