Every Microsoft Enterprise Agreement true up is a small, recurring negotiation. The seller arrives with a proposed quantity calculated from their view of your tenant. You arrive with the quantity that reflects your view of consumption, your downgrade rights, your reassignment posture, and your right to true down the categories that contract allows. True up preparation is the work that closes the gap between those two numbers, on your terms, before the order is even drafted.
The Microsoft EA true up is treated by most customers as a procurement formality. The seller produces a quantity, the customer validates it lightly, the order issues, the payment processes. That motion is the path of least resistance, and it is the path that systematically overstates the obligation. The true up is a negotiable order, governed by contract terms that include downgrade rights, reassignment posture, persona segmentation, leaver process timing, and a set of options that compound across product lines.
Five categories of variance show up between the seller proposed true up and the customer defended true up. Persona over assignment, where users on E5 should have been on E3 during the qualifying period. Leaver lag, where deprovisioned users were not removed before the true up snapshot. Downgrade rights misapplied, where the contract permits a lower edition than the deployment shows. Reassignment posture, where licenses were moved within the estate but the seller record does not reflect the rebalance. Reserved license pools, where unassigned entitlement covers some of the proposed quantity.
Each category individually moves the order by a few percent. Together they routinely move it by 12 to 28 percent against the seller proposed number. The customer who runs the discipline captures the difference. The customer who does not pays the seller proposed number and explains the run rate increase to the CFO at the next budget review.
The seller proposed number is not adversarial. It is calibrated against the seller view of your tenant, which is structurally less current than your view. The seller cannot see leaver activity that happened after the snapshot. The seller does not know your reassignment work. The seller does not apply your downgrade rights without being asked. The number arrives high because the seller methodology produces high numbers absent customer correction.
Preparation produces the customer defended true up quantity per product line, with the methodology footnote and the supporting evidence. The customer arrives at the true up conversation with the order it expects to place. The seller can challenge specific lines. The seller cannot reset the conversation to the seller proposed quantity.
Across the practice, customers who ran the preparation discipline closed true up orders at a median 79 percent of the seller proposed number, with no material concession beyond reassignment posture and downgrade rights being applied. The work pays back inside the same true up cycle.
True up preparation runs in a tight 60 day window leading to the EA anniversary. Each phase produces the input to the next. Starting later than 60 days out compresses the discipline. Starting later than 30 days out converts the engagement into damage control.
Current entitlement reconciliation. Current deployment scan across M365, Azure, Dynamics. The starting baseline against which true up calculations will run.
Edition mapping by persona. E5 to E3 downgrade candidates. F3 candidates among current E3 users. Leaver process audit and provisioning cleanup.
The defended true up quantity per product line. Methodology footnote per line. The order the customer will propose to the seller.
The conversation with the seller. The seller proposed number challenged on the methodology lever. The closing order issued against the defended position.
The customer defended true up applies six levers per product line. Some apply only to certain products. Together the levers compose the methodology footnote that supports the proposed order.
Users assigned to E5 who only consume E3 capabilities during the qualifying period step down for the true up. The downgrade right is in the contract. The application of it requires evidence of consumption, which the preparation work produces.
Users deprovisioned during the qualifying period are removed from the count. The leaver process audit closes the gap between HR deprovisioning and license deprovisioning. The number is often 4 to 9 percent of the deployed quantity.
Unassigned entitlement in license pools absorbs incremental deployment up to the pool quantity. The pool tracking discipline determines whether the absorption is recognized by the seller proposed number or whether it has to be argued in.
Workers who qualify for F3 rather than E3 step down to the frontline SKU. The eligibility criteria are contract defined. The preparation work tests every E3 assignment against the F3 eligibility test and steps down where applicable.
Add on SKUs attached to base licenses are tested against actual consumption. Where the add on capability is unused, the add on is detached. Where the add on overlaps with another add on already attached, the redundancy is resolved.
Multi tenant estates often carry duplicate entitlement across tenants. The consolidation review identifies the duplication and reassigns where possible. The true up reflects the consolidated estate rather than the historical fragmented one.
The true up is not a number you accept. It is an order you propose. Customers who treat it as a negotiation save five to seven figures per cycle. Customers who treat it as paperwork pay the seller proposed number every year for the term.Managing analyst · True up and renewal practice
True up preparation is the same discipline as renewal preparation, applied to a smaller order with a tighter window. Customers who run the true up discipline well arrive at renewal with the consumption baseline, the persona segmentation, the leaver process audit, and the entitlement reconciliation already in current state. The renewal work compounds on top of the true up work.
The data infrastructure that powers true up preparation is the same data infrastructure that powers renewal posture work. The deployment scan, the persona segmentation, the leaver process audit, the pool tracking. Running the true up discipline annually keeps the infrastructure current and compounds the analytic value across cycles.
Enterprises that engage on true up preparation typically extend the relationship into renewal posture work in the 18 to 24 months following. The transition is natural because the data is already in place and the methodology is already understood by both sides of the engagement.
A three year EA carries three true up cycles and one renewal. Customers who run preparation on all three true ups arrive at renewal with three years of methodology footnotes, three years of defended order history, and three years of demonstrated discipline that the seller deal desk reads as a sophisticated counterparty. The renewal lands at a different concession band than the customer who let three true ups pass uncontested.
The compound effect is not a marketing claim. It is observable in the practice data. The renewal concession bands of customers who ran true up discipline trail higher in the distribution than peer customers who did not.
The same four questions surface at the discovery stage of every engagement in this service line. The short answers are below. The full conversation happens against the customer specifics on the first analyst call.
A reseller earns margin on what you buy from Microsoft. Our economics are inverted. We are paid by the customer to reduce or restructure what the customer commits to Microsoft. No SKU we recommend produces revenue for the firm. No customer outcome we deliver compromises a reseller relationship the firm does not hold. The advice is buyer side without qualification, and the engagement structure is built around that posture.
This is the reason most reseller produced analyses recommend keeping the SKUs the reseller earns the most on. Our analyses do not have that incentive. The recommendations follow the customer interest, full stop.
The engagement is buyer side and confidential. Analyst access to customer data runs against a signed NDA with the engagement entity, not against any Microsoft visible data sharing arrangement. The artifacts produced for the customer are not shared with Microsoft unless the customer chooses to share them in negotiation. The methodology footnotes are designed to be defensible if surfaced and silent if not.
The engagement does not surface to the customer Microsoft account team. The seller will see the customer producing better counter analysis than the seller proposed pricing accounts for. The seller will not see the source of the counter analysis unless the customer chooses to disclose it.
Most engagements run as a fixed scope, fixed fee, fixed timeline structure. The fee is set on day one against the scope agreed in the engagement letter. Success based or contingent fee structures are available for specific engagement types where the outcome is cleanly attributable, but they are the exception rather than the default. Buyer side advisory works best when the analyst incentive is to do the right thing rather than to maximize a contingent number.
The first two analyst calls are scoped at no fee and produce the engagement letter only if the fit is right. We do not propose engagements we cannot deliver the outcome on.
The customer provides access to the contract record, the procurement file, the relevant administrative telemetry, and a single point of contact who can authorize the data access and the stakeholder interviews. The engagement does not require dedicated customer resourcing beyond the point of contact. The analyst team runs the work and surfaces findings into the customer cadence.
The data access is scoped tightly. Read only telemetry is sufficient for most workstreams. Where elevated access is required, the engagement scopes the access against a specific runbook with the customer security team in the loop.
Two analyst calls. No pitch. We tell you what we would do, what the leverage actually is, and whether we are the right firm for this engagement.