True-up vs True-down: What You Can and Cannot Reduce in Microsoft Licensing

Understanding the Mechanics of True-up vs True-down 📊

In the complex ecosystem of Microsoft Volume Licensing, two terms frequently surface during budget season: True-up and True-down. While They sound like simple opposites, the reality is dictated by rigid contractual frameworks that can either empower a growing organization or trap a shrinking one in unnecessary costs. Understanding these mechanisms is the difference between an optimized IT budget and "shelfware"—software bought but never used.

For the uninitiated, a True-up is an annual reconciliation process, most commonly associated with the Enterprise Agreement (EA). It allows organizations to deploy software as needed throughout the year and then "square up" with Microsoft on an annual anniversary. Conversely, "True-down" refers to the ability to reduce license counts when headcount drops or projects end. However, Microsoft’s policy on True-downs is notoriously stricter than its policy on True-ups, creating a potential financial liability for the unwary CIO.

Key Insight: Microsoft licensing is designed for growth. The True-up mechanism is a courtesy for expansion, but the True-down functionality is often restricted to protect Microsoft's recurring revenue streams.

The Enterprise Agreement Trap: Why You Can’t Always Reduce 🔐

The Enterprise Agreement (EA) remains the flagship vehicle for large-scale licensing. Within this framework, the True-up is a mandatory annual checkpoint. If your organization started the year with 1,000 Microsoft 365 E3 seats and ended with 1,200, you have 30 to 60 days from the anniversary date to report those 200 additional seats and pay for them.

However, the concept of a "True-down" in an EA is largely a myth for core Enterprise products. Here is what you need to know about the limitations:

• The Baseline Rule: When you sign an EA, you establish a "Baseline" (the number of seats at the time of signing). You cannot reduce your seat count below this baseline for the duration of the 3-year term.
• Additional Products vs. Enterprise Products: While you can sometimes reduce quantities of "Additional Products" (non-core items like Visio or Project), "Enterprise Products" (Windows, Office, CAL Suites) are locked in.
• The Anniversary Window: You can only reduce the number of extra seats you added above your baseline at the anniversary. For example, if you moved from 1,000 to 1,200, and then back to 1,100, you can "True-down" that extra 100 on the anniversary, but you still cannot go below the original 1,000.

Admins must proactively track departures. If an employee leaves, their license should be marked for "re-harvesting." Instead of purchasing a new license for a new hire during the True-up, you assign them the vacant license. This is the only way to effectively "lower" your future True-up bill within an EA.

CSP NCE: The New Rules of Seat Reduction ⏳

With the shift toward the New Commerce Experience (NCE) in the Cloud Solution Provider (CSP) program, the rules for reduction have become even more granular. In the old CSP "Legacy" model, you could add or remove seats daily. Under NCE, Microsoft has enforced "commitment terms" that mirror the rigidity of the EA but at a smaller scale.

The 7-Day Window: The Only Opportunity for True-down

In CSP NCE, if you purchase an annual commitment of Microsoft 365 Business Premium, you have exactly 168 hours (7 days) to reduce that seat count or cancel the subscription. Once that window closes, you are financially committed to those seats for the full 12 months. There is no True-down mid-term.

Monthly vs. Annual: The Cost of Flexibility

To gain the ability to True-down at any time, Microsoft forces a choice: pay a 20% premium for a "Monthly Term." This is often the most strategic move for organizations with seasonal staff or high turnover. By paying 20% more, you gain the right to reduce seat counts at the end of every month. For stable staff, the Annual Term (locked seat count) is usually the better financial move.

• Annual Commitment: Lower price, locked count for 12 months (True-up only).
• Monthly Commitment: 20% higher price, True-down allowed every 30 days.

Smart procurement officers use a "Hybrid Strategy": They put 80% of their stable workforce on Annual commitments and the remaining 20% of "swing" capacity on Monthly commitments to allow for effective True-downs.

Strategic Step-ups and the Step-down Barrier ⚖️

What can you actually change during a True-up? It isn't just about the number of seats; it's about the value of those seats. Microsoft allows "Step-ups," which are a vital part of the True-up process for organizations maturing their security infrastructure.

A Step-up License allows you to transition a user from a lower-tier product (e.g., Office 365 E3) to a higher-tier product (e.g., Microsoft 365 E5). During your True-up reconciliation, you can report these transitions. This is often more cost-effective than buying a brand-new E5 license because you only pay the "gap" in price between the two editions.

What You Cannot Step-down

Conversely, "Step-downs" (moving from E5 back to E3) are generally prohibited mid-term in both EA and CSP NCE. Once you have upgraded a user to a higher service level, you are typically committed to that premium price until the end of your contract term. This is why "trialing" E5 features using a trial tenant is critical before committing to a permanent upgrade during a True-up cycle.

Optimizing Costs: License Harvesting is Your "Virtual" True-down 💡

When organizations undergo mergers, acquisitions, or divestitures, the True-up and True-down rules become even more critical. In a divestiture where a company spins off 30% of its workforce, a standard Enterprise Agreement can become a massive liability because the "Baseline" doesn't automatically drop with the headcount.

To mitigate this risk, IT leaders should focus on License Harvesting. This is a technical process, not a procurement one. It involves:

1. Identifying Inactive Users: Use the M365 Admin Center to find users who haven't logged in for 30+ days.
2. Automating License Revocation: Use PowerShell or Entra ID (formerly Azure AD) groups to automatically pull licenses from disabled or terminated accounts.
3. Pooling: Maintaining a pool of unassigned licenses to satisfy new requests rather than triggering a True-up purchase.

Without a rigorous harvesting process, the "license bloat" during a True-up can become astronomical. Statistics from license optimization audits suggest that up to 22% of SaaS licenses in an enterprise environment are either underutilized or assigned to former employees.

Practical Guidance for IT Admins and Procurement 🛠️

Managing the True-up vs. True-down dynamic requires a proactive calendar. Waiting until 30 days before your anniversary to count your seats is a recipe for disaster. Organizations should maintain a "Shadow True-up" spreadsheet throughout the year.

Quarterly Review Checklist:

• Review Entra ID logs for inactive users.
• Compare HR "Joiners and Leavers" reports against license assignment counts.
• Evaluate upcoming projects that may require "Additional Products" like Power BI Pro or Project Plan 3.
• Assess if any "Monthly" CSP seats can be converted to "Annual" to save that 20% premium.

Finally, remember that the only time you have 100% leverage to True-down and reset your baseline is at the Renewal. At the end of the 3-year EA or 1-year CSP term, you can re-architect your entire stack. This is the moment to prune unnecessary features, move users to lower tiers, and set a new, leaner baseline for the next cycle.

Notice: This guide is for informational purposes. Licenses should only be acquired through Retail or Volume Licensing channels. Standalone OEM keys are not sold individually to end-users and should be avoided as they violate Microsoft distribution terms.

📊 Comparison