Headcount Dropped? Right-Size Licences Without Breaking Anything

Fix it now

Almost nothing on a term subscription can be reduced mid-term: seats come down only within seven days of being added, and otherwise at renewal. The expensive mistake is not the wasted months. It is deleting an account to free a seat and starting clocks on the mailbox and the OneDrive that were sitting behind it.

1. Check the window before reducing anything. A seat decrease is allowed only within seven days – 168 hours – of those licences being added, whether at purchase, renewal or mid-term.
2. Convert the mailbox before you remove the licence. A shared mailbox holds up to 50 GB with no licence assigned, which is the free retention route for most leavers.
3. Skip the licence entirely if the mailbox is under 50 GB and needs no archive and no hold. Above that it needs Exchange Online Plan 2, as does an archive or a litigation hold.
4. Move anything a colleague needs out of OneDrive within 60 days. After licence removal or user deletion it goes read-only at day 60 and is archived at day 93.
5. Buy nothing to keep a CAL. Microsoft’s terms permit reassignment inside the usual 90-day interval where it follows termination of the user’s employment or contract.
6. Reduce SQL Server only when cores or servers actually go, and not below the published minimum of four core licences per physical processor.

If the reduction is small and hiring is planned, reassign rather than reduce and stop here. Below is what can actually be cut and when, the order that preserves the data, and what happens to content once the licence is gone.

Why it happens

The first question is not which licences you want to drop but which ones the contract lets you drop. Subscriptions are term commitments: you have bought a seat count for a period. Perpetual licences and CALs are property: you own them whether or not anyone is using them, so reducing the count saves nothing because there was no recurring charge to stop. Mixing those two up produces the two classic mistakes, which are cancelling a subscription that still holds live data and trying to hand back a CAL that was never rented.

The second question is timing, and Microsoft publishes the answer precisely enough that there is no need to guess. Under new commerce terms a subscription can be cancelled with a prorated refund within the first seven days, stated as 168 hours, of any term. The licence count can be decreased only within seven days of when those licences were added – at initial purchase, at renewal, or mid-term. A redundancy in month two therefore costs you the remainder of the term for that seat no matter what you do, which is a strong argument for repurposing the seat rather than deleting accounts in a hurry. A paid-for seat handed to a new starter is the cheapest licence you will issue all year, and Microsoft’s online services terms accommodate exactly that: a reassignment for any purpose other than covering a temporary absence must simply run for the remaining term of the licence.

The third question is what happens to the data, and this is where a rushed reduction becomes irreversible. Deleting the user account starts a 30-day recovery window in Microsoft Entra ID, and a separate 30-day soft-delete window on the mailbox in Exchange Online. Those are safety nets for mistakes, not an archiving strategy. The OneDrive behind the account runs on a longer and less familiar clock: after licence removal or user deletion the account goes read-only at day 60, is archived or moved to the recycle bin at day 93, is no longer available in eDiscovery at day 275, and becomes subject to deletion after 365 cumulative unpaid days. The day-60 read-only stage is the one that catches people, because colleagues who were told the content was still available discover they can look but not change.

The free retention route for mail is the one most organisations skip because it looks like extra work rather than a saving. A shared mailbox stores up to 50 GB with no licence assigned. Above that it needs an Exchange Online Plan 2 licence to reach 100 GB. Adding an in-place archive or a litigation hold to a shared mailbox needs Plan 2, or Plan 1 with the Exchange Online Archiving add-on. Which of those you already hold is decided by your plan: Microsoft 365 Business Premium includes archiving with In-Place Hold and Litigation Hold, while Business Standard and Business Basic require the Exchange Online Archiving add-on.

So the sensible response to a headcount drop is an inventory rather than a cancellation spree. Count what you hold against what you now need, convert what can be converted for free, reassign what you own outright, and take the genuine reduction at the renewal date where the count can actually move.

Full reference

What can be reduced, and when

The order that keeps the data

Deleting a Microsoft 365 user account starts a 30-day recovery clock on the account and a 30-day soft-delete clock on the mailbox, and the OneDrive behind it goes read-only at day 60 and is archived at day 93. Once those pass the content is gone and no licence purchase brings it back. Convert or export before you delete.

1. Block sign-in and revoke active sessions. This ends access immediately and touches no data.
2. Set mail forwarding or delegate access if somebody needs to cover the role.
3. Convert the mailbox to a shared mailbox so the contents stay reachable without a licence.
4. Move or reassign the OneDrive content that other people need, and do it inside 60 days while the account is still writable.
5. Only then remove the licence.
6. Only after that, consider deleting the account – and place any required hold before you do.

Shared mailboxes: where the free route ends

CALs and perpetual licences do not shrink

If ten people leave and you hold thirty Windows Server User CALs, you still hold thirty. There is nothing to cancel and no refund to chase. What you gain is capacity: those CALs can be reassigned. Microsoft’s terms normally restrict reassignment to no sooner than 90 days after the last reassignment, and list the exceptions explicitly – permanent hardware failure or loss, termination of the user’s employment or contract, and temporary reallocation to cover an absence or an out-of-service device. A permanent leaver is squarely inside the second of those. Record the reassignment and the date when you make it, because the exception is only defensible if you can show when it was used.

Online services behave under a different sentence and it is worth reading it as written. A subscription licence may not be reassigned on a short-term basis, meaning within 90 days of the last assignment, except to cover a user’s absence or a device that is out of service. Reassignment for any other purpose must be for the remaining term of that licence – which is exactly what handing a departed employee’s seat permanently to their replacement is. There is no ninety-day wait on that.

Which route fits your situation

• A handful of leavers with hiring planned: reassign the seats for the remaining term. Reduce nothing.
• A large permanent reduction on an annual term: park the mail on shared mailboxes, leave the seats unassigned, and cut the count at the renewal date.
• Headcount that swings seasonally: ask for a monthly-term quote for the flexible portion and keep a stable core on annual terms.
• Departments closing entirely: export what must be kept to a location you control before touching the tenant, then reduce.
• Perpetual estate: reduce nothing, reassign everything, and review whether Software Assurance is still earning its cost.
• Antivirus: remove the retired devices from the console, then read the console’s own licence usage page to confirm the seats show as free before you set the new count at renewal.

Questions people ask about this