This question comes up constantly. Someone in management heard that Access is being discontinued. Or an IT consultant mentioned that Access is “going away.” Or someone read a headline about Microsoft 365 changes and jumped to conclusions.
Here is what is actually true, what is not, and what it means for your planning.
Access Is Still Part of Microsoft 365
As of 2026, Microsoft Access is still included in Microsoft 365 plans that include desktop applications (Microsoft 365 Apps for Business, Microsoft 365 Apps for Enterprise, etc.). You can still install it, use it, and create new databases.
Microsoft has not announced an end-of-life date for Access.
But Microsoft Is Not Investing in It
This is the more important point. While Access has not been killed, it is clearly in maintenance mode. Compare the pace of updates to Access versus Excel, Power BI, or any of the Power Platform tools, and the contrast is obvious.
Access has not received significant new features in years. The updates it does receive are bug fixes and security patches — not new capabilities. Meanwhile, Microsoft is pouring resources into Power Apps, Power Automate, Dataverse, and the broader Power Platform as the intended replacements for the scenarios Access traditionally served.
This matters because:
- New features and integrations will not come to Access. Cloud connectivity, modern authentication, mobile support, AI features — these are going to Power Platform, not Access.
- Third-party tool support will decline. As fewer people use Access, fewer developers build tools, connectors, and drivers for it. Some ODBC drivers and reporting tools have already deprioritized Access compatibility.
- Finding Access expertise will get harder. New developers are not learning Access. The pool of people who can build and maintain Access applications is shrinking every year through retirement and career changes.
The Runtime Is Going Away
One concrete change: Microsoft stopped including the free Access Runtime in Microsoft 365 starting with certain subscription plans. The runtime allowed users without a full Access license to use Access applications. Without it, every user who interacts with your Access application needs a full Microsoft 365 license that includes Access.
This may not affect you if all your users already have Microsoft 365. But if you distribute Access applications to external users or departments that do not have Access licenses, this is a real constraint.
The .mdb Format Is Deprecated
Microsoft has long recommended migrating from the older
.mdb format to .accdb. While .mdb
files still open in current versions of Access, they use the older Jet
database engine rather than the newer ACE engine. Microsoft has not
actively maintained the Jet engine in years.
If you are still using .mdb files, you are running on an
engine that is effectively unsupported. Converting to
.accdb is straightforward and should be done regardless of
any other migration plans.
What “Supported” Actually Means
When Microsoft says Access is “supported,” they mean:
- Security patches. If a vulnerability is found, Microsoft will release a fix.
- Compatibility updates. If a Windows update breaks Access, Microsoft will fix it.
- Technical support. If you have a Microsoft support contract, you can open tickets about Access.
What “supported” does not mean:
- New features. Do not expect significant new functionality.
- Strategic direction. Microsoft’s strategic investment is in Power Platform, not Access.
- Indefinite availability. Support can end at any time with appropriate notice, and Microsoft has been giving signals about direction for years.
What Microsoft Recommends
Microsoft’s official guidance for organizations looking to modernize Access applications points to the Power Platform:
- Power Apps for replacing Access forms
- Dataverse for replacing Access data storage
- Power Automate for replacing Access macros and automation
- Power BI for replacing Access reports
This is Microsoft’s recommended path, and they have migration tools and documentation to support it. However, Power Platform has its own licensing costs, learning curve, and limitations. It is not a drop-in replacement for Access, and many organizations find the transition more complex and expensive than expected.
The Practical Timeline
Nobody outside Microsoft knows when Access will be discontinued. Based on Microsoft’s typical patterns with legacy products, a reasonable estimate is:
- Near term (1-3 years): Access continues as-is. Security patches and compatibility updates. No new features. Gradual reduction in ecosystem support.
- Medium term (3-7 years): Possible announcement of end-of-support date. Reduced inclusion in Microsoft 365 plans. Stronger push toward Power Platform migration.
- Long term (7+ years): Potential end of support, though the application itself would continue to run on existing installations.
These are educated guesses, not official Microsoft statements. The actual timeline could be shorter or longer.
What You Should Do
If Your Access Database Is Working Fine
Do not panic. There is no immediate emergency. But start planning:
- Document your Access applications. Know what you have, what it does, who uses it, and what data it contains. You cannot plan a migration if you do not know what you are migrating.
- Evaluate your options. The replacement does not have to be Power Platform. SQL Server, MySQL, PostgreSQL, Python desktop applications, and web applications are all viable paths depending on your situation.
- Budget for migration. Migration takes time and money. Starting the conversation now means you will have budget when you need it.
If Your Access Database Is Already Causing Problems
The support question is secondary. If you are dealing with corruption, multi-user conflicts, performance issues, or security concerns, you already have a reason to migrate that has nothing to do with Microsoft’s product plans.
The question is not “will Microsoft keep supporting Access?” The question is “is Access still the right tool for what we need it to do?” For many organizations, the answer has been “no” for years, regardless of Microsoft’s support policy.
If You Are Starting a New Project
Do not build it in Access. This is the one recommendation that is unambiguous. Whatever Microsoft’s support timeline turns out to be, starting a new project in a tool with no strategic future is a poor investment. Choose a platform with active development, modern capabilities, and a clear roadmap.
The Bottom Line
Access is supported today. It will not be supported forever. Microsoft is clearly signaling that the future lies elsewhere. The smartest approach is to plan your migration on your own timeline rather than waiting for Microsoft to force it. A planned migration is always cheaper, less disruptive, and more successful than an emergency one.