Said It Here

Why do Power Automate flows break when EWS is disabled?

Disabling Exchange Web Services blocks legacy protocols used by standard email connectors like Office 365 Outlook. This causes automated workflows such as Power Automate email actions to fail across your tenant unexpectedly.

What people tried

Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.

  1. 1
    Running PowerShell scripts to check organization configurations
  2. 2
    Manually setting EwsEnabled true per client
  3. 3
    Building allow-lists and identifying apps using legacy protocols
  4. 4
    Adding specific connector IDs and application paths to the EwsAllowList configuration.

In their words

Unedited, most upvoted first, each linked to the thread it came from.

“When I disable EWS for apps in my tenant, except for my allow list, Power Automate flows using the Send an email (V2) action from the Office 365 Outlook connector break.”source ↗

Odd-Cod3753 · r/sysadmin · 4 upvotes

“EWS report lists Apple as the one and only offender for our tenants.”source ↗

devloz1996 · r/msp · 1 upvotes

Where this came up

r/mspr/sysadminadministrationautomationcloud-servicesemailsystem administration

People with this problem also raised