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

>>IanH1. . .running the report after performing an upgrade/update to the exchange build. Is there a way to test or confirm that an exchange server will not be throttled in the future, other than just looking at the server build number? 

Yes, but it depends on your update path. If we detected a server with a non-compliant build which you then update to make it compliant (preserving the same server name) then you should, after updating to a compliant build, see that server's record with Status = Resolved, with the Details column stating the server was updated to an up-to-date build. This is as an historical record of the server's non-compliant state (that's now resolved). It's NOT a record for the existing (compliant) state of the server, so the Detected build for this record will still show the old non-compliant build. So long as Status = Resolved then you're not at risk for throttling. If that's your scenario (sounds like it is) and if you're not seeing Status = Resolved yet, you should soon - there was a report bug that obscured that in some scenarios, a fix for which is rolling out. 

FWIW, the original intention of the "Out-of-date connecting. . .servers" report was to show ONLY non-compliant servers that will be throttled if not updated; it was to help assuage any worry that all your servers were at risk: "Nope, just those servers that show up in the report are at risk for being throttled" was the idea. Well intended, but it falls short of what folks suggest they want/need. So we're redesigning the report to show ALL connecting servers all the time, and show Status = Up to date, or Status = Out of date for each (rough ETA later this summer).