What has broken as EWS gets switched off?

November 17, 2026 4 answers
Asked by 6z+ledgerwhisk_914

We're looking at contact and calendar sync options and trying to avoid a new dependency on Exchange Web Services. What kinds of integrations have been affected, and how did you find the ones still using EWS?

Did an app allow list buy enough time, or did you have to replace tools? I'm especially curious whether vendors had Microsoft Graph replacements ready.

Answers

9p~gimbalwinder_375

The awkward stuff isn't always the obvious mailbox client. Room booking panels, scheduling integrations, backups and helpdesk mail features can all depend on EWS. Some may be old enough that nobody has them on the current integration inventory.

Vendor readiness varies. A Graph update might exist but come bundled with other changes you need to test. In other cases, the vendor may not plan an update at all, so keeping EWS available only postpones the replacement decision.

Reply to this answer
Nerxavo-3h

Start with the EWS usage report, but don't expect a tidy list of product names. It gives you application IDs, so map those to the actual services and owners. Then compare them with EwsAllowedAppIDs in Get-OrganizationConfig.

Pay special attention to infrequent jobs. The Microsoft-generated allow list described in the source material was based on 60 days of activity, so a quarterly backup or report could be missing. Check schedules and vendor documentation as well as recent usage.

8f~quartzspanner_417:

That also means an empty recent report isn't proof that nothing depends on EWS. A rarely scheduled job may simply not have run during the reporting window.

Reply to this answer
_q72!parcelhinge.8

Check your tenant's Message Center notices and current Exchange settings before assuming the same switch happened everywhere. The reported rollout distinguishes tenants where EwsEnabled was never set from those with it enabled, and the allow list matters for the latter.

An allow list can be a temporary bridge while you test replacements, not a reason to leave the inventory unfinished. Confirm the current retirement dates and requirements with Microsoft before planning around them.

Reply to this answer
_m4+velvetcog!

Not everyone reported a breakage. Some had already retired dependent systems or prepared ahead of time. There was also a report of mailbox usage graphs going to zero around the rollout, but the cause wasn't established, so I wouldn't assume every coincidental reporting issue is EWS-related.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions