The Microsoft Product Terms permit reassignment of most licenses but constrain it with a default minimum holding period and a default reassignment window. The defaults are written for Microsoft. The contract is where the buyer rewrites them. Most enterprises run a pool that violates the default rules without realizing it and a reassignment policy that loses dollars they were entitled to recover. The asymmetry is unnecessary.
The default Microsoft Product Terms state that a license assigned to a user or device may only be reassigned after a minimum of ninety days, unless the reassignment is due to permanent reassignment or the original user leaves the organization.
A license assigned to a user must remain with that user for at least ninety days before it can be reassigned to a different user for general purposes. The clock resets at each new assignment.
The default Product Terms list specific cases where the ninety day rule does not apply. Most enterprises overlook these and constrain themselves unnecessarily.
The default rule was written for a different commercial era. Modern EA buyers who run dynamic licensing groups, frequent contractor cycles, and a clean leaver process should negotiate a different rule into the contract.
Negotiate the standard reassignment window down from ninety days to thirty days for all Microsoft 365 and Defender SKUs in scope. Microsoft will accept this for most large EA renewals because the rule is not commercially load bearing.
Negotiate additional exception categories beyond the default three. Contractor end, internal role change, and pooled reabsorption are all worth specifying.
For seasonal or training populations, negotiate the reassignment window to zero on identified SKUs. Microsoft frequently agrees for Teams Phone, Power BI Pro, or training tier products that are not contested elsewhere.
The reassignment rule is one of the cleanest evidentiary fields in a Microsoft audit. The assignment history is in the tenant. The auditor will pull it.
The audit pattern that fails the buyer is a license that cycles through three or four users inside ninety days with no documented exception. Each rotation is a Product Terms violation, and the auditor will count each one as a separate unlicensed use event.
The remediation is rarely a license purchase. The remediation is documentation of which exception applied to each rotation. Buyers who keep the ledger close the finding with no settlement. Buyers who do not keep the ledger settle for the assumed violation count.
The defensible position is a per user reassignment ledger that records each assignment, the trigger event, the exception category if any, and the date. The ledger does not need to be a separate system. Entra ID audit logs combined with HR feed records reconstruct it.
The discipline is to make the reconstruction routine before an audit triggers it. The monthly pooling reconciliation is the right cadence. The output is a ledger ready at any time for an auditor.
The reassignment rule is one of the cheapest contracting concessions Microsoft makes. The friction is not on the Microsoft side. The friction is that most buyers do not ask.
The negotiated clause goes into the EA amendments section. The language reduces the standard window to thirty days, lists the expanded exceptions, and names specific SKUs that move to zero. The drafting is straightforward and Microsoft has accepted variants of this language at every concession band we have negotiated.
The carve outs matter as much as the headline number. The pool reabsorption exception, in particular, removes the largest practical risk for an enterprise running aggressive operational discipline.
The contracted language is half the work. The other half is the operational ledger that demonstrates compliance. We stand up the ledger as part of the pooling implementation, integrate it with HR triggers, and run the first reconciliation alongside the customer team.
The result is a buyer who can hand Microsoft a clean reassignment record at any audit moment, with the contracted exceptions clearly mapped. The conversation shifts from defending the practice to defending the contract that already permitted it.
Sample contract language for the thirty day reduction, expanded exception list, and SKU specific zero day windows. Sent on request alongside our reassignment ledger template.
The clause does not require waiting for a renewal. A mid term amendment can introduce the reassignment language for the remainder of the EA term.