POS frontline and enrollment and all the licensing

%3CLINGO-SUB%20id%3D%22lingo-sub-2721612%22%20slang%3D%22en-US%22%3EPOS%20frontline%20and%20enrollment%20and%20all%20the%20licensing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2721612%22%20slang%3D%22en-US%22%3EI%20have%20a%20fairly%20unique%20situation%20where%20want%20to%20deploy%20massive%20amounts%20of%20POS%20terminals%20to%20multiple%20branches.%20Unfortunately%2C%20the%20frontline%20staff%20(majority%20do%20not%20have%20smartphones%20and%20change%20their%20cellphone%20numbers%20fairly%20frequently).%20Honestly%2C%20shift%20change%20and%20sign-on%20is%20also%20going%20to%20be%20a%20problem%20wrt%20password%20remembrance%20and%20resets.%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20do%20not%20intend%20to%20give%20a%20MS365%20account%20(F3%2BSecurity)%20for%20every%20user%20but%20would%20rather%20want%20to%20provide%20generic%20user%20to%20every%20device%20(i.e.)%20***%20Email%20address%20is%20removed%20for%20privacy%20***.%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20don't%20need%20any%20office%20functionality%20for%20the%20device%20or%20user%20either.%20Perhaps%2C%20just%20the%20branch%20manager%20which%20is%20a%20separate%20unique%20account.%20We%20have%20multiple%20staff%20using%20the%20devices%20(roaming)%20between%20them%20on%20any%20giving%20shift%20due%20to%20the%20nature%20of%20the%20POS%20sale%20and%20business.%20INW%20we%20cannot%20allocate%20a%20device%20to%20specific%20staff.%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20really%20just%20want%20the%20device%20to%20join%20the%20Azure%20AD%20to%20implement%20device%20policies%20and%20provide%20EDR.%20We%20have%20software%20(POS)%20which%20controls%20the%20access%20for%20every%20user%20on%20shift.%20We%20don't%20have%20any%20on%20prem%20AD%20or%20SCCM%20and%20wish%20to%20do%20everything%20via%20Azure%20AD.%3CBR%20%2F%3E%3CBR%20%2F%3EWhat%20is%20MS%20best%20practice%20in%20this%20case%3F%20Is%20this%20allowed%3F%20Also%20can%20i%20assign%20multiple%20devices%20with%20same%20account%20(i.e.%205%20devices%20per%20account).%3CBR%20%2F%3E%3CBR%20%2F%3EI%20have%20really%20asked%20many%20folks%20on%20this%20topic%20and%20everyone%20seems%20to%20have%20another%20idea%20or%20perception%20on%20the%20above%20matter.%3CBR%20%2F%3E%3CBR%20%2F%3EThanks%20in%20advance.%3CBR%20%2F%3E%3CBR%20%2F%3EDavid%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2721612%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAccess%20Management%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAzure%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EPOS%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Occasional Visitor
I have a fairly unique situation where want to deploy massive amounts of POS terminals to multiple branches. Unfortunately, the frontline staff (majority do not have smartphones and change their cellphone numbers fairly frequently). Honestly, shift change and sign-on is also going to be a problem wrt password remembrance and resets.

We do not intend to give a MS365 account (F3+Security) for every user but would rather want to provide generic user to every device (i.e.) *** Email address is removed for privacy ***.

We don't need any office functionality for the device or user either. Perhaps, just the branch manager which is a separate unique account. We have multiple staff using the devices (roaming) between them on any giving shift due to the nature of the POS sale and business. INW we cannot allocate a device to specific staff.

We really just want the device to join the Azure AD to implement device policies and provide EDR. We have software (POS) which controls the access for every user on shift. We don't have any on prem AD or SCCM and wish to do everything via Azure AD.

What is MS best practice in this case? Is this allowed? Also can i assign multiple devices with same account (i.e. 5 devices per account).

I have really asked many folks on this topic and everyone seems to have another idea or perception on the above matter.

Thanks in advance.

David
0 Replies