This feature idea is to allow switching Store Commerce (and MPOS) to offline mode even when Azure AD Login Authentication Method is enabled in a store via the Functionality profile. Currently AD Authentication can only work in online mode which essentially eliminates offline support. This means that customers that need to support offline mode and functionality cannot take advantage of some new and important collaboration and productivity capabilities such as Task Management and M365 Teams integration. Since offline capability is a requirement for most retail operations, we need these features to coexist. In order to support both concurrently our suggestions are as follows:

1. Support AAD Offline tokens so that Store Commerce can seamlessly switch to offline mode if connectivity is lost to the HQ Scale Unit
2. Alternatively, auto switch to the Standard Personnel ID and password method if connectivity is lost to the HQ Scale Unit
3. Consider moving the AAD Login Authentication configuration setting to the Hardware profile to allow some devices in store to be configured with AAD while others to continue using the traditional personnel ID and Password methodology
4. Many retailers leverage Android devices for some store operations and line busting while leveraging other Windows device to support offline mode within the same store
5. Since the login methodology today is inherited from the functionality profile to all devices in the store it is not possible to have a mix depending on the customer’s needs
6. Another option for more device flexibility is to allow configuring the Login Authentication at the Register and Worker level and use an override methodology similar to how Screen layouts work today. If there is a value at the Store level, all registers and workers inherit that value. If the value is set at the Register level, it overrides what is set at the Store level. And finally, if this is set at the worker level, that would override all other settings.
7. This also gives the retailer the flexibility of offering M365 Teams/Task Management to the most appropriate workers and devices.
8. For example, all managers might always have AAD to insure they are connected via M365 Teams (when connectivity is available), but allow Android or Hybrid devices to continue using the traditional login since they might not need the M365 Teams integration and since they don't support offline capabilities anyway
9. On devices that are smaller sizes running android or hybrid POS the login is easier than the more complex AAD login steps