I've been looking more into Power Apps, and I think it would be great for you to work with the Power Apps team to provide a web and mobile solution to what Access can do today on the premises of a server. Because there is unfortunately no web version of Access, maybe Power Apps can help solve this problem? Ideally, we should be able to continue moving (and linking) Access data into SQL and then create a Power App on top of the "Access-created" data from SQL; essentially viewing a Power Application that looks exactly like access but online and on the phone.

Every now and again, each of our developers experiences an issue where Access will crash the first time you try to use intellisense when writing VBA code.

To get back up and running, decompiling the database always fixes the issue, but surely the editor could deal with this by suggesting the user decompiles and recompiles the code, instead of dropping out and potentially losing a lot of unsaved changes.

Example from such a crash -

Faulting application name: MSACCESS.EXE, version: 16.0.13029.20534, time stamp: 0x5f53f9d7
Faulting module name: VBE7.DLL, version: 0.0.0.0, time stamp: 0x5ea725ac
Exception code: 0xc0000005
Fault offset: 0x000256bc
Faulting process ID: 0x3748
Faulting application start time: 0x01d6a38b4a0cc91c
Faulting application path: C:\Program Files (x86)\Microsoft Office\Root\Office16\MSACCESS.EXE
Faulting module path: C:\Program Files (x86)\Common Files\Microsoft Shared\VBA\VBA7.1\VBE7.DLL
Report ID: 14338b0a-4d1f-432d-b845-f3272647ccc1
Faulting package full name:
Faulting package-relative application ID:

In order to add a Add-in (.mda) file into MS Access, the user has to be in the local admins group. Even if you are a domain admin, not having local admin rights won't work because your user profile changes when you open MS Access as Admin with other credentials.

Full Detail: In order to Install an Add-in library in MS Access 2016 (and at least the two prior versions) you have to open MS Access 'Run as Administrator', then do the install, then close and reopen as the standard user. If you are not in the local administrators group you must log off, login with admin rights, add the user into the local admins group, logout, login as user, run MS Access as Admin, install the add-in, remove the user from the local admins group, then logout and back in again to use it.

The simplest solution is to allow this whole process to be done by the regular user, as long as the appropriate settings are in the Trust Center. Could be anything; Add-in File in the Trusted Locations, Add-in File is a Trusted Document, Add-in File is Digitally Signed requirement stops install if not signed, but otherwise allow. I like the last one the best myself.

Use EdbMails for seamless migration of user mailboxes from PST files to Office 365. Thanks to its easy to use user interface, even a non-technical person can easily make use of the PST to Office 365 migration utility from EdbMails and perform the migration operation.
EdbMails will display all the mailboxes/ users from your Office 365 tenant during PST to Office 365 migration operation. You can map your PST mailbox to Office 365 user account easily and even apply include/exclude email filters.
Some of the salient features of EdbMails Import PST to Office 365 Migration tool include:
Truly secure Migration of all PST file data
Reliable Outlook PST to Office 365 migration
Incremental PST migration to ensure there are no duplicates
Brick level migration that allows you to migrate individual items of your choice from mailbox/folders
Capable of recovering unintentionally deleted items
No Outlook dependency

Visit: https://www.edbmails.com/pages/pst-migration-tool.html