Right sizing for Microsoft 365 specifically is usually the highest value cost optimization move a mid market organization can make, because Microsoft 365 is almost always the largest single line item in the digital workplace stack. The same per user model that makes it easy to buy makes it easy to overspend. People are placed on the wrong plan tier, premium add ons overlap with capability already included, and seats linger after staff leave. Each looks minor on its own, yet together they inflate the bill every renewal cycle.
This guide focuses on the Microsoft 365 mechanics that matter for right sizing: plan tiers, frontline plans, add on overlap, and the buying route that governs how you change seats. It links up into the wider digital workplace cost optimization plan, because Microsoft 365 savings are the anchor of a stack wide engagement.
Why right sizing for Microsoft 365 specifically pays off most
Microsoft 365 typically carries the largest seat count and the widest range of plan tiers and add ons in the stack. That scale means a small percentage of waste is a large absolute number. It also means the levers are well defined. Plan tiers, frontline editions, and add ons each map to a specific right sizing action, so the work is precise rather than guesswork. Correcting them before renewal is where the real money is recovered.
Match the plan tier to real usage
The most common Microsoft 365 waste is paying for E5 where E3 would do. E5 adds advanced security, compliance, voice, and analytics on top of E3. Those features earn their cost only when they are deployed and used. If your E5 seats show no usage of the advanced security or compliance capability, and you run separate tools for those needs, the E5 premium is waste. The fix is to measure feature level usage, identify E5 seats that behave like E3 seats, and downgrade them at renewal.
Source: Microsoft 365 enterprise plan documentation and pricing, as of June 2026. Plan contents and prices change often, so confirm current E3 and E5 inclusions and list prices on Microsoft official pages before you decide.
This is not an argument against E5. For organizations that genuinely use its security and compliance stack, E5 can consolidate several tools and save money overall. The point is to base the tier on measured usage, not on a blanket rollout. The related plan mixing approach is covered in our Microsoft 365 cluster.
Use frontline plans where they fit
Microsoft offers frontline plans, the F1 and F3 editions, for staff who do not need the full desktop and productivity suite, such as shift workers and deskless roles. Placing those users on an enterprise E plan is a frequent and expensive mismatch. Identify roles that need only core communication and lightweight access, and move them to the appropriate frontline plan. The saving per seat is large and the capability still fits the role.
Cut add on and security overlap
Microsoft 365 add ons are a quiet source of overspend. Buyers stack add ons for security, compliance, or voice that duplicate capability already inside their plan, or that overlap with third party tools they also pay for. Map every add on against what the base plan already includes and against any standalone tool covering the same need. Where the capability is duplicated, drop the add on or the overlapping tool. This connects directly to the broader question of quantifying shelfware for the business case.
Reclaim inactive and orphaned seats
Like any seat based model, Microsoft 365 accumulates seats assigned to people who left or never adopted the tools. Reconcile your assigned seats against your active employee list and sign in activity, then reclaim the orphaned and dormant seats. Tying this to right sizing and employee offboarding keeps the count accurate going forward rather than rebuilding the waste.
Mind the buying route and renewal mechanics
How you can change seats depends on your agreement. Common routes include the Enterprise Agreement, the Cloud Solution Provider channel, and the Microsoft Customer Agreement. The Enterprise Agreement uses true up and true forward mechanics, which affect when and how you can reduce counts, so the timing of any reduction matters. Understand your agreement reduction windows before you plan the right sizing, because the contract, not just the usage data, decides when savings can land. This is commercial guidance, not legal advice, so confirm contract terms with your own counsel.
Sequence the Microsoft 365 right sizing
Work in order. Measure feature level usage to find E5 seats that behave like E3. Identify frontline eligible roles. Map add on and security overlap. Reconcile seats against active staff. Total the recoverable spend, then schedule the changes to land at the right point in your agreement. Right size first, then negotiate the renewal from the corrected baseline, then govern so the savings hold. For the general method see SaaS license right sizing and measuring SaaS license utilisation.