Windows Office Hours: September 28, 2023

All deleted... disappointing... Thx for your good intention though! I really appreciate it. Have a nice one!

Sorry... it got deleted again. I might be using some restricted statements because I'm sure I'm not writing anything wrong, rude, nor obscene. It's related to route "customername.onmicrosoft.com" emails to a 3rd party solution provider gateway. I won't write more details to see if it can stay this way.

Thank you, Thomas... let's try... A customer is facing an issue with emails sent to "customername.onmicrosoft.com" email addresses. They want those emails sent to such aliases (default email addresses are using customer's custom domain) to be routed to a 3rd party security solution. Microsoft official response was to have them routed through and ETR (Exchange Transport Rule), which never worked. We found later the reason is because transport rules apply after the recipient is resolved and the post-resolution email address is changed to the user custom domain bypassing the rule. We have spent many many hours in calls with Microsoft Support without a fully working solution. We don't want the 3rd party solution to be configured by Microsoft, just all traffic sent to "customerdomain.onmicrosoft.com" email addresses routed to it. This was easily done for the custom domain (pointed the DNS MX record to the 3rd party gateway), but there is no such option to the same for the "*.onmicrosoft.com" domains (although Microsoft owns these, onmicrosoft.com subdomains are independent from its parent and it should be possible), only TXT records can be managed for them. Anyways... I was hoping to find any help about this on this session. Any help would be great! Thank you!