I'm setting up a shared, multi-user Entra-joined Windows laptop for healthcare staff, mainly nurses, using Autopilot Self-Deploying mode. The device isn't hybrid joined and has no on-premises AD computer object, but on-premises single sign-on works through the standard Entra authentication setup for file-server access. The device is shared by a mix of F3 and E3 users. Shared Computer Activation lets E3 users run the desktop Microsoft 365 apps, while F3 users are directed to Outlook, Word, and Excel on the web through installed Edge web apps. The problem is that our healthcare documents still live on an on-premises SMB file share. F3 users can browse and copy files in File Explorer, but Office for the web cannot open or save files directly from a local or network drive. SharePoint/OneDrive migration is planned but won't happen soon. Possible alternatives include device-licensed Office LTSC, a third-party gateway that connects Office for the web to the SMB share, or changing the users' licenses. Has anyone implemented a reliable production solution for this scenario?
3 Answers
Office for the web doesn’t support opening files directly from an on-premises SMB path. The straightforward workaround is to install a device-activated desktop Office edition, such as Office LTSC, so users can edit files from the mapped or network drive without relying on their individual Microsoft 365 license.
If changing the licensing model is possible, assigning the affected users a license that includes the desktop Microsoft 365 apps would avoid the web-app limitation. Other lower-cost fallbacks are LibreOffice or another locally installed office suite, but compatibility with healthcare templates, macros, and document formatting should be tested carefully.
A non-KMS option is Office LTSC Professional Plus 2024 activated with a MAK key. That provides locally installed Office for the shared device, though you’ll need to confirm the licensing and deployment model fits the organization.

Upgrading the users would solve the technical problem, but budget approval is difficult, so we’re trying to find a device-based or lower-cost option first.