Office 2021 reached end of support on October 13, 2026. Copilot was never coming to it.

Why can't Microsoft 365 Copilot run on Office 2021?

Because Microsoft draws the eligibility line around the Microsoft 365 subscription rather than around the Office version. Microsoft states that Copilot is supported only on the cloud-backed apps included in Microsoft 365 suites, and that on-premises versions of Office are not eligible. That statement was true before October 13 and it stays true now.

The end of support date was the news. The eligibility rule is the decision, and it is the reason this page leads with it.

The word doing the work there is "eligible." It describes a boundary, and a perpetual install sits outside it. Copilot does not wait on a newer build of Office 2021 or on a future update. What it needs is the subscription relationship itself, and that is the one thing a perpetual license is built to avoid.

Microsoft's admin requirements say the same thing from the other side. They state that users need a Copilot license and a qualifying prerequisite license, and they tell administrators to deploy Microsoft 365 Apps to the users who need Copilot in the desktop apps. They also rule out one nearby case by name: Copilot is unavailable with device-based licensing for Microsoft 365 Apps for enterprise. The line follows the licensed user and the subscription apps, which is exactly what an Office LTSC install lacks.

One naming note, so the sources line up when you check them. Microsoft's requirements page now calls the product Microsoft Copilot, formerly Microsoft 365 Copilot. The Partner Center statements quoted on this page use the earlier name.

What the December 1 purchasing change moves

Microsoft has announced that from December 1, 2026, new Microsoft 365 Copilot and Microsoft 365 Copilot Business offers can be purchased without a qualifying Microsoft 365 base subscription. Microsoft frames it in one line: "This purchasing change affects how customers purchase Copilot, not the underlying Copilot capabilities." The same announcement adds that "Copilot experiences continue to depend on the Microsoft 365 apps and services a customer is licensed for." The Copilot experience in desktop Word, Excel and PowerPoint comes from Microsoft 365 Apps, so the September statement about on-premises Office stays where it was.

Why this reframes the decision

An end-of-support date, on its own, reads as a cost to absorb, which is why it gets deferred one cycle at a time, and how an estate ends up on a 2021 product after the date has passed.

The eligibility rule changes the arithmetic. The choice in front of the institution is between Microsoft 365 Apps, where Copilot in Word, Excel and PowerPoint can be licensed, and a perpetual install where it structurally cannot. For as long as a desk stays perpetual, the loan officer, processor or analyst at it sits outside Copilot in the desktop apps, and spending more on the current license leaves them there. Eligibility is the first step; the data access and permissions work described in the related reading below comes before any rollout.

What ended on October 13, 2026?

Support ended. The software keeps running. Getting that distinction right in both directions saves money: panic buys what was not needed, and complacency leaves an unpatched estate in place.

Microsoft's announcement named three products and one date. Support for Office Long Term Servicing Channel 2021, Project LTSC 2021 and Visio LTSC 2021 ended on October 13, 2026, and from that date these products receive no updates, security fixes or technical support.

That sentence settles a question planning before the date could only hedge. Windows and Windows Server have paid Extended Security Updates programs. Office 2021 has none, and Microsoft has now said so in writing. The same page puts it plainly for these installs: "You'll no longer receive Office 2021 software updates."

The apps still open, and that is the risk

Word opens, the file saves, the spreadsheet calculates. What changed is that Microsoft provides no security fix for the next vulnerability found in any of these products, and no technical support the next time something breaks.

Microsoft states the consequence in its lifecycle announcement: running the product past the date "may increase your organization's exposure to security risks and could impact compliance requirements." For a bank, a credit union or a mortgage company, the second clause carries the weight. An examiner can write a finding about software that still works perfectly well.

The line about regulated environments describes you

The September announcement contains a line that reads like throat-clearing and carries real information. Microsoft writes that these products "have served organizations for many years, particularly in specialized or regulated environments."

That is the profile. Perpetual Office survives longest where a cloud move was deferred for a defensible reason: an examination cycle that was never a good time, an air-gapped branch, a core system integration that needed a specific Office build, a policy written before the institution had a cloud position. Those reasons were often correct when they were made. The date arrived anyway.

Which editions this covers

Microsoft's lifecycle records list Office LTSC 2021 in Standard and Standard for Mac editions, and Visio LTSC 2021 in Professional and Standard. All of them follow the Fixed Lifecycle Policy, which produces a single published end date with no rolling extension behind it. Microsoft's upgrade guidance applies the same October 13, 2026 date to volume licensed versions of Office LTSC 2021, so every volume-licensed Office LTSC 2021 install, whatever its edition, is on the same date.

Consumer Office 2021 shares the same October 13, 2026 date. If your institution ever reimbursed a remote employee for an Office Home & Business 2021 license, that copy is on the same clock as the volume-licensed ones, and it is usually the copy nobody has a record of.

Can Office 2021 still connect to Exchange Online, SharePoint and OneDrive?

It may well connect today. Microsoft's support for that connection ended on October 13, 2026, and that matters most to the institutions that moved mail to the cloud and kept perpetual Office on the desktop.

This is the fact most coverage of the date skipped. Microsoft publishes a separate table of Office versions it supports for connecting to Microsoft 365 services, and Office LTSC 2021 dropped off it on the same day it left support.

Read that precisely. Microsoft describes a supported configuration, and it does not say the connection is switched off. Its own explanation of the risk is gradual: older versions "might not be able to use all the latest functionality and features of Microsoft 365 services," and "over time, these older versions might encounter other unexpected performance or reliability issues," because service improvements are not tested against them.

