Microsoft Access 2021 End of Support: What Actually Happens on October 13, 2026
Microsoft Access 2021 reaches end of support on October 13, 2026. After that date the software continues to run and your databases continue to open, but Microsoft stops issuing security updates for it. Access 2016 and Access 2019 already passed the same milestone in October 2025. Access included in a Microsoft 365 subscription is unaffected, because it is updated continuously.
Before going further, I should declare an interest. I rebuild Microsoft Access databases as web applications for a living, which means one of the four options at the end of this post is the one I sell. I will be plain about where each option genuinely fits — including the two that involve no work from anyone like me.
The dates, in one table
Everything in this post hangs off a handful of dates, so here they are first, each row linked to Microsoft's own lifecycle page.
| Version | End of support | Status today |
|---|---|---|
| Access 2016 | October 14, 2025 | Unsupported |
| Access 2019 | October 14, 2025 | Unsupported |
| Access 2021 | October 13, 2026 | Supported until October 13, 2026 |
| Access 2024 | October 9, 2029 | Supported |
| Access in Microsoft 365 | No end-of-support date | Updated continuously |
Verified against Microsoft's lifecycle documentation on August 15, 2026.
One quirk worth knowing before you click any of those links: Microsoft's lifecycle pages show dates in Pacific Time and record the Access 2021 retirement moment as 6:59:59 AM on October 14, 2026. October 13 is the last full day of support, and it is the date Microsoft communicates. The same convention explains why Access 2016 and Access 2019 are listed against October 15 but ended, in every practical sense, on October 14, 2025 — and why Access 2024's listing of October 10, 2029 makes October 9 its last full day. The table above uses last-full-day dates throughout.
What actually stops on that date — and what doesn't
End of support does not mean end of function. An unsupported copy of Microsoft Access opens, runs and saves exactly as it did the day before. What changes is that newly discovered security vulnerabilities in it will not be patched — which is why unsupported Office installations are typically the first thing flagged in an IT or compliance audit.
Your database keeps opening. Nothing switches off.
There is no kill switch. Access 2021 is a perpetual licence: it is installed on your machines, it was activated once, and Microsoft has no mechanism — and no intention — of disabling it. Your .accdb files, your forms, your queries, your reports and your VBA will behave on October 14 exactly as they did on October 12. A fair share of the databases I am asked to migrate arrive from copies of Access that fell out of support years ago, and every one of them still opened.
Security updates stop. This is the whole event.
The substance of end of support is a single change: security patches stop. Any vulnerability discovered in Access 2021 after October 13, 2026 stays open on every machine running it, permanently. Whether that matters depends on honest sizing, not slogans. A single-user database on a locked-down office PC carries a modest, slow-growing risk. A copy of Access that regularly opens files from outside the business — supplier imports, emailed spreadsheets, downloads — carries a much less comfortable one, because malformed Office files are a well-worn attack route.
Microsoft support stops taking your calls about it.
Assisted support ends on the same date. No phone support, no paid escalation, no guaranteed fixes for non-security bugs. In practice this is the least consequential change: most small businesses running Access have never once rung Microsoft about it, and the documentation stays online. I mention it mainly because "end of support" is often read as something more dramatic than it is.
What this does to your next IT or compliance review
Here is where the date bites first for most organisations. Cyber-insurance questionnaires, Cyber Essentials-style certifications and customer security reviews all ask some version of "is all your software vendor-supported?" On October 13, 2026 your truthful answer changes. In my experience the forcing event for a migration is rarely an actual breach — it is an auditor, an insurer or a large customer refusing to accept "unsupported but working" as an answer.
Am I even affected? (a 30-second check)
The check takes half a minute. Open Access, then go to File → Account and read the Product Information panel on the right.
- If it says Subscription Product and mentions Microsoft 365, you are not affected by this deadline. That copy of Access updates continuously and has no end-of-support date.
- If it says Microsoft Office Professional 2021, Office LTSC 2021 or names Access 2021 outright, you hold a perpetual licence and October 13, 2026 applies to you.
- If it names 2016 or 2019, you passed the deadline in October 2025 and are already unsupported.
Most small businesses genuinely do not know which they have, and there is no shame in that. The licence was usually chosen years ago — by a supplier, an IT provider, or whoever bought the PCs — and the two products look identical in daily use. The difference only surfaces at moments like this one.
If you already know you are moving off Access, the free 24-hour Migration Blueprint maps your database and gives you a fixed number before you commit.
No, Microsoft is not discontinuing Access
Microsoft has not announced the discontinuation of Microsoft Access. It has, however, retired Access-based web publishing before: Access Web Apps and Access Services were withdrawn from Microsoft 365, leaving customers to migrate their applications elsewhere.
Let me state the first half plainly, because plenty of marketing copy implies otherwise: Access is still shipping. The Microsoft 365 version is actively updated, and Access 2024 exists and is supported into October 2029. Anyone telling you Access is dead is usually selling the thing they would like you to replace it with.
The second half is the honest caveat. Microsoft retires Access surfaces — ways of using it — even while Access itself continues, and the Web Apps withdrawal stranded real businesses mid-workflow. Betting a critical process on any vendor's roadmap deserves at least a plan B. I answer this question, and the others I hear most often, in the FAQ on my homepage.
Your four options, honestly
Option 1 — Do nothing (and what that actually risks)
Doing nothing is a legitimate option, and I would rather say so than pretend otherwise. A single-user database that never touches outside files, on a machine that is otherwise patched, will very likely run unsupported for years without incident. What you are accepting is a risk that compounds quietly: unpatched vulnerabilities accumulate, the audit answer stays "no", and the eventual migration gets harder as the database grows and the person who built it drifts further from the payroll. The risk of doing nothing is not that the database stops working. It is that the liability becomes formally, documentably yours.
Option 2 — Move to Microsoft 365 Apps
Switching to a Microsoft 365 subscription puts you back on supported, continuously updated Access. That is the entire benefit, and for some teams it is enough. The cost is a per-user subscription that never ends, replacing the licence you bought once. Be clear about what it does not fix: the 2GB file limit (Microsoft's own specification) still applies, multi-user contention over a shared drive is unchanged, and remote access is as awkward as ever. It suits teams already paying for Microsoft 365 whose database is comfortably inside those limits.
Option 3 — Upsize the back end to SQL Server
Moving your tables into SQL Server while keeping the Access front end fixes the data problems: file size, concurrency, proper backups. It is well-trodden and considerably cheaper than a rebuild. The trade-off is that everything user-facing stays exactly where it was — a desktop-only front end, VBA, and a supported copy of Access still required on every machine, so in practice this option is paired with Option 2 and both costs apply. It suits a business whose forms and reports are genuinely sound but whose data has outgrown a single file.
Option 4 — Rebuild as a web application
A web application rebuild replaces the Access application entirely: forms, VBA logic, queries and reports become a browser-based application that needs no Office licence on any machine, has no 2GB ceiling, handles simultaneous users properly and works wherever your people are. This is the option I sell, so weigh my words accordingly. It is the most expensive option up front and the only one that is a real project — weeks, not an afternoon — and a careless rebuild can lose the workflow subtleties that made the original useful, which is why discovery matters more than code. Two things take most of the sting out. Your team keeps working in Access for the whole build, with cutover on a date you choose. And at handover you own the full source code, so you are not trading Microsoft's roadmap for a new vendor's. The way I de-risk the rest — discovery first, then a fixed quote, then the build — is described under how it works. It suits databases that are business-critical, multi-user, needed remotely, or orphaned by a departed developer.
| Option | What it fixes | What it costs | Who it suits |
|---|---|---|---|
| Do nothing | Nothing — the risk is accepted, not removed | Nothing today; growing security and audit exposure | Single-user, low-stakes, offline databases |
| Microsoft 365 Apps | Security updates only | A per-user subscription, indefinitely | Teams staying on desktop Access within its limits |
| SQL Server back end | File size, concurrency, backups | Server or Azure costs plus migration work; usually paired with Option 2 | A sound front end whose data outgrew one file |
| Web application rebuild | Updates, size limit, multi-user, remote access | The largest up-front cost; a genuine project | Business-critical, multi-user or remote databases |
If you are going to move, the deadline is not October — it is now
A real migration does not happen on a deadline day. It has a discovery phase, where somebody maps what the database actually does — including the parts only one employee knows about. It has a build phase. And it has a cutover, on a quiet date the business chooses, with the old system held in reserve. Work backwards from October 13 and the arithmetic is sobering: a cutover in early October means testing in September, which means building through late August and September, which means discovery starts more or less now. None of this is urgent because Access switches off in October — it does not. It is urgent because every week of delay narrows your choice of cutover dates and lengthens the gap you will spend unsupported.
Where to start
Start with the 30-second version check above, because if File → Account says Microsoft 365 you can close this tab with a clear conscience. If it says 2021 — or 2016, or 2019 — decide which of the four options fits, on the honest trade-offs, not the deadline panic. And if the answer is a rebuild, or you want a priced comparison before choosing, send me a short description of your database. The Migration Blueprint below comes back within 24 hours with the scope, the timeline and an exact fixed quote — free, and without a call.