Office 2021 does not stop working: it stops being tested against Microsoft 365

On 13 October nothing switches off. Word will open, Excel will calculate, Outlook will keep pulling mail and nobody in your company will notice a thing. That is the problem. That day two clocks start at once, and only one of them makes any noise.

The noisy one is worth stating plainly, because it is the one that makes headlines and then hides the other. The lifecycle announcement Microsoft published on 22 April 2026 puts it like this: from that date "Microsoft will no longer provide technical support, bug fixes, or security updates for this product." A plain old end of support, with the usual risk in a program that opens files coming from outside. Everybody understands that half.

The second clock is the quiet one, and it is the one that will cost you a morning. From that day Microsoft stops checking that its own services still work with your Office. That raises no alert, shows up in no vulnerability scan and changes nothing visible. The outage, when it comes, will not come on 13 October: it will come on some random Tuesday in 2027, after somebody moved something on the other side, and it will start with the most frustrating sentence in IT support: "we haven't touched anything." Which will also be true.

Microsoft gives two different dates, and both are its own

If you look up the date, you will find two. It is not a press mistake: both are published on Microsoft Learn, on two different pages.

For day-to-day planning, use 13 October and move on. It is also the date Microsoft itself puts in the title of its own end-of-support announcement, so it is the one anyone writing to you about this will quote. The gap between the two is hours, and hours on somebody else's calendar never work in your favour: if you plan against the optimistic date and the vendor applies the other one, you are the one left exposed.

There is a second detail almost nobody checks, and it does change the conversation: what people call "Office 2021" is actually two products under two different lifecycle policies. The box bought in a shop (Home and Business, Home and Student, Professional, plus their Mac versions) runs on the Modern Lifecycle Policy. The one bought through volume licensing — Office LTSC 2021, Standard or Professional Plus — runs on the Fixed Lifecycle Policy. And the LTSC page has a single date column: end of mainstream support. There is no extended phase underneath. There is no ESU to buy, the way there is for Windows 10. It is one date and that is it.

Anyone who went through the Windows 10 toll will recognise the mechanics, even though there is no toll here: we ran the numbers in the Windows 10 ESU, the toll that doubles. There you paid for extra time. Here there is no option to pay.

The quiet clock: what expires is the compatibility guarantee

The connectivity page says it with welcome clarity, and it is worth reading twice: "Older Office versions might still be able to connect to Microsoft 365 services, but that connectivity isn't supported." Translated: it will keep connecting. Nobody is going to block you on the morning of 14 October.

The important sentence comes two lines later, and it is the one that explains the actual mechanism: older versions may start hitting performance or reliability problems "because improvements to Microsoft 365 services don't consider or test compatibility with these older Office versions." That is the whole thing. It is not that they take anything away: it is that they stop testing.

The precedent is already on paper: 2020, 2023, 2023

This is not a hypothesis. That same Microsoft page lists, between the note right below the table and the "other changes related to connectivity" section, three cuts that already happened and behaved in exactly this way:

All three have the same shape: a part you depended on moved inside somebody else's house. It is the same reasoning we applied to the six services that are really one dependency: when mail, files, identity and meetings all live on the same platform, that platform's calendar is also yours, whether you signed up for it or not.

The operating system underneath expires in the very same second

This is what we found when we cross-read the pages, and it is the part that made us look up. The lifecycle page for Windows 11 Home and Pro gives, for version 24H2, exactly this end date: 10/14/2026 6:59:59 AM. Same day. Same hour. Same second as Office 2021 and Office LTSC 2021.

And now the part that actually decides who is in a hurry and who is not. That same 24H2 version, in the Enterprise and Education editions, does not expire in 2026: it expires on 10/13/2027. One extra year. Same OS version, same machine, same number under "About Windows": the only thing that changes is the edition that shipped with the device when it was bought.

For a small company this translates into something very concrete: the laptop bought in 2024 or 2025 with Windows 11 Pro OEM and a boxed Office Home & Business 2021 on top — the pair that has walked out of every computer shop these past five years — reaches the same day from both sides, with one difference that matters and that we get to right now. In your head those are two separate purchases on two separate invoices. In Microsoft's head they are one date.

