Exchange Online Protection - rant on Office365 Support

%3CLINGO-SUB%20id%3D%22lingo-sub-2135995%22%20slang%3D%22en-US%22%3EExchange%20Online%20Protection%20-%20rant%20on%20Office365%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2135995%22%20slang%3D%22en-US%22%3E%3CP%3ESo%20I%20had%20this%20case%20with%20another%20IT%20provider%20who%20sends%20messages%20with%20failing%20SPF%20and%20thus%20marked%20as%20spam.%20That%20IT%20provider%20resists%20updating%20their%20own%20DNS%20for%20no%20reason.%20They%20were%20in%20contact%20with%20Office365%20support%20(security%20and%20compliance%20team)%20who%20mentioned%20%22adding%20domain%20to%20allow%20list%22%20as%20a%20viable%20solution.%20Microsoft%20docs%20states%20very%20clearly%20that%20this%20is%20not%20recommended%20and%20is%20a%20high%20security%20risk.%20It's%20crazy%20to%20see%20that%20Office365%20support%26nbsp%3B(security%20and%20compliance%20team!)%20would%20suggest%20doing%20that..%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2135995%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Contributor

So I had this case with another IT provider who sends messages with failing SPF and thus marked as spam. That IT provider resists updating their own DNS for no reason. They were in contact with Office365 support (security and compliance team) who mentioned "adding domain to allow list" as a viable solution. Microsoft docs states very clearly that this is not recommended and is a high security risk. It's crazy to see that Office365 support (security and compliance team!) would suggest doing that..

0 Replies