We recently enabled a new feature in Office 365, which allows tenant admins to assign more than one Exchange Online license per AAD user.
SharePoint Online and Teams, for example, have been support...
Hi, hoping someone could help clarify this feature and what the expected experience should be based on how we distribute licenses. We assign all our M365 licenses via AAD group membership. We have an AAD group for our Office 365 F3 licenses and another for our M365 E3 licenses. We often get warehouse workers who start with a Office 365 F3 license (since they just use a shared Kiosk for accessing email in OWA once every few months) but because of a role change or specific project, they need to use a desktop with the full Office suite. The help desk often adds the account to the AAD group for the M365 E3 license and forgets to remove them from the AAD group which assigns the O365 F3 license. Looking in AAD for the user, we get the normal 'conflicting service plans' error and the O365 F3 license remains active until they get removed from that AAD group. We thought this would resolve that but that has not been the case. Are we interpreting this Concurrent License Assignment feature wrong? Does this not fix our issue (until we get the proper automation in place)?