What are compliant Microsoft 365 licensing options for casual warehouse staff using shared iPads?

If the requirement is only a locally installed Office application, device-based Microsoft 365 Apps licensing may be worth evaluating for shared workstations. That option is more specialized and may require an appropriate volume licensing agreement, so it is unlikely to solve a SharePoint or Power Apps licensing requirement on its own.

The exact app matters, but for Power Apps and SharePoint you generally need to license the users who access them. A guest account is not automatically a free alternative, and a shared account would undermine individual accountability. Check whether the Power App uses premium connectors or Dataverse, since that can require a separate Power Apps license in addition to any Microsoft 365 entitlement.

Microsoft 365 F1 or F3 may fit frontline workers, depending on the required features. F1 is often the lower-cost starting point, but verify the current terms and whether the users need SharePoint, Teams, conditional access, or other services. The fact that the device is shared does not generally remove the requirement to license each person using the service.

If the business refuses every applicable license, there may simply be no compliant Microsoft solution for the requested access. A shared iPad is a device arrangement, not a shared-user license. Document the requirement and have whoever owns licensing, security, or legal risk approve the decision rather than quietly implementing a shared account.

There can be standalone licenses for individual services instead of buying a complete bundle, but they still normally attach to named users. For SharePoint, the practical design is usually individual identities with the appropriate license, plus shared-device configuration and strong sign-in controls. A generic login may appear cheaper, but it creates audit, MFA, offboarding, and compliance issues.