No change.
Throttling / blocking is not a “you need to be on the latest build” enforcement system. So far, we have had a generous number of builds that are not considered “persistently vulnerable”. Our business is not throttling or blocking emails.
Throttling / blocking builds are decided on by humans after triaging the security payload that we have released in the past. In the case of a really high severity vulnerability (think of something like HAFNIUM from a few years ago) - I expect that we would bring the “persistently vulnerable” bar much closer to the present time sooner, than if we did not have such things. Therefore, there is no set “amount of time” that throttling / blocking covers, because that time can change.
Do we have plans to throttle / block fully up to date E2016/E2019 in November 2025? No. Could there be a set of circumstances that makes it so we block them somewhat soon after they go out of support? Possibly… but realize that if that happens, there are serious security vulnerabilities that we are dealing with, and everyone really needs to be updating their servers ASAP. There is no "calendar schedule" that decides this.
Also remember that the only servers that are throttled / blocked are the ones with connectors to Exchange Online. Update those.