Update on Transport Enforcement System in Exchange Online

The detected build are bugged as heck.

The CU version we run is originally 15.1.2507.6, but with all patches it actually is 15.1.2507.39.

WHY IS Microsoft still detecting the .6 version??

Also the ExSetup.exe file is .039, so why only detect the initial CU version instead of the actual live version?

Why is Microsoft throtteling and blocking my up to date 2016 on-prem server?

Is this a False positive?

Before last thuesday it ran on 15.1.2507.37 which is also a supported version.

Also, we did not get any notification the server was throttled, we found out when users starting to receive NDR.

Not happy at all with this.

We need migrate 3 servers Exchange 2013 to Exchange 2019 but we don't have enough time and the servers stop 20 min everyday. The enviroment is too complex and we need more time to do this migration, we get the license but is not possible, a lot of users still on these servers. Is it time extend at least 30 days to migrate these servers ?

Apologies in advance if there is a post that addresses this question but has the enforcement date for Exchange 2016/2019 been pushed out? Is there a new target date for enforcement?

BalakrishnaG, you can find details of our roadmap at Exchange Server Roadmap Update - Microsoft Community Hub.

Deleted, yes for all versions mentioned above, we are targeting the specific configuration of OnPremises inbound connector in a hybrid configuration.  We will post future announcements when we move beyond this configuration.

esczerwin2021, Currently, we're targeting servers that are out of support.  When we move to servers that are out of date (later this year), we'll announce the minimum compliant build requirements.  The minimum compliant build requirements will be determine using a number of variables, but the last thing we want to do is make it difficult for customers (so we won't block your email if you haven't installed an update in 30 days, etc.).

How long after a CU or SU has been released is a Hybrid connection point server considered out of date? Meaning when does the clock start ticking on the enforcement duration? 30 days after release? 60 days? 90 days? This is very important because most Organizations take over 30 days to patch their Lab/QA environments prior to Production. Also It is considered Standard Operating Procedure to wait a for a period of time before patching in case of a failed release (e.g. SU February 2023). If the clock starts ticking the moment a CU/SU has been released I consider this to be extremely aggressive given failed updates that have been released in the past.

BalakrishnaG Check out https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-server-roadmap-update/ba-p/3421389 

BalakrishnaG  I understood that those 2016/2019 blocked in 2024 are refering to vunderable (lack of CU or SE) instance of that versions.

Thanks for your comments. i agree, this aligns with the legacy systems and supported outdated versions. I know this talks only about the Exchange servers (Hybrid mail flow), just curious to know, What is the MS plan for other SMTP servers(Linux and etc) relay their emails via EXO. Not sure how it’s going to impact them. Also MS is releasing the SE editions for other services. I hope it applies to EX as well. 

Just to confirm, this timeline is only for M365 tenants with an inbound connector to an on-premise with an outdated version of Exchange (i.e. within an organisation)?  This timeline isn't for external organisations with outdated versions that send to a M365 tenant?