EwsEnabled Set to False at Org Level but EWS Still Accessible‎

[synologywinniehsiao]

Describe the bug

After reading this article: https://techcommunity.microsoft.com/blog/exchange/exchange-online-ews-your-time-is-almost-up/4492361

I am trying to verify what happens when EWS is disabled, and the result is not expected. Here’s what I did:

1. Logged in via PowerShell with Connect-ExchangeOnline as a Global Administrator.

2. Ran Set-OrganizationConfig -EwsEnabled $false

3. Verified the setting with Get-OrganizationConfig | fl EwsEnabled — the result shows False.

4. Waited for over 24 hours, but my application can still successfully call EWS APIs, not expected.

Since we are planning to migrate our application to Microsoft Graph, I wanted to test the behavior when EWS is disabled in advance and understand how it would impact the current application.

Many thanks!

Expected behavior

After setting Set-OrganizationConfig -EwsEnabled $false and allowing sufficient time for the configuration to propagate, EWS should be blocked at the organization level. Any attempt to call EWS APIs should fail with an appropriate error (for example, an authorization or access denied error).

How to reproduce

1. Logged in via PowerShell with Connect-ExchangeOnline as a Global Administrator.
2. Ran Set-OrganizationConfig -EwsEnabled $false
3. Verified the setting with Get-OrganizationConfig | fl EwsEnabled — the result shows False.
4. Waited for over 24 hours, but my application can still successfully call EWS APIs, not expected.

SDK Version

No response

Latest version known to work for scenario above?

No response

Known Workarounds

No response

Debug output

Click to expand log

```

</details>


### Configuration

_No response_

### Other information

_No response_

[gavinbarron]

Looks like this is an issue with Exchange Online and not the Microsoft Graph PowerShell modules.

Try contacting the EXO folks https://www.powershellgallery.com/packages/ExchangeOnlineManagement/3.9.2/ContactOwners

Closing as there is nothing for my team to do here.

[synologywinniehsiao]

Hi, thanks for pointing me to the correct place to ask.
Sorry for the inconvenience, and I appreciate your help.