Throttling and Blocking Email from Persistently Vulnerable Exchange Servers to Exchange Online

B_Helt1273 Cris21875 I actually addressed this in a reply over on this blog post: How to pause throttling and blocking of out-of-date on-premises Exchange Servers - Microsoft Community Hub. I've pasted my response here for convenience. 

"We've received a few customer reports that after replacing their non-compliant server (2007, 2010, 2013) with a compliant server (2016 or 2019) the old server is still showing up in the report even though it's no longer sending mail and not connecting to EXO. This happens when the old and new servers have different names. If the servers have the same names then the record disappears when you bring it into compliance, and you won't see that server's record until the next time it goes out of compliance (out-of-date).  We do this for historical tracking, so you'll always have a record of what happened for a server and when. But if the replacement server has a different name than the old server, we can't associate the old server with the new server, so the old server still shows up as "Update required" even when it's no longer sending mail into EXO and no longer relevant. Understandably, that's confusing. While there's currently no way to hide the old server's record or show it as resolved, you can track the number of throttled and/or blocked messages for the server in the report - if those don't change over time any more then you know it's been resolved.

We're investigating different options to address this issue, and we expect to have an update out in the near future. If you have any feedback on what you'd like to see, please leave a comment or DM me. 

Apologies for the inconvenience and confusion, and thanks in advance for your patience while we work on an update. "

Best wishes,

Kevin Shaughnessy
Principal Product Manager | Exchange Online