MicrosoftSundeep_Saini thank you for these informative posts and all the links and additional info. I have a question that indirectly relates to these changes.
We have a ticketing system set up to send from our 365 mailboxes, so the sender address looks like an internal address from our company. The ticketing system uses SMTP2GO to relay all emails sent from it, to both external customers and our internal users. SMTP2GO emails seem to be automatically marked as High Confidence Spam ( not phish ) by the spam filter ( I think based on the fact that their origin is New Zealand / outside our country ), so the filter wants to send them to Junk.
We have an ETR which bypasses the spam filter based on the specific IP addresses that SMTP2GO uses. As I understand, this particular ETR will not be affected by these changes because it's for spam, not phishing, however, I wanted to ask if we should be doing this differently, or if there's a way to migrate this and other ETRs from the old Exchange Admin Center into the newer 365 Defender systems. Or, how can I contribute to telling the spam filters that SMTP2GO isn't automatically High Confidence Spam? I've already submitted several messages a long time ago, and it continues to mark them as HCS.
