Microsoft now says any business still running Exchange Server 2016 or 2019 should treat it as "permanently vulnerable". The final security updates came out in October, and November's fixes, including one for a critical flaw, were released for the newer Subscription Edition only. If your email still runs on one of these servers, the question is no longer whether to move, but how quickly, and what happens to the old machines afterwards.
This piece sets out what Microsoft has said, why this week's Microsoft 365 outage is part of the decision, and the step most migrations get wrong: getting rid of the old server and the email it still holds.
What Microsoft has said
Exchange Server 2016 and 2019 went out of support in October 2025. Microsoft then sold paid Extended Security Updates for organisations that needed more time, first to April 2026 and then, in a second paid period it said would not be extended, to the end of October 2026. On 13 October it confirmed it had released the final updates under that programme, and said it would stop testing the two versions for vulnerabilities.
Its November security update notice, published on 10 November, covers Exchange Server Subscription Edition (SE) only. It says Exchange 2016 and 2019 "are no longer tested for vulnerabilities and there are no updates released", that anyone using them "should consider them permanently vulnerable", and that they should upgrade immediately. According to The Register, the November update fixed nine vulnerabilities in Exchange SE, including a critical remote code execution flaw. Microsoft is not testing whether the older versions share them.
In our reading, that is the important change. Until now, an unsupported Exchange server at least appeared in Microsoft's security notices. From here on, a new flaw that affects it may never be mentioned at all.
Where this week's outage fits
The two ways forward are Exchange SE, which still runs on your own servers, or Exchange Online in its cloud. This week showed the trade-off with the cloud option. From around 18:00 UTC on 12 November, a Microsoft outage took down Exchange Online, Teams and other services, and administrators also lost access to management tools such as Intune, The Register reported. By the next morning the BBC was reporting effects on GPs, police forces, pharmacies and schools across the UK, with Microsoft saying services were gradually being restored. Microsoft and security experts ruled out a cyber attack, the BBC said.
None of that makes an unpatched server the safer choice. It does mean the decision between Exchange SE and Exchange Online deserves a real conversation about what your business does when email stops, rather than a default. Either way, the old servers have to go.
The part most migrations get wrong
An Exchange server is not just software. Its disks hold mailbox databases, which contain the email of everyone in the organisation, often going back years, along with names, contact details, contracts and personal data of customers and staff.
Removing Exchange does not necessarily remove that data. Microsoft's own documentation for removing a mailbox database says the command removes only the database's entry in the directory and "doesn't remove the physical database files", which have to be removed separately. Even then, deleting files is not the same as making them unrecoverable.
The email also rarely lives in one place. A retired Exchange setup can leave copies on:
- every server that held a copy of the databases, not just the main one
- backup disks, tapes and cloud backup sets taken over the years
- storage arrays and virtual machine disk files, if the servers were virtual
- old drives swapped out during the server's working life and never disposed of
Before anything is wiped, check that the new system really holds everything you need, including mail under legal hold or retention rules. Then account for every copy of the old data, and make sure each drive that held it is wiped to a recognised standard or destroyed, with a certificate that lists it by serial number.
What to do this month
- Confirm what you are running. If anyone in the business is unsure whether an Exchange 2016 or 2019 server is still switched on, including one kept only for administration, find out.
- Set a date to leave. Microsoft has said plainly there will be no more updates. Every week on these versions is a week without fixes.
- Decide between Exchange SE and Exchange Online with your IT provider, knowing what each means when something goes wrong.
- Plan the retirement before the migration ends. List every server, backup and drive that has held mailbox data, and decide how each will be wiped or destroyed.
- Keep the evidence. A certificate of destruction with drive serial numbers is what shows the old email was dealt with, if anyone asks.
If your Exchange servers run on Windows Server 2016, that system reaches the end of its own support in January 2027, and our article on Windows Server 2016 end of support covers it. Our guide to old backup tapes covers the backups.
For disclosure, Nanosoft provides server decommissioning and data destruction, so weigh the above accordingly. Every fact here can be checked against the sources linked in the text, as they stood on 13 November 2026.
The honest summary
Microsoft has stopped patching and testing Exchange 2016 and 2019 and says to treat them as permanently vulnerable. Moving off them is overdue. The move is not finished when the mail arrives in its new home: it is finished when every copy of the old mail on every old disk has been accounted for and destroyed.
Nanosoft Team
Writer at Nanosoft - covering ITAD, data security, and sustainable technology lifecycle management.
Found this useful? Share it.



