![]() The same experience would have been seen for any combinations of the following licenses: When tenant admins tried to assign more than one license pack (which contains Exchange Online) to the same AAD user, either through AAD PowerShell or the Microsoft 365 admin center or through group-based licensing in AAD, an exception message would have been shown and license changes would not have gone through.įor example, if the user already had a Microsoft 365 Business Standard license, and the admin tried to assign a second Exchange Online (Plan 2) license (either the standalone license, or as part of E3 or E5 suites), the following type of exception would have been raised in the Microsoft 365 admin center:Īnother example, where a user already has Exchange Online (Plan 1) assigned, and a tenant admin is trying to assign them an additional Microsoft 365 E5 license package: To better understand what this feature changes, let's compare the old behavior of Exchange Online license management, with the new behavior. Our new feature hence helps bring the same level of support to Exchange Online. ![]() SharePoint Online and Teams, for example, have been supporting concurrent license assignments for their own services for some time now. ![]() We recently enabled a new feature in Office 365, which allows tenant admins to assign more than one Exchange Online license per AAD user. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |