Reassigning licences: how often you can actually move them in 2026: Everything You Need to Know in 10 Minutes

The essentials 💡

Understanding the complexities of Reassigning licences: how often you can actually move them is a foundational skill for any modern IT administrator or procurement specialist. In the current landscape, Microsoft enforces strict temporal boundaries on how frequently a license can jump from one "Licensee" or "Device" to another. While the cloud has made assignment feel instantaneous, the legal framework governing these assets remains rooted in the "90-day rule," a policy designed to prevent organizations from using a small pool of licenses to cover a large, rotating workforce.

For organizations operating in 2026, the stakes for non-compliance have never been higher. As Microsoft pivots toward more automated auditing via the Microsoft 365 Admin Center and Azure portal, tracking the movement of assets is no longer a manual task for the vendor. If your organization is frequently transferring Office licenses between employees 2026 guidelines suggest you must maintain rigorous documentation to prove these moves coincide with permanent staffing changes rather than temporary shifts. Failing to do so can lead to significant financial exposure during a true-up or a formal SAM audit.

This roundup serves as your definitive guide to the "cooldown" periods of various Microsoft products. We will break down the differences between user-based subscriptions, perpetual volume licenses, and the rigid nature of OEM software. By the end of this guide, you will have a clear framework for when you can legally hit the "reassign" button and when you must wait for the clock to run out.

Recent changes worth knowing 🔄

The most significant shift in recent years involves the hardening of the 90-day rule across hybrid environments. While Microsoft licensing 90-day rule explained in older manuals focused heavily on physical servers, the 2026 context applies this to virtualized instances and user-based SaaS seats. Microsoft has clarified that "reassignment" does not mean "sharing." A license is assigned to a specific user or device, and that entity owns the right to use the software for a minimum period.

Another major change is the integration of license mobility rights for server workloads in 2026. Previously, moving a license to a cloud provider required complex "Bring Your Own License" (BYOL) paperwork. Now, through the Flexible Virtualization Benefit, customers with Software Assurance (SA) have more leeway to move licenses to authorized Outsourcers. However, without SA, the 90-day lock remains ironclad for products like SQL Server and Windows Server. If you are reassigning SQL Server licenses without SA, you cannot move that license to another physical host in your cluster more than once every 90 days, effectively killing your ability to use high-availability features like vMotion or Live Migration without full coverage.

"Reassignment is not a tool for load balancing; it is a tool for lifecycle management. Treat every reassignment as a permanent change until 90 days have passed." — Senior Licensing Consultant Observation

Furthermore, the transition from legacy Open Value programs to the Cloud Solution Provider (CSP) model has changed the mechanics of reassignment. In the CSP world, while you can suspend and reassign seats, the CSP license reassignment frequency limits are often governed by the underlying subscription term (Monthly vs. Annual). While you can move a seat to a new user, you cannot decrease the total seat count mid-term in an annual commitment, which is a common point of confusion for procurement teams.

Quick decision framework 📊

Navigating the rules for moving Windows 11 Pro retail to another PC or reassigning a M365 seat requires a structured approach. Use the following framework to determine if your move is compliant:

• Identify the License Type: Is it OEM, Retail (FPP), or Volume Licensing (VL)?
  • OEM: Non-transferable. It lives and dies with the original motherboard.
  • Retail: Transferable once every 90 days.
  • Volume: Transferable once every 90 days, with specific exceptions.
• Verify the Trigger: Why is the license moving?
  • Hardware Failure: If the device is permanently inoperable, the 90-day rule is waived. You must document the disposal or repair record of the original machine.
  • Staff Turnover: For user-based licenses, if User A leaves the company, User B can take the license immediately.
  • Temporary Project: If you are transferring Office licenses between employees 2026 for a two-week project, this is generally a violation. Licenses must be assigned to the "primary user."
• Check for Software Assurance (SA):
  • Without SA, you are bound by the 90-day rule for almost all server products.
  • With SA, you may qualify for "License Mobility within Server Farms," allowing you to move licenses between servers as often as needed within a single server farm.

It is critical to note that "Retail" licenses (FPP) purchased from a store have the same 90-day restriction as Volume licenses. The only way to bypass the 90-day wait for server products is through active Software Assurance. For desktop applications, the rule is almost universal: 90 days or permanent hardware failure.

Cheat-sheet 📝

To keep your organization audit-ready, memorize these core principles of the Microsoft Product Terms for license transferability:

• The 90-Day Rule: The default waiting period for any license transfer. Once moved, the license is "locked" to the new device/user for three months.
• The "Dead Iron" Exception: If a computer's motherboard fries, you don't have to wait 90 days. You can move the Retail or Volume license to a replacement machine immediately. Note: This does NOT apply to OEM.
• User vs. Device: User-based licenses (like M365 E3) follow the human. Device-based licenses (like Office LTSC) follow the hardware. Don't mix the logic between them.
• SQL Server Gotcha: When reassigning SQL Server licenses without SA, you cannot follow a VM as it moves across hosts in a cluster. You must license every host the VM *could* touch, or wait 90 days between moves.
• Documentation: Always log the date of reassignment, the source ID, and the destination ID. In an audit, the burden of proof is on you to show that a license hasn't been moved multiple times within a 90-day window.

Reassignment Scenarios at a Glance

Consider a scenario where a consultant joins for a 30-day contract. If you assign them a perpetual Office 2021 license, you cannot reclaim that license and give it to a new consultant on day 31. The license is effectively "consumed" by the first consultant's workstation for the full 90-day term. For short-term needs, monthly CSP subscriptions are the only compliant pathway.

Where to dig deeper 🔍

For those managing large estates, the nuances of Reassigning licences: how often you can actually move them require checking specific legal documents. Start with the Microsoft Product Terms site (formerly the Product List and Product Use Rights). This is the "source of truth" that defines reassignment for every SKU Microsoft sells.

If you are exploring license mobility rights for server workloads in 2026, download the "License Mobility through Software Assurance" guide from the Microsoft Licensing website. This document details which products are "Mobility-enabled" and which require you to stay on-premises or within dedicated hardware environments.

Finally, for those dealing with CSP license reassignment frequency limits, consult your CSP Partner Agreement or the Microsoft Customer Agreement (MCA). These documents outline how the transition to "New Commerce Experience" (NCE) affects your ability to move and manage seats. Pay close attention to the "7-day window" for cancellations, which is often confused with reassignment rights—cancellation is about billing, while reassignment is about usage rights.

📊 Comparison