The difference, and this is an honest caveat that works in your favour: Windows 11 does have an automatic way out. The Enterprise and Education page says it outright — unless deferred, later feature updates may be installed before the listed end date — and on Home and Pro the default behaviour is the same: many machines will already have moved themselves to 25H2, which expires on 10/13/2027 for Home and Pro, or straight to 26H1, which holds until March 2028. The operating system tends to heal itself. Perpetual Office does not. Office 2021 will not jump to Office 2024 on its own, not one night and not ever: it stays put until somebody decides.

Project and Visio are the ones nobody remembers to count

That same page, in the additional-information section that follows the table, lists two more families with their own date: Project Professional 2021 and Project Standard 2021 are supported for connecting to Microsoft 365 services "until October 2026", and likewise for Visio LTSC Professional 2021 and Visio LTSC Standard 2021.

These are the licences inventories handle worst, because they were not bought for "the company": they were bought for one person, five years ago, because they needed it for a specific project. They are on nobody's asset list, they do not appear in the maintenance contract, and they live on a single laptop that, with luck, still belongs to the same person. If your company plans works, installations or rollouts with a desktop Project, that piece is on the list.

The inventory you do not have (and how to build it this week)

The reason almost nobody knows how many perpetual licences they own is structural, not sloppiness: perpetual Office was never bought in one go. It was bought machine by machine, over five years, sometimes with the laptop and sometimes separately, on invoices from different suppliers and often by whoever needed the device rather than whoever runs IT. There is no single place to look because there never was a single place to write it down.

Four questions, in this order. They can be answered in one afternoon and they hold for the next three years, not just for October:

What you do not need is to rush out and buy anything. The date is not an outage: it is the point from which the clock starts running against you without telling you. With the list in hand, the decision can be made calmly in November; without it, it gets made in March, with somebody angry on the phone.

What we are not going to tell you

We are not going to tell you to buy Office LTSC 2024. According to that same connectivity table, it is supported for connecting to Microsoft 365 until 9 October 2029: buying it moves the problem three years down the road and drops you back into this exact conversation with a different manager and a different budget. Sometimes that is the right call. It is never the automatic call.

And we are not going to tell you that subscription is the answer to everything either. If you have a machine that never touches the internet, a lab box, a PC driving an installation, or an Access database written fifteen years ago that nobody is going to rewrite, a perpetual licence is still the right call and we will defend it in front of whoever needs convincing. What is not defensible is keeping it out of inertia, without knowing how many there are or where. We are not resellers of any particular platform: if the inventory says you are carrying spare software, we will tell you so anyway.

It is the same lens we use on the servers somebody left running after a migration: the dangerous part is rarely the one causing trouble, but the one that has caused none for years and has therefore dropped off the map.

Two clocks, and only one makes noise

You will hear the patching clock: the vendor, the auditor and probably your own cyber policy will all remind you. The other one never rings. From 13 October, every improvement Microsoft ships to its services will be made without considering or testing compatibility with what you have installed — their documentation uses those words — and the day it shows, nothing will have changed on your side. Neither of these is an outage. Both are fixed the same way: with a list of machines that does not exist today and takes one afternoon to build.

Sources (verified on 2026-09-25 against primary Microsoft documentation): end of support and the quote on technical support, bug fixes and security updates — announcement "Office LTSC 2021 reaching end of support on October 13, 2026" (published 2026-04-22); connectivity dates, literal quotes and the notes on Office 2016/2019, TLS 1.2, basic authentication, Project and Visio — Microsoft Learn, "Office versions and connectivity to Microsoft 365 services" (page updated 2026-03-19); lifecycle and Fixed policy for Office LTSC 2021 and Modern policy for Office 2021; per-version dates for Windows 11 Home and Pro and Windows 11 Enterprise and Education. Every lifecycle date Microsoft publishes is in Pacific Time, as the pages themselves state.