Microsoft's support policy for Access depends entirely on which version and licensing model you're using — a perpetual (one-time purchase) license or a Microsoft 365 subscription follow completely different rules. Here's the complete picture.
On this page
Full Version-by-Version Support Table
| Version | Support Status | Policy Type |
|---|---|---|
| Access 2010 and earlier | Support ended years ago | Fixed |
| Access 2013 | Support ended (mainstream and extended support both expired) | Fixed |
| Access 2016 | Support ended October 2025 | Fixed |
| Access 2019 | Support ended October 2025 | Fixed |
| Access 2021 / Office 2021 (perpetual license) | Support ends October 13, 2026 | Modern |
| Access LTSC 2024 | Supported through October 2029 | Fixed |
| Access in Microsoft 365 | Continuously updated while your subscription is active | Modern (subscription) |
Modern Policy vs. Fixed Policy: Why This Matters
Microsoft governs its products under one of two lifecycle policies, and which one applies changes how much warning you get:
- Fixed Policy — used for older perpetual-license products, typically offering a longer, predictable support window with distinct "mainstream" and "extended" support phases.
- Modern Policy — used for newer products and most subscription services, generally offering shorter, simpler support windows tied to a single end date rather than phased support tiers.
The shift toward the Modern Policy for recent one-time-purchase Office versions (like Office/Access 2021) is part of why support windows have been getting shorter — five years from release rather than the decade-plus older perpetual versions sometimes received.
What "End of Support" Actually Means
When Microsoft's support window closes for a version, the software doesn't stop working — but it does stop receiving:
- Security patches for newly discovered vulnerabilities
- Bug fixes and non-security updates
- Official technical support from Microsoft, free or paid
- Compatibility updates as Windows and other Microsoft products evolve around it
In practice, this means an unsupported Access database becomes a slowly growing security liability. It won't break on the day support ends, but every month afterward increases the chance an unpatched vulnerability gets exploited, especially if the database is exposed to shared networks or the internet in any way.
Why the Microsoft 365 Version Is Different
Access included with a Microsoft 365 subscription doesn't follow a fixed end-of-life date the way perpetual versions do. As long as your subscription stays active, you continue receiving updates — mostly maintenance, compatibility, and occasional minor feature additions rather than major new functionality, since Microsoft's active feature development attention has shifted toward Power Platform.
This is the main reason many organizations choose to move to a Microsoft 365 subscription model for Access specifically to avoid the recurring "which version am I on and when does it expire" question — though it doesn't solve Access's underlying architectural limitations around multi-user access and scale.
How to Check Which Version You're Running
- Open Access and go to File → Account (or Help, in older versions).
- Look for the product information panel, which shows your version number and whether it's a Microsoft 365 subscription or a perpetual (one-time purchase) license.
- Cross-reference against the table above to see your actual support runway.
- If you're unsure or the information is ambiguous, Microsoft's official product lifecycle search tool is the authoritative source — always verify there, since support dates can be updated.
Once you know your actual runway, the next question is what to do with that information — see our breakdown of signs it's time to leave Access or jump straight to how a migration actually works.
Not sure what your support timeline means for your business?
Get a free, plain-English assessment of your risk level and options.
Book a Free Assessment →Support dates reflect Microsoft's published lifecycle policies as of 2026 and are subject to change. Always verify current status through Microsoft's official product lifecycle documentation before making planning decisions.