Client application doesn't honor EwsAllowList in Exchange Server 2019 and 2016

Symptoms

In Microsoft Exchange Server 2019 or Exchange Server 2016, assume that you try to prevent client applications from using REST and EWS by using the EwsAllowList parameter in the Set-OrganizationConfig cmdlet. However, you experience an issue that the application doesn't honor the EwsAllowList parameter. The client application can still use the REST and EWS to connect to Exchange Server even if the value of EwsAllowList is set to null (it prevents all client applications from using REST and EWS).

Cause

This issue occurs because all users have the EWSEnabled parameter set to null by default in on-premises Exchange. This setting allows all clients that have null set in EWSEnabled to access without checking EwsAllowList. 

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Resolution

To fix this issue, install one of the following updates:For Exchange Server 2019, install the Cumulative Update 1 for Exchange Server 2019 or a later cumulative update for Exchange Server 2019.

For Exchange Server 2016, install the Cumulative Update 12 for Exchange Server 2016 or a later cumulative update for Exchange Server 2016.

References

Learn about the terminology that Microsoft uses to describe software updates.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×