Microsoft Access in the Cloud: More Than Just File Storage
Microsoft Access has evolved far beyond its roots as a desktop database application. With cloud integration through SharePoint, Dataverse, and Azure SQL, Access databases can now serve as the front-end for cloud-hosted data, enabling organizations to modernize their legacy Access applications while preserving the familiar interface that business users depend on. This guide explores how Access fits into the modern cloud ecosystem and the strategic pathways for migrating Access workloads to scalable, secure platforms.
The Current State of Microsoft Access
Microsoft Access remains one of the most widely used database tools in enterprise environments, often operating as "shadow IT" -- critical business applications built by power users outside of IT governance. Despite the rise of cloud-native database solutions, millions of Access databases power business processes across departments like finance, operations, HR, and compliance. The challenge for enterprises is not whether to keep Access, but how to modernize these workloads for the cloud era.
Microsoft continues to include Access in Microsoft 365 Apps for Enterprise and Microsoft 365 Business plans. While Microsoft has deprecated Access web apps on SharePoint Online, the desktop application remains fully supported with regular updates, including modern UI improvements and connectivity enhancements.
Access in the Cloud: Architecture Options
There are several approaches to running Access workloads in the cloud, each with distinct tradeoffs:
- Access front-end with SharePoint lists backend -- Access can link to SharePoint Online lists as a data source, enabling multiple users to work with shared data through a familiar Access interface. This approach requires no Azure infrastructure but is limited to SharePoint list capacity (approximately 30 million items per list with indexed views limited to 5,000 items per view).
- Access front-end with Azure SQL Database backend -- For larger datasets and more demanding workloads, Access can connect to Azure SQL Database via ODBC. This provides enterprise-grade scalability, backup, and security while preserving the Access front-end that business users know.
- Access front-end with Dataverse backend -- Microsoft Dataverse (the data platform behind Power Platform) provides a structured, governed data layer that Access can connect to. This approach positions Access data for future Power Apps and Power BI integration.
- Full migration to Power Apps -- The most forward-looking approach replaces the Access front-end entirely with a Power Apps canvas or model-driven app, backed by Dataverse or Azure SQL. This eliminates the desktop dependency and provides web and mobile access.
- Migration to Azure SQL with custom web app -- For complex Access applications, migrating the database to Azure SQL and rebuilding the front-end as a modern web application (using Power Apps, React, or ASP.NET) provides the greatest scalability and flexibility.
Why Legacy Access Databases Are a Risk
While Access is a capable tool, legacy Access databases present several enterprise risks that drive modernization initiatives:
- Single points of failure -- Many critical Access databases are maintained by a single power user. If that person leaves the organization, the institutional knowledge of the database's design and business logic goes with them.
- Scalability limitations -- Access databases have a 2GB file size limit and degrade in performance with more than 10-15 concurrent users. As business data grows, these limitations become acute.
- Security and compliance gaps -- Access databases stored on file shares often lack encryption at rest, audit logging, row-level security, and the access controls required by HIPAA, SOC 2, and GDPR. Moving to Azure SQL or Dataverse addresses these gaps.
- No mobile or web access -- Desktop Access applications cannot be accessed from mobile devices or web browsers, limiting remote work capabilities.
- Backup and disaster recovery -- Access .accdb files on file shares typically depend on basic file backup schedules. Cloud backends like Azure SQL provide automatic backups, point-in-time restore, and geo-redundancy.
Migration Strategy: Moving Access to the Cloud
A structured migration approach minimizes disruption and preserves business continuity:
- Step 1: Inventory and assess -- Identify all Access databases in your organization (they are often scattered across file shares, OneDrive, and local drives). Document each database's purpose, owner, user count, data volume, and business criticality.
- Step 2: Categorize and prioritize -- Group databases into tiers: critical business applications (migrate to Azure SQL or Dataverse), departmental tools (migrate to SharePoint lists or Power Apps), and obsolete databases (archive or retire).
- Step 3: Split front-end and back-end -- If not already done, split each Access database into a front-end (forms, reports, queries) and back-end (tables). This is a prerequisite for cloud migration.
- Step 4: Migrate data to cloud backend -- Use the SQL Server Migration Assistant (SSMA) for Access to migrate tables and data to Azure SQL Database. For Dataverse migrations, use the Data Migration Framework or Power Platform data flows.
- Step 5: Relink and test -- Update the Access front-end to connect to the new cloud backend via ODBC (for Azure SQL) or linked tables (for SharePoint). Test all forms, reports, queries, and VBA code for compatibility.
- Step 6: Plan front-end modernization -- Once the data is in the cloud, plan a phased front-end modernization using Power Apps, Power BI, or custom web applications. This can happen over months or years based on business priority.
How EPC Group Can Help
With 28+ years of enterprise Microsoft consulting experience, EPC Group has migrated hundreds of Access databases to modern cloud platforms. Our services include:
- Access database discovery and assessment -- We scan your environment to identify all Access databases, assess their complexity, and recommend the optimal migration target (SharePoint, Azure SQL, Dataverse, or Power Apps).
- Azure SQL migration -- We handle the full migration lifecycle from schema conversion to data transfer, ODBC configuration, performance optimization, and security hardening.
- Power Apps modernization -- We rebuild Access front-ends as modern Power Apps with web and mobile access, backed by Dataverse or Azure SQL for enterprise scalability.
- Compliance enablement -- We ensure your migrated databases meet HIPAA, SOC 2, GDPR, and industry-specific compliance requirements with proper encryption, access controls, and audit trails.
- Training and knowledge transfer -- We document migrated applications and train both IT staff and business users on the new platform, eliminating single-point-of-failure risks.
Modernize Your Access Databases
Have legacy Access databases that need to move to the cloud? Our migration specialists can assess your environment and execute a seamless transition to Azure SQL, Dataverse, or Power Apps.
Frequently Asked Questions
Is Microsoft discontinuing Access?
No. Microsoft has confirmed that Access remains part of the Microsoft 365 Apps suite and continues to receive updates. However, Microsoft deprecated Access web apps on SharePoint Online and is clearly investing more heavily in Power Apps and Dataverse as the future direction for low-code business applications. The strategic recommendation is to continue using Access where it works but plan migration paths for critical databases to avoid future disruption.
Can Access connect to Azure SQL Database directly?
Yes. Access can connect to Azure SQL Database via ODBC linked tables. You create an ODBC connection string pointing to your Azure SQL server, and Access tables are linked to the cloud database. Forms, reports, queries, and VBA code in the Access front-end work against the cloud data transparently. This is often the fastest path to cloud migration because it preserves the existing Access interface while moving data to a scalable, secure backend.
How many users can Access support?
Desktop Access databases with a file-share backend typically start degrading in performance with more than 10-15 concurrent users. With an Azure SQL or SQL Server backend, the user limit is determined by the backend infrastructure rather than Access itself, effectively removing the concurrency bottleneck. For applications needing more than 25-50 concurrent users, we recommend migrating the front-end to Power Apps or a web application for the best user experience.
Should we migrate to Power Apps or Azure SQL?
It depends on your priorities. If you want to quickly move data to the cloud while keeping the existing Access front-end, migrate to Azure SQL with ODBC linked tables. If you want to eliminate the desktop dependency and provide web and mobile access, migrate to Dataverse with a Power Apps front-end. For complex applications with heavy VBA code, Azure SQL with a phased front-end modernization is usually the most practical approach. EPC Group typically recommends a two-phase strategy: migrate data to Azure SQL first (quick win), then modernize the front-end to Power Apps or a web app over time.
What about VBA code in our Access databases?
VBA code in Access front-ends continues to function when the backend is migrated to Azure SQL or SharePoint. However, VBA code does not translate directly to Power Apps or web applications. For databases with complex VBA business logic, the options are: (1) keep the Access front-end connected to a cloud backend, (2) rewrite the logic in Power Fx (Power Apps), (3) move business logic to Azure Functions or stored procedures in Azure SQL, or (4) rebuild as a custom web application. EPC Group assesses VBA complexity during our discovery phase to recommend the most efficient approach.