Forum Discussion
Moving mx records to O365
- You're so welcome!
So that's the beauty of TABL (see above link) - it will be honoured and is the correct new way to allow senders that are caught incorrectly, rather than in the spam filter policies or transport rules. (Please also do an admin submission!) - this way you can use secure presets and not need to edit them.
Microsoftskipster311-175 - Thanks for such a great question, and I'm super glad to hear you're going with MDO!
We have a detailed migration guide here you should find useful: Migrate from a third-party protection service to Microsoft Defender for Office 365 - Office 365 | Microsoft Docs
Speaking from my experience, I've done both the SCL-1 method detailed in the above guide, and your mentioned method of domain by domain. - Either way the desired outcome is the same, moving carefully and slowly to ensure minimal disruption, so that's completely up to you!
Regarding your comment for safe senders, my advice is that you shouldn't need to import a single safe sender, this brings legacy debt across to your new configuration and opens up holes in your protection stack. The good news however is that by moving slowly as you plan to, you can address senders one by one, sending test emails and then fixing issues with things like SPF/DKIM to ensure correct authentication and remove the need for a safe sender / allow list entry.
However, these are sometimes required in situations where you don't control the sending infrastructure and for example the company who owns the sending infrastructure may not be in a position to support DKIM signing at this point in time - so I'd recommend using TABL here instead. (if however it's a false positive from our side, please report it to us so we can fix it!)
My final point is around preset policies, please do use them, it keeps everything up to date for you as / when we release new protection features, sets you up for continued success in the long term. - TABL will be honoured so if you do have to add a safe sender, this will be respected by the policy!
I wish you a really successful migration, and would love to hear how you get on, don't afraid to ask any other questions you may have, hopefully this has been helpful!
Thanks
Ben.
- Thanks Ben for the detailed information. I do like the idea of using preset security policies for the reasons that you mentioned, however if i cant edit them, then i fear it will open up the door to creating custom polices, to allow for things like block or allow bulk email. If i have to add a sender to skip spam filtering, is the recommended approach to use a transport rule , instead of adding the sending to allow list in anti spam policy ?
- Ben_HarrisYou're so welcome!
So that's the beauty of TABL (see above link) - it will be honoured and is the correct new way to allow senders that are caught incorrectly, rather than in the spam filter policies or transport rules. (Please also do an admin submission!) - this way you can use secure presets and not need to edit them.- Hi Ben
From my understanding around adding a sender to TABL is I have to use "Admin submission" I cannot add a sender using TABL. Is this correct? It does appear that I can use TABL to allow a spoofed sender ?