Microsoft's configuration matrix states the rule behind the table: Office apps connecting to Microsoft 365 services "must be in mainstream support to be considered a supported connection." Office 2019 and Office 2016 lost that status in October 2023, two years before they left support. Office LTSC 2021 lost both on the same day.

Why this lands hardest on a hybrid estate

A common shape at community institutions is cloud mail with perpetual desktops: mailboxes moved to Exchange Online, files moving to SharePoint and OneDrive, and the Office apps left on a volume license because they still worked. That shape was a supported configuration until October 13. It is now two supported services joined by an unsupported client, and the client is the part that opens every external attachment.

That is the strongest reason to put the mail-handling desks at the front of the queue. They combine the two exposures on this page: an Office build that receives no more security fixes, and a connection to Microsoft 365 that Microsoft no longer tests against.

What happened to sensitivity labels on perpetual Office?

The add-in that provided them is retired, and the built-in replacement requires a subscription edition of Office. Both halves of that sentence come from Microsoft, and together they describe a control with no supported client left on a perpetual desktop.

The September 15 announcement mentions it in a single clause, immediately after the Copilot sentence: "the Azure Information Protection (AIP) labeling client for perpetual Office has been retired."

Microsoft's documentation for that client confirms the retirement and names the successor. The AIP unified labeling client is replaced with the Microsoft Purview Information Protection client, and the Office add-in for labeling in Word, Excel, PowerPoint and Outlook is retired.

So far this reads like an ordinary product succession. The second half is where it changes.

Put the two statements next to each other. The add-in that let perpetual Office apply sensitivity labels is retired. The built-in labeling that replaced it requires a subscription edition. An institution running standalone Office therefore has no supported client-side path to sensitivity labeling in Word, Excel, PowerPoint or Outlook. October 13 did not create that gap, and the end of support makes it harder to defer.

What this means for a documented classification control

A written information security program can name data classification as a control. The policy document can be current, approved and produced on request. The label taxonomy can exist in the Purview portal and look perfectly healthy there.

A person working in Word or Excel on a perpetual install still needs a supported client to apply a label to the loan file in front of them. The policy exists and the taxonomy exists; on that desktop the supported client is missing. The portal hides the gap, because it shows the labels you published rather than the endpoints that can consume them.

Keep the size of the gap exact. What Microsoft rules out is sensitivity labeling in the Office apps on a standalone edition. Other routes to a label are untouched: service-side automatic labeling in Microsoft Purview still evaluates content at rest, and a user signed in to Office on the web is working in a cloud-backed app. What goes missing is the labeling your people do themselves, at the moment they create or handle the document.

That is usually the part of the control the policy describes. Microsoft's word is "supported," and an unsupported path is one an institution cannot rely on or expect Microsoft to stand behind if it changes, whatever a given machine does today. The practical question is which routes to a label your environment supports, and whether the people relying on the control know which those are.

Which upgrade path is actually yours?

Microsoft published named recommendations for each kind of customer. They split on organization size first, and then on whether a cloud move is possible. The middle column is Microsoft's own routing; the right-hand column is ABT's read of what each path means for a regulated institution.

What if regulation requires on-premises Office?

Then Office LTSC 2024 is a supported, legitimate answer, and Microsoft says so plainly. It is worth being equally plain about what that choice carries forward.

Microsoft treats the on-premises path as a recognized route. Its announcement says that where regulatory, connectivity or technological constraints prevent the use of cloud solutions, customers might consider the latest supported on-premises alternatives, naming Office LTSC 2024, Project LTSC 2024 and Visio LTSC 2024. The lifecycle announcement repeats it: for organizations not yet ready to move to the cloud, the recommended path is the most recent supported on-premises version for commercial customers, Office LTSC 2024.

Microsoft's upgrade guidance describes who that product is for: Office LTSC 2024 "is designed for specific scenarios. These include regulated devices that can't accept feature updates, process control devices on manufacturing floors, and specialty systems that can't connect to the internet." Its lifecycle record shows availability from September 2024 under the same Fixed Lifecycle Policy, in Embedded, Professional Plus and Standard editions, and Microsoft's connectivity table supports it for connecting to Microsoft 365 services until October 9, 2029. That is a real runway.

What moving to the 2024 generation leaves in place

Both of the limits described earlier on this page are properties of perpetual licensing rather than of the 2021 vintage, so they travel with you.

• Microsoft 365 Copilot stays out of reach. Microsoft's eligibility statement covers on-premises versions of Office generally, and a 2024 perpetual install is still an on-premises version.
• Sensitivity labels in the apps stay unsupported. Microsoft's wording is "standalone editions of Office, sometimes called Office Perpetual." Office LTSC 2024 is a standalone edition.
• The same conversation returns in 2029. A Fixed Lifecycle Policy product has a published end date from the day it ships. Choosing the 2024 generation sets the next deadline and keeps the category of deadline.

An institution with an air-gap requirement, a specific integration dependency, or a connectivity constraint at a branch is making a defensible engineering decision, and Microsoft supports it. The recommendation worth making is narrower: decide it deliberately, for the part of the estate that has the constraint, and keep the rest of the organization off the last renewal's default.

What should happen now, in order?

Six steps. The first two are discovery and need no purchase. The order matters, because each one narrows the decision the next one has to make.

A free licensing assessment for the Office 2021 installs still in service

Where the facts on this page come from

Every date, quotation and Microsoft recommendation on this page comes from the Microsoft sources below, re-checked on October 15, 2026, after the end of support date. The prioritization, the six steps and the assessment are ABT's advice.

Related reading

What the estate on the other side of this decision can do

The capability in this short is the one the Copilot eligibility rule puts out of reach for a perpetual install. Sixty seconds on what it looks like in practice.

Office LTSC 2021 after end of support, answered from Microsoft's documentation