Office SCC doesn't get email-forwarding rule alerts from Windows Outlook

%3CLINGO-SUB%20id%3D%22lingo-sub-2278720%22%20slang%3D%22en-US%22%3EOffice%20SCC%20doesn't%20get%20email-forwarding%20rule%20alerts%20from%20Windows%20Outlook%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2278720%22%20slang%3D%22en-US%22%3E%3CP%3EIn%20Office%20365%20Security%20%26amp%3B%20Compliance%20center%20(protection.office.com)%2C%20we%20used%20to%20get%20alerts%20from%20policy%20%22Creation%20of%20forwarding%2Fredirect%20rule%22%20when%20we%20create%20rules%20in%20Outlook%20in%20Windows.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20late%20March%2C%20we%20one%20day%20realised%20alerts%20were%20no%20longer%20following%20in%20SCC's%20alerts%20list%3B%20users%20reporting%20malicious%20emails%20show%20up%20in%20our%20report-archival%20mailbox%20but%20no%20corresponding%20%22Email%20reported%20by%20user%20as%20malware%20or%20phish%22%20alert%20policy%20trigger.%20After%20a%20lengthy%20check%20with%20Microsoft%20support%2C%20it%20appears%20the%20backend%20mechanism%2Fservice%20for%20flowing%20these%20alerts%20was%20faulty.%20Eventually%2C%20we%20were%20able%20to%20see%20alerts%20flowing%20in%20again.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOne%20odd%20residual%20thing%20though%2C%20the%26nbsp%3B%22Creation%20of%20forwarding%2Fredirect%20rule%22%20alert%20only%20happens%20if%20we%20create%20forwarding%20rules%20in%20%3CEM%3EOutlook%20Web%20Access%20(OWA)%3C%2FEM%3E.%20No%20alert%20triggers%20if%20we%20use%20Outlook%20in%20Windows.%20Support%20mentions%20it%20could%20be%20due%20to%20the%20difference%20between%20server-side%20rules%20and%20client-side%20rules.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%2C%20on%20further%20inspection%2C%20the%20forwarding%20rules%20do%20not%20have%20client-side-only%20conditions%20(and%20it%20used%20to%20work%20in%20the%20past).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3EIf%20sender%20is%20%3CCERTAIN%20party%3D%22%22%3E%3C%2FCERTAIN%3E%3C%2FLI%3E%3CLI%3EForward%20to%20%3CEXTERNAL%20email%3D%22%22%20address%3D%22%22%3E%3C%2FEXTERNAL%3E%3C%2FLI%3E%3CLI%3EStop%20processing%20more%20rules%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20other%20conditions%20could%20be%20in%20play%20here%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2278720%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Occasional Contributor

In Office 365 Security & Compliance center (protection.office.com), we used to get alerts from policy "Creation of forwarding/redirect rule" when we create rules in Outlook in Windows.

 

In late March, we one day realised alerts were no longer following in SCC's alerts list; users reporting malicious emails show up in our report-archival mailbox but no corresponding "Email reported by user as malware or phish" alert policy trigger. After a lengthy check with Microsoft support, it appears the backend mechanism/service for flowing these alerts was faulty. Eventually, we were able to see alerts flowing in again.

 

One odd residual thing though, the "Creation of forwarding/redirect rule" alert only happens if we create forwarding rules in Outlook Web Access (OWA). No alert triggers if we use Outlook in Windows. Support mentions it could be due to the difference between server-side rules and client-side rules.

 

However, on further inspection, the forwarding rules do not have client-side-only conditions (and it used to work in the past).

 

  • If sender is <certain party>
  • Forward to <external email address>
  • Stop processing more rules

 

What other conditions could be in play here?

0 Replies