Do true-up mechanics only work in one direction (adding, not removing)?

This varies by agreement type, some enterprise agreements are structured to true up annually based on actual headcount in both directions, others are less flexible, check your specific agreement.

Is it common to be on a higher tier than needed?

Yes, tiers bundling premium security or compliance features are commonly adopted company-wide when only a subset of users or teams actually need those specific capabilities.

Can different departments be on different tiers?

Often yes, mixed licensing across tiers is a common right-sizing approach when usage needs genuinely differ across teams.

What's the biggest source of overpayment in agreements like this?

Unused premium add-ons bundled into a higher tier that was adopted for one specific feature, without unbundling analysis at renewal.

Vendor Guide6 min readBoris, FounderPublished 26 March 2026, updated 31 August 2026

Microsoft 365 Renewal Negotiation: What Buyers Should Know

Why a bundle makes tier fit hard to see, and what a component-level usage breakdown changes.

Microsoft 365 bundles email, storage, collaboration, and security add-ons into a single tier, which makes it genuinely hard to tell which component is earning its place and which is just along for the ride.

Where a Microsoft 365 agreement is actually decided

Quiet months

True-up and prep

Notice window

Term startRenewal date

Licence mix reviewed by tierHighest yield

E3 against E5 across the estate, not one blended number.

Total seat count challengedModerate yield

Leavers and dormant mailboxes rarely leave the count on their own.

Discount asked for lateLow yield

Inside the notice window the term is effectively already set.

The expensive part of a Microsoft agreement is usually the tier people sit on, not the number of people.

Where the value sits in a Microsoft 365 agreement, and when it can still be moved.

Why the bundle hides the real usage picture

Tiered plans (Business, Enterprise E1/E3/E5-style tiers) that bundle a wide range of services at each level, enterprise agreements with annual true-up mechanics tied to headcount, and premium security or compliance add-ons that may have been included in a higher tier without a clear decision to actually use them.

Tier questions worth asking component by component

Are we on the right tier for what we actually use, or paying for a higher tier mainly for one or two features
Has our true-up process accurately reflected actual headcount changes, in both directions
Are premium security or compliance add-ons being actively configured and used, or sitting unconfigured
Would a mix of tiers across different employee groups (rather than one tier company-wide) better match actual usage

Breaking the bundle apart before negotiating it

Because these agreements bundle so much, the clearest lever is usually a tier-by-tier usage breakdown: confirming which specific services within the bundle are actually delivering value, rather than negotiating the bundle as a single unit.

Common questions

Keep reading

In-depth GuideRight Sizing SaaS Contracts With Real Usage Data

Why seat count and real usage are two different numbers, and how involving the business users unlocks savings that spend data alone misses.

In-depth GuideThe SaaS Spend Audit Playbook

A step by step audit for uncovering forgotten SaaS contracts, duplicate tools, and hidden software spend nobody is currently tracking.