First decide what users need to access
Identify who needs to work remotely, from which devices and on which tasks. An office team using all existing forms has a different requirement from a customer submitting one request. Include printers, scanners, file paths and integrations that the desktop workflow relies on.
The useful question is whether the data, desktop session or user interface needs to change. Those choices should not be combined into one unexplained promise to “put Access online”.
Keep Access and use a cloud database backend
Microsoft documents Access with linked SQL Server tables, while its migration tooling supports SQL Server and Azure SQL. This can change where data is managed while retaining a desktop interface.
Review connection requirements, performance on representative tasks, authentication and the reports or queries affected. A backend move does not itself give a customer a browser screen or remove desktop deployment work.
Host the Windows experience rather than rewrite it
Services such as Azure Virtual Desktop provide hosted Windows desktops and applications. Whether a particular Access deployment fits depends on compatibility, licensing, provider configuration, profiles, storage and connected devices.
This is still a desktop-application approach. Test ordinary tasks, printing or exports, concurrent work and access removal in the proposed environment. Do not assume a remote session behaves like a newly designed mobile web interface.
Consider Dataverse or a separate browser workflow
Microsoft describes Access data migration to Dataverse, including continued use of the desktop client. Review data compatibility and the application components needed around it before treating that as a complete replacement.
If users need a browser workflow, identify the forms, validation, roles and reports that workflow requires. It may be a bounded new interface or a larger rebuild; neither should be assumed to convert every Access object automatically. See the Access-to-Django implementation guide only if that architecture is justified.
Do not confuse file synchronization with a shared backend
Microsoft advises against opening an Access database from OneDrive or a SharePoint document library, explaining that multiple copies and unexpected behaviour can occur. Synchronizing a file is different from coordinating application users against an authoritative database.
A stored backup copy and the actively edited working database have different purposes. Decide which system owns live records, how front-end copies are distributed and how a user knows they are using the correct version.
Agree the operating model before choosing a provider
- Who owns the hosting, subscription and administrative accounts?
- What licences and ongoing support are required?
- Where are the working data, backups and connected services, and what requirements must they meet?
- What happens during loss of connectivity or a provider failure?
- Who tests recovery and manages updates?
- If old and new components coexist, which one may write each record?
Illustrative example: office staff may retain an Access interface while a proposed remote task needs only a controlled submission and review queue. The assessment must resolve record ownership and feasibility before that task is promised as an integration.
The Access assessment service reviews these options. Use the migration planning guide for transition controls and the cost guide to compare the selected architecture’s full scope.
Related reading
Sources and review notes
https://support.microsoft.com/en-us/access/migrate-an-access-database-to-sql-server
https://learn.microsoft.com/en-us/sql/ssma/access/migrating-access-databases-to-sql-server-azure-sql-db-accesstosql?view=sql-server-ver17
https://learn.microsoft.com/en-us/azure/virtual-desktop/overview
https://learn.microsoft.com/en-us/power-apps/maker/data-platform/migrate-access-to-dataverse
https://support.microsoft.com/en-us/access/import-link-or-move-data-to-sharepoint



Comments
Leave a comment
Comments are reviewed before publishing.