Concurrent Exchange Online License Assignment Supported! Finally!!!

I’m back from winter break and today’s #MicrosoftCloudQuickFix is #Microsoft365 finally supports concurrent Exchange Online License Assignments!!! This is going to dramatically reduce the administrative burden managing #ExchangeOnline license assignments and specifically will allow an intuitive groups-based licensing strategy!

Previously when Microsoft 365 Tenant Admins tried to assign more then one license pack containing #ExchangeOnline to the same user, whether that be thru the Microsoft 365 Admin Center, #AzureActiveDirectory PowerShell, or group-based licensing, an exception message would be displayed and the assignment rejected.

In this case the user already has an Exchange Online Plan 1 license included in Microsoft 365 Business Standard suite and the Tenant Admin is looking to upgrade the user to an Exchange Online Plan 2 license likely to take advantage of the larger mailbox size, Data Loss Prevention, In-place Hold, or Exchange Online Archiving capabilities.

The same exception message is displayed for any combination of the following licenses:

  • Microsoft 365 Business packages: Basic, Standard, Premium
  • Microsoft / Office 365 F1, F2, F3, E1, E3, E5, A1, A3, A5
  • Exchange Online Essentials
  • Exchange Online Kiosk
  • Exchange Online Plan 1
  • Exchange Online Plan 2
  • Other #MicrosoftTeams and #MicrosoftProject license packs which rely on Exchange Online

Now with this change any combination of the above is allowed and Exchange Online will automatically decide which of the assigned plans is “superior” and will enable the features of that plan (mailbox quotas, transport limits, protocol access, etc.).

When a license is removed Exchange Online will reevaluate and adjust as needed to the new superior plan.

For more information, please see the following Exchange Team Blog post.

#MicrosoftCloudQuickFix #Microsoft365 #AzureActiveDirectory #ExchangeOnline

Azure AD Connect V1.x End of Support

For the last few weeks we have been advising that all Azure Active Directory Connect V1.x versions would reach end of support on August 31, 2022. Well that’s tomorrow and in case you haven’t yet upgraded here is your #MicrosoftCloudQuickFix !

Azure Active Directory Connect supports a couple different methods for upgrading from previous versions from an in-place upgrade to a swing migration upgrade depending on the complexity of your deployment and/or if you need to upgrade Azure Active Directory Connect onto a newer version of the Windows Server Operating system. Windows Server 2016 is the minimum supported version of Windows Server but we recommended Windows Server 2022.

For both the in-place upgrade and swing methods please see the instructions contained in Azure AD Connect: Upgrade from a previous version to the latest. Specific to the swing method please see instructions on how to Import and export Azure AD Connect configuration settings.

Note: A handy tool is available from Microsoft to document and report on the current configuration of an Azure Active Directory Connect installation named Azure AD Connect Configuration Documenter. This tool can be used to create a comparison report for a swing migration.

#Microsoft365 #AzureActiveDirectory #AzureADConnect #MicrosoftCloudQuickFix

Aug 19, 2022 – New Podcast Available

In this episode Ryan McKay and Andrew Lowes discuss the retirement of Azure Active Directory Connect V1 and steps to transition to V2 of Azure Active Directory connect.

URLs shown in today’s video podcast include:

https://azure.microsoft.com/en-us/updates/action-required-upgrade-to-the-latest-version-of-azure-ad-connect-before-31-august-2022/

Azure AD Connect: Version release history

#Microsoft #Microsoft365 #AzureActiveDirectory #AzureADConnect #MicrosoftCloudQuickFix