If your Microsoft 365 sits on an Enterprise Agreement, true up and true forward are the mechanics that decide what you pay as your usage changes during the term. Getting Microsoft 365 true up and true forward explained clearly matters because these processes are where uncontrolled seat growth turns into a bill, and where a small amount of governance saves a large amount of money. They are not penalties. They are reconciliation, and reconciliation rewards the buyer who has been counting.
This is a Microsoft specific mechanic, but the discipline behind it, knowing your real usage before a contract event, applies across the stack. That is why Enterprise Agreement decisions should connect up to the bundled digital workplace cost optimization view.
What a true up is
An Enterprise Agreement lets you add users and products during the year and reconcile them periodically rather than transacting each change. A true up is that reconciliation: you report the additional quantities you deployed above your baseline, and you pay for them. The key point for buyers is that the true up counts what you actually have, so inactive and over assigned seats get paid for unless you clean them up first.
Why true ups inflate
True ups inflate when seat growth runs unmanaged through the year. People join, projects spin up licences, and assignments are rarely reclaimed when they end. By the time the true up arrives, the count includes a layer of seats nobody actually uses. You pay for the gross number, not the net of what you need, unless you have reclaimed the unused seats before reporting.
What a true forward is
A true forward applies to additions made late in the agreement term. Rather than paying for a partial period, additions made in the final stretch can be carried forward and paid from the next anniversary, which can change the economics of when you add seats near the end of a term. The practical takeaway is that timing matters: when you add capacity relative to your anniversary affects what you pay for it.
How to avoid overpaying at reconciliation
The single most effective move is to reclaim unused seats before you report. Run a usage review ahead of the true up, identify assigned licences with no genuine activity, and remove them so they never enter the count. This is ordinary licensing hygiene, and it is the difference between truing up to your real need and truing up to your accumulated waste.
Second, track seat growth continuously rather than discovering it at reconciliation. A live count of assigned against active seats means no surprises. Third, plan additions around the anniversary so the true forward mechanics work for you rather than against you. None of this is exotic. It is counting, done before the vendor counts for you.
A note on plan mechanics
Microsoft adjusts its agreement programs and reconciliation rules over time, and the exact mechanics depend on your specific agreement and buying route. Treat the descriptions here as the general shape of how Enterprise Agreement reconciliation works, and confirm the precise terms against your own contract.
Source: Microsoft Enterprise Agreement program terms and true up guidance, microsoft.com licensing documentation, as of June 2026. Confirm specifics against your own agreement.
Microsoft 365 true up and true forward explained in practice
True up and true forward are reconciliation events, which makes them natural moments to right size. The same review that prepares you for a true up also surfaces the wrong tiers and unnecessary add ons you may not need, and the Power Platform commitments in Microsoft 365 Power Platform licensing costs. Our Microsoft 365 optimization service prepares clients for reconciliation so they true up to real need, not accumulated waste, and feeds the result into the bundled stack wide engagement.