Microsoft 365 add ons let you bolt capability onto a base plan, but they also overlap E5 in ways that quietly bill you twice. Here is every add on and where the duplication hides.
Microsoft 365 add ons attach extra security, voice, compliance, and analytics to a base plan, but several of them duplicate features already bundled inside E5, so buyers often pay for the same capability twice.
This guide is for license managers untangling a Microsoft 365 add on stack. Read it with the Microsoft licensing guide and the Microsoft Practice page.
A Microsoft 365 add on is a paid extension that attaches extra capability to a base user plan such as E3 or E5. Add ons cover security, voice, compliance, analytics, and Copilot. Microsoft lists the current set on its plans and pricing page.
Most add ons require a qualifying base plan and must be assigned to the same user. The prerequisites are defined in the Microsoft licensing terms, which set out which base plans each add on supports.
Add ons cluster into a few families. Knowing the family tells you fast whether E5 already covers it. Security and compliance are the families that overlap E5 most often.
Copilot is a per user add on that requires a qualifying base plan and is priced separately from E3 and E5. Microsoft documents it on the Microsoft 365 Copilot page.
Microsoft 365 add on families and E5 overlap
| Family | Examples | Overlaps E5? |
|---|---|---|
| Security | Defender, Entra premium | Often yes |
| Compliance | Purview, eDiscovery | Often yes |
| Voice | Teams Phone, calling plans | No |
| Analytics | Viva suite components | Partly |
| AI | Microsoft 365 Copilot | No, priced separately |
E5 already bundles advanced Defender, Entra premium, Purview compliance, and analytics. Buying those same capabilities as standalone add ons on top of E5 is the classic duplication, and it is common where teams buy tactically.
White Paper ยท Microsoft
The Microsoft EA Renewal Playbook
The buyer side framework for the 2024 to 2026 EA cycle. Read it in your browser.
List every assigned add on, then check each against the E5 component list in the Microsoft licensing documentation. Anything that appears in both is a candidate to drop.
Reconcile the add on stack against the base plan once a year. Drop add ons that duplicate E5, remove voice and analytics add ons on idle seats, and only keep standalone add ons where the base plan genuinely lacks the feature.
A standalone add on makes sense on an E3 base where only a few users need one premium feature. Buying the add on for those users beats upgrading the whole population to E5.
The standard reseller advice is to layer add ons freely because each one is small and targeted. We disagree. Across the 30 to 40 add on stacks Fredrik Filipsson reviewed in 2024 to 2025, standalone security add ons duplicated E5 features in 4 of 10 estates, and removing the overlap cut add on spend 15 to 30 percent. The buyer side move is to reconcile every add on against the base plan before each renewal, drop anything E5 already covers, and treat targeted add ons as the exception on E3 seats, not the default everywhere.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
An add on is only a saving when the base plan does not already include it. Most stacks fail that test.
A Microsoft 365 add on is a paid extension that attaches extra capability, such as security, voice, compliance, analytics, or Copilot, onto a base user plan like E3 or E5. It must be assigned to the same user as the base.
Security and compliance add ons most often duplicate E5, because E5 already bundles advanced Defender, Entra premium, and Purview compliance. Buying those as standalone add ons on top of E5 pays for the same feature twice.
No. Microsoft 365 Copilot is a separate per user add on that requires a qualifying base plan and is priced on top of E3 or E5. It is not bundled into the standard E5 seat.
List every assigned add on, then check each one against the E5 component list. Any capability that appears both as a standalone add on and inside an assigned E5 seat is duplicate spend you can remove.
A standalone add on makes sense on an E3 base when only a few users need one premium feature. Buying the add on for those users is cheaper than upgrading the whole population to E5.
In reviewed estates, removing duplicate and idle add ons cut add on spend by 15 to 30 percent. The saving depends on how many add ons overlap the base plan and how many sit on unused seats.
Yes. Most Microsoft 365 add ons require a qualifying base plan and must be assigned to the same user. The prerequisites are set out in the Microsoft licensing terms for each add on.
Review the Microsoft 365 add on stack at least once a year, before renewal. An annual reconciliation against the base plan catches duplication and idle add ons before the next term locks the spend in.
Microsoft renewal moves, the EA framework, the M365 SKU framework, the Copilot framework, and the buyer side moves across the full Microsoft estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
One short note on Microsoft renewal moves, license classification, M365 SKU posture, and the buyer side moves we are running in client engagements.
