Understanding Microsoft True-Up, True-Down, and Contract Basics
Can I reduce (true down) my Microsoft 365 subscriptions, and when?
Yes. On your Enterprise Agreement anniversary, you can true down:
- Additional Online Services (e.g., Visio, Project, Power Apps, Dynamics, M365 F3) to as low as zero with 30–60 days’ notice
- Enterprise Online Services (e.g., M365 E3/E5/E7) down to the quantity listed on your Product Selection Form at signing (the “floor”)
Microsoft sometimes accepts reductions below the floor, but can also enforce it. Plan reductions 30–60 days before the anniversary for smooth processing.
What is the enterprise subscription “floor” and how do I work around it?
The floor is the minimum quantity of Enterprise Online Services (e.g., E3/E5/E7) defined on your Product Selection Form at contract signature. If your needs fall below that, you can:
- Reduce to the floor
- Shift excess seats to cheaper qualifying Enterprise Online Services to meet the floor at lower cost
- Push for exceptions when data supports it
What are Additional Online Services versus Enterprise Online Services?
Enterprise Online Services include core suites like Microsoft 365 E3/E5/E7. Additional Online Services include add-ons such as Visio, Project, Dynamics, Power Apps, and often M365 F3. Additional services can be reduced to zero at anniversary with notice; enterprise services are subject to the floor.
How do ramped payment deals affect my renewal baseline?
In ramped deals, Year 1 is the lowest cost and Year 3 is the highest. Microsoft often anchors renewals to the highest (Year 3) price — not your three-year average. If you model your budget off the average, you can be underprepared. Always model renewals using the highest ramp year as the baseline.
Finding and Fixing License Waste
Why do different user counts in AD, Entra ID, and M365 matter?
Disagreements between Active Directory enabled users, Entra ID active logins, and M365 assigned/usage data create gaps that drive overpayment. Typical findings include 15–20% waste from stale accounts, shared or service identities wrongly licensed, or licenses assigned where no usage exists. Reconciling these systems exposes both savings opportunities and compliance risks.
How much waste is common in real environments?
Assessments frequently uncover 15–20% waste. Real-world examples include:
- A client with 7,200 AD users, 7,900 active Entra users, but 8,400 M365 licenses — roughly a 15% gap costing ~$500K/year
- A retailer where 21% of store staff had no M365 usage, enabling a seven-figure reduction
- A 1,000-user firm with ~50 E5 licenses on shared mailboxes and two dozen unneeded service-account licenses
Which patterns most often indicate overspend?
Watch for these common signals:
- M365 portal license counts exceeding internal verified user needs
- Enabled AD accounts with no M365 usage
- Kiosk or shared-device users licensed with E3/E5 instead of F3 or device-based options
- Duplicate assignments (e.g., E3 and F3 on the same user)
- Large add-on pools (e.g., Power Apps) with minimal active users
How can I safely move users from E to F licenses or cheaper options?
Use data to segment users. Confirm device context (kiosk/shared vs. assigned PC), actual app usage (Office, Teams, Outlook), and job roles (e.g., contractors, retail associates). Pilot changes with a small cohort, address required exceptions (e.g., Outlook, macros, full desktop apps via shared device licensing), then scale. Always validate end-user impact before making widescale changes.
Data-Driven Approach and Governance
What data should I combine to right-size Microsoft 365?
Blend the following data sources:
- Active Directory enabled users
- Entra ID sign-in activity and attributes (e.g., job codes, departments, contractor flags)
- M365 license assignment and usage via APIs/reports
- Contextual data such as device inventory (kiosk vs. assigned), Power Apps/Power BI usage, and organizational plans (e.g., Copilot rollout)
Analyze intersections across these sources to spot outliers and right-sizing opportunities.
How often should I review my licensing data?
Continuously, with at least 60–90 day checkpoints. Start optimization 3–9 months before your anniversary to maximize leverage, allow time for change management, and meet notice windows. Ongoing monitoring prevents re-inflation — for example, catching new license orders when cleanup capacity still exists.
How do I align IT, Procurement, and Finance to avoid surprises?
Create a shared, validated count traced to source data. Document discrepancies, agree on buffer policies, and synchronize PO/budgeting with actual consumption, reservations, and true-up/true-down actions. Ensure Finance models ramped years correctly and Procurement negotiates from a right-sized baseline — not inflated historical counts.
What is the green/yellow/red readiness framework?
- Green: Reconciled counts across sources, documented deltas, cross-team alignment, and budget impact understood
- Yellow: Some conflicts or missing data; issues are known but not fully resolved
- Red: No traceable source, unclear data ownership, and high likelihood of overpayment
Aim to reach green status before your next anniversary.
Common Pitfalls and Compliance Risks
Why doesn’t license assignment always equal license need?
Assignment only shows what’s provisioned, not what’s required. Some services operate at the tenant level without per-user assignment (e.g., Intune Remote Help). Reducing licensed counts to match assigned seats can create non-compliance if the service is enabled tenant-wide. Always understand entitlement rules and how a service is licensed before making reductions.
How can proposals and renewals get inflated?
Vendors often quote to your historical maximum or Product Selection Form quantities — not current active usage. Proposals may include unassigned or unused quantities and add-ons you no longer need. Insist on a data-backed baseline using active usage and validated headcount, and remove surplus before negotiating discounts.
What recent pricing changes should I anticipate?
Level D removal increased E-suite pricing ~15% for affected customers, and M365 F licenses are increasing ~25% on July 1. Combined with ramp structures and Copilot/E7 pushes, these changes can materially lift your run rate. Use data-led reductions and product mix adjustments to offset increases before renewals.
Are Microsoft audits increasing again?
Yes, audit activity is picking up. Areas of focus include tenant-level services enabled without matching entitlements and misaligned assignments (e.g., service or shared accounts). Maintain clear evidence of entitlement, usage, and reductions tied to contract terms to mitigate audit risk.
Actionable Steps and Examples
What are practical steps to reduce my next true-up bill?
- Reconcile AD, Entra ID, and M365 usage to build a single validated count
- Identify and remove stale, shared, and unneeded assignments
- Segment roles (contractors, retail/frontline, kiosk users) and downshift licenses where appropriate (E to F, device, or shared)
- Right-size Additional Online Services to zero if unused
- Prepare 30–60 days before your anniversary and execute true-down orders
- Establish continuous monitoring to prevent license re-creep
How do I evaluate Copilot or E7 commitments without overbuying?
Align purchases to a concrete rollout plan: pilot size, timelines, target roles, and expected usage. Compare outright licenses vs. pay-as-you-go for limited scenarios (e.g., agent access). Model how long a discount takes to be erased by under-deployment. Only commit to quantities you can realistically deploy within a defined schedule.
When should I start if my anniversary is close?
Start now. Even inside 30–60 days you can take data-driven reductions, though options narrow and change management becomes harder. If you miss the notice window, build governance immediately for the next cycle and explore negotiable paths (e.g., shifting mix within Enterprise Online Services) to soften spend in the interim.
What results have organizations achieved using this approach?
- 21% reduction in in-store licensing for a large retailer by identifying non-using roles
- $1.5M reduction in M365 spend in year two, and an additional $0.5M in year three for an EA customer
- 7% savings by moving from EA to CSP once data confirmed safe reservation handling
- Avoided a $672K compliance mistake by recognizing tenant-level licensing on a remote help tool
Is Your Microsoft Licensing Data Telling You the Full Story?
Many organizations are overpaying on their Microsoft True-Up without realizing it — because the data they’re working from doesn’t accurately reflect their environment.
Our team specializes in validating user counts, identifying discrepancies across Active Directory, Entra ID, and Microsoft 365, and building a stronger foundation for your next True-Up and renewal cycle.
Connect with our team to find out where your gaps are — before your next anniversary date.
