Six months until Exchange Server 2016 / 2019 End of Support

Do you have old on-premises Exchange servers kicking around? Old Hybrid Exchange servers left over from a previous Exchange Online Migration or an anonymous SMTP relay? Last week marked t-minus 6 months until the end of support for Microsoft Exchange Server 2016 / 2019. After October 14, 2025, Microsoft will no longer provide technical support, bug fixes, or security updates. What are your options? This is today’s #MicrosoftCloudQuickFix !

Of course, on October 15, 2025, your Exchange 2016 and Exchange 2019 will continue to work but it is recommended you begin to prepare now.

We recommended that you either fully migrate to Exchange Online as moving to Microsoft Cloud Services ensures continuous support, access to advanced features, and security advancements or (and if you haven’t done this by now there is likely good reason) upgrade your on-premises Exchange Servers to Exchange Server Subscription Edition (SE) to be released in July 2025 and offers a direct in-place upgrade from Exchange Server 2019 CU 15 released in February 2025.

If you are still running Exchange Server 2016 you should perform a side-by-side ‘legacy upgrade’ to Exchange Server 2019 CU 15 now and then perform the in-place upgrade to Exchange Server SE once released. The good news is Exchange Server 2019 CU15 is fully supported on Windows Server 2025!

Exchange Server SE is the next release of Microsoft Exchange Server and will be available for download in July 2025. The licensing model for Exchange Server SR requires subscription licenses for all users and devices that access Exchange Server SE on top of required Server licenses and CALs. Microsoft will continue to provide a free Hybrid server license and key via the Hybrid Configuration Wizard.

See for more information see:

Microsoft Cloud Quick Fix Exchange

Now that you know your options, it’s time to start planning your transition.

#MicrosoftCloudQuickFix #Microsoft365 #MicrosoftExchange #ExchangeOnline

Change to user sign-in experience with Microsoft Authenticator

Ever had connectivity issues that delayed your MFA authentication? Left your phone by the coffee pot but have your cup ready for the meeting? One-time code expired before you could use it? Microsoft is changing the user sign-in experience to help reduce duplicate request errors and allow the user to refresh their notifications in the Microsoft Authenticator app. This is today’s #MicrosoftCloudQuickFix !

With the rollout of this change the user sign-in experience will include the message, “Didn’t receive a sign-in request? Swipe down to refresh the content in your app.” advising the user that they can refresh notifications in the Microsoft Authenticator app (or Microsoft Authenticator Lite for Outlook mobile) if they have not received the sign-in notification. Once refreshed the user can complete the sign-in.

Screenshot of new user sign-in experience

This is already in General Availability and began rollout worldwide in late March 2025 with an expected completion by mid-April 2025.

Although no administrator action is needed to prepare for this change it is recommended to notify users of the change and update training documentation.

For more information see:

#MicrosoftCloudQuickFix #Microsoft365 #MicrosoftCloudSecurity #MicrosoftEntraID #MicrosoftAuthenticatorApp

Keep your Microsoft Teams desktop clients up to date

Microsoft has announced that it will block access to versions of the Microsoft Teams desktop client older the 90 days. Enforcement of this policy has been deferred several times but it is now proceeding and that is today’s #MicrosoftCloudQuickFix !

Keeping Microsoft Teams up to date is critical to ensure devices remain secure and compliant. By default, Teams updates automatically which successfully updates most clients around the world without user interaction.

With this announcement Microsoft Teams desktop clients older than 90 days will be blocked. Users with these versions will see a blocking page and won’t be able to use the app.

The blocking page will be displayed:

  • Starting April 11th, 2025, for users using the Windows desktop app
  • Starting May 6th, 2025, for users using the Teams app in VDI environment
  • Starting May 15th, 2025, for users using the Mac desktop app

An in-app warning banner will appear 60 days beforehand (30 days before for VDI versions) to remind users they need to update.

To prepare for this change make sure you’ve updated to the latest version of Microsoft Teams either by going to the download page (listed below) or inside the Teams client under the ellipsis menu ( … ) -> Settings -> About Teams.

Microsoft Teams about page screenshot

Administrators should make sure their users Teams application is automatically updating to stay current.

For more information see:

#MicrosoftCloudQuickFix #Microsoft365 #MicrosoftTeams