Comments on: What to Do About Exchange On-Premises After Microsoft Starts to Block Messages  https://practical365.com/what-to-do-about-exchange-on-premises-after-microsoft-starts-to-block-messages/ Practical Office 365 News, Tips, and Tutorials Thu, 12 Oct 2023 18:44:59 +0000 hourly 1 https://wordpress.org/?v=6.6.1 By: <div class="apbct-real-user-wrapper"> <div class="apbct-real-user-author-name">Becky Cross</div> <div class="apbct-real-user-badge" onmouseover=" let popup = document.getElementById('apbct_trp_comment_id_271793'); popup.style.display = 'inline-flex'; "> <div class="apbct-real-user-popup" id="apbct_trp_comment_id_271793"> <div class="apbct-real-user-title"> <p class="apbct-real-user-popup-header">The Real Person!</p> <p class="apbct-real-user-popup-text">Author <b>Becky Cross</b> acts as a real person and passed all tests against spambots. Anti-Spam by CleanTalk.</p> </div> </div> </div> </div> https://practical365.com/what-to-do-about-exchange-on-premises-after-microsoft-starts-to-block-messages/#comment-271793 Thu, 10 Aug 2023 18:33:58 +0000 https://practical365.com/?p=58976#comment-271793 Hi Callum, this change will not affect customers sending directly to recipients hosted by M365, since those messages do not enter M365 via the On-Premises Inbound Connector. Instead, those messages are routed to EXO via normal mail flow based on MX records and can be scanned by the recipient’s standard mail protection methods.

Microsoft is adding this change for Hybrid environments because messages routed from on-prem to EXO in a Hybrid configuration pass directly through the Inbound Connector and skip all the normal hygiene processes, so they are at greater risk when coming from unsecured systems.

]]> By: Callum https://practical365.com/what-to-do-about-exchange-on-premises-after-microsoft-starts-to-block-messages/#comment-271760 Thu, 10 Aug 2023 04:21:03 +0000 https://practical365.com/?p=58976#comment-271760 Is this only affecting Hybrid configurations or are customers without any sort of hybrid setup that are sending directly to recipients hosted by M365 also affected.

]]>