-
Ability to activate Modern POS device/register at PC scope
Currently Retail Modern POS can only be activated at user scope. This means that if multiple workers needs to use the register, they would still be logged in under the same windows account. Can there be a way to allow activation in such a way that any logged in windows user can use that register for sales? Under current functionality, potentially, we could activate multiple registers on the same PC under each windows user, however, Modern POS complains about the first register that was activated when trying to access second register under a different windows user profile. That error message says "You can't access devicefrom here becuase device is currently activated. Deactivate device and then try again. This message is misleading, because if you try to activate the original register under a different windows user, it will then get deactivated from the original windows profile. Scenario: windows user 1 - register 001 windows user 2 - register 002 when logged in as windows user 1 register 001 comes up and allows worker to login when logged in as windows user 2 register 002 displays error message described above and then shows login page. So the request for feature is to allow Modern POS activation to be windows user independent. -
Azure AD Forms Based Authentication when using AAD Functionality Profile
When using AAD Sign-in functionality profile for MPOS, the authentication defaults to "Windows Security" pop-up if the MPOS PC is joined to a domain and the organization uses AZ as well as Active Directory. Please implement Azure AD Forms based authentication within MPOS so complete authentication experience can be handled by the application instead of handing off to the OS. The hand off can cause an issue when organization has policies defined that for example restrict username/password sign-in and enforce PIV only sign in.
