How to pause throttling and blocking of out-of-date on-premises Exchange Servers

Messaging_Ninja RE updating to .39 but report and cmdlet still shows .17.
First, you've updated to a compliant build (.39) so you're fine, not at risk for throttling. Second, by design the report currently only shows servers and server builds that currently are, or in the past were, detected as out-of-date (hence the name of the report: Out-of-date connecting on-premises Exchange servers). Since you updated to a compliant build the record in the report should show Status = Resolved, as designed. There was a report bug where that didn't get updated, but the fix for that is rolling out. If you don't see "Resolved" in the report DM me a large screen shot of the servers table in the report and your tenant ID and I'll confirm that you're fine.

That said, I hear you that you're expecting it to show the current build (.39) and the status. We're redesigning the report so in the future it'll do just that, show the current connecting server(s) and current detected build, with server Status either Up to date or Out of date. ETA later this summer.

SAust1655 DM me your tenant ID and I'll take a look. 

lgzplai Given your description of your company size and scale I assume you have a Microsoft account team - I suggest reaching out to them for assistance. 

MWill_LUS >>is Microsoft checking all message headers for all on-premises servers or only the ones that are actually connecting to Exchange Online?
Just the servers that are actually connecting to EXO. 

Best wishes,

Kevin Shaughnessy
Principal Product Manager | Exchange Online