![]() Make a note of the ConsumedUnits count (here 173) of the current assigned licenses, as this will be used during the final verification. With PowerShell we can see that they are actually two different licensing SKU ID’s (SKU = Stock Keeping Unit), and this also tells us, that there is difference between the two licenses. Looking in the Office 365 Portal, you may be surprised to see two seperate licenses, as they have the exact same name ( Office 365 Business Essentials), and therefore should be pooled. This situation is ideal for using the Azure AD PowerShell module to perform the license switch.įirst, we need to get the old and new license SKU, using the Get-MsolAccountSku cmdlet.ĪccountSkuId ActiveUnits WarningUnits ConsumedUnitsĪdatumdk:POWER_BI_INDIVIDUAL_USER 100 0 98Īdatumdk:O365_BUSINESS_ESSENTIALS 175 0 0Īdatumdk:SMB_BUSINESS_ESSENTIALS 175 175 173 ![]() When making changes to licenses in Office 365, I sometimes experience that the old and new licenses include options that conflict, and does not allow the licenses to be pooled or added to accounts at the same time.Ĭhanging the license of users in Office 365 need to be performed without impacting the end users or affecting the services and data they consume.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |