EWS retirement: what the end of Exchange Web Services means for your booking system
10 min
EWS retirement: the key points
Microsoft has been disabling Exchange Web Services (EWS) in Exchange Online since October 2026. From April 1, 2027, it's permanently off there, and Microsoft says there will be no exceptions.
Exchange Online is affected. Microsoft isn't changing EWS in Exchange Server, but it does call out two hybrid edge cases.
Booking tools that read or write over EWS lose their sync. Room calendars, door displays, and Outlook add-ins end up with stale data or none.
The EWS usage report in the Microsoft 365 admin center helps you check. It lists apps with successful EWS calls over the last 7, 30, or 90 days.
For Exchange Online, Microsoft recommends migrating to Microsoft Graph.
The anny booking system connects to Exchange Online through Microsoft Graph and to on-premises Exchange through its own sync service.
What Microsoft is turning off, and when
EWS is the older SOAP interface apps use to reach mailboxes and calendars. Room booking systems and door signs may be connected through it too. Microsoft announced the end for Exchange Online in 2023 and published the detailed timeline in 2026:
When | What happens |
|---|---|
Since October 2026, tenants with no EWS setting of their own | Microsoft posts a Message Center warning seven days ahead, adds apps used in the last 60 days to the allow list (EWSAllowedAppIDs), then turns EWS off. |
Since October 2026, tenants with EWS explicitly on | Microsoft filled the allow list on October 10–11 and won't change anything until April 2027. |
Until April 1, 2027 | Admins can temporarily turn EWS back on with EWSEnabled. Any admin who turns it on after October 11 has to fill in the allow list themselves. |
From April 1, 2027 | EWS is permanently off in Exchange Online. |
This schedule covers the worldwide cloud. Microsoft says a separate timeline for sovereign clouds will follow (Microsoft Exchange Team). On the end date, Microsoft writes: “There will be no exceptions past April 2027” (Microsoft Exchange Team). The allow list only buys you a few months.
Two scenarios also affect organizations running Exchange locally (Microsoft Exchange Team):
Hybrid with online archives. If on-premises mailboxes keep their archive in Exchange Online, EWS has to stay on there for now. Microsoft says this problem doesn't apply without on-premises mailboxes or without online archives.
Calendar sharing with another organization. If a purely on-premises Exchange shares free/busy data with a separate Exchange Online organization, that organization has to keep EWS on until Microsoft offers a solution without it.
Hybrid coexistence also requires Exchange SE with at least the May 2026 update.
What fails in room and desk booking
A room booking system syncs with Exchange constantly. It reads who booked a room in Outlook and writes its own bookings back to the room calendar. If that runs over EWS and EWS goes away, you get this:
A booking made in Outlook never reaches the booking tool, or the other way around, and two teams show up at the same door.
The door display says “free” while the calendar shows a meeting.
The tool releases a room after a missed check-in, but Outlook still shows it as taken.
Outlook add-ins that rely on EWS stop working. Microsoft lists them among the affected apps (Microsoft Exchange Team).
Utilization reports built on room calendars get no new data.
If your tool has already stopped working
Search the Message Center for “EWS will be disabled in your tenant in 7 days” or “EWS has been disabled in your tenant.” In Exchange Online PowerShell, Get-OrganizationConfig | Fl EWSEnabled shows the status. If it says False, Set-OrganizationConfig -EWSEnabled $true turns EWS back on. That usually takes effect in under an hour, and in rare cases up to four. You can also do it in the admin center through Baseline Security Mode (Microsoft Exchange Team).
Allow list changes take 24 hours. Adding apps with Set-OrganizationConfig -EwsAllowedAppIDs replaces the whole existing list (Microsoft Exchange Team). All of this only works until April 2027.
How to check if your booking tool is affected
You'll need admin access to the Microsoft 365 admin center or Exchange Online PowerShell.
Open the EWS usage report: admin center → Reports → Usage → Exchange → EWS usage. For each Application ID, it shows SOAP actions and the number of successful calls. Set the period to 90 days, and keep in mind the data can lag by up to 10 days (Microsoft Learn).
Identify unknown IDs. Look up each Application ID under Enterprise applications in Microsoft Entra to find the vendor.
Check the allow list. Get-OrganizationConfig -RetrieveEwsOperationAccessPolicy | Format-List EwsAllowedAppIDs shows which apps are on it. If Microsoft filled it, those are the apps from the last 60 days (Microsoft Exchange Team). Rarely used tools can be missing from the report, so check both.
Remember Microsoft's own apps. If they appear in the report, they also need to be on the allow list while they still use EWS (Microsoft Exchange Team).
Ask your vendor: Do you use only Microsoft Graph for Exchange Online, and since when? Do you support on-premises Exchange, and how?
If your room booking or display vendor is in the report, sort out the switch as soon as you can. If EWS goes off in your tenant before April, you won't have much time.
Room booking and Exchange: migrating to Microsoft Graph
Microsoft's advice for Exchange Online is clear: “we strongly suggest migrating to Microsoft Graph” (Microsoft Exchange Team). Your vendor usually does the actual work. What you do depends on their answer:
Vendor's answer | What you do |
|---|---|
Already on Graph | Get it in writing and confirm the app disappears from the EWS usage report. |
Still moving | Get a date, keep the app on the allow list until then, and schedule the update before April 2027. |
No plan or no answer | Start looking for another tool now. After April 2027, there's no way back. |
After the switch, a simple test will do: book one room in Outlook and one in the tool, then check that both sides show them as taken.
The main change for your IT team is sign-in. Graph integrations authenticate with OAuth through a registered app, and an admin grants permissions centrally. In Exchange Online you can limit an app's calendar permissions to specific mailboxes, for example with RBAC for Applications. For a booking tool, the room mailboxes are the obvious scope.
Two technical details are worth raising with your vendor. A delta query for calendars without a fixed date range is still beta-only in Graph. And change notifications for Outlook events expire in under seven days, so the app has to keep renewing them.
Microsoft's roadmap shows which EWS features are still moving to Graph. If something isn't listed, Microsoft says not to expect it in Graph before EWS ends (Microsoft Learn).
On-premises Exchange: EWS stays, and Graph can't help
For local servers, Microsoft writes: “there are no changes to EWS in Exchange Server” (Microsoft Exchange Team). If you run Exchange Server in your own data center, you keep EWS.
That's awkward for cloud tools. Graph reaches mailboxes in Exchange Online, and Microsoft ended the older REST option for hybrid deployments in July 2023 (Microsoft Learn). A booking tool that only speaks Graph can't reach a purely on-premises Exchange. This mostly affects public agencies, universities, and hospitals with their own IT, so ask every vendor about it directly.
We've lost projects over this ourselves. Public agencies on local Exchange and classic Outlook wanted room booking in their calendars, and we couldn't connect them. So we built the connection.
How anny connects to your Exchange
anny is a booking system for rooms, desks, parking, vehicles, and visitors. How the calendar connection works depends on where your Exchange runs.
Exchange Online through Microsoft Graph
anny's Microsoft 365 integration only uses Microsoft Graph, so the EWS retirement doesn't affect it. anny signs in as an app with admin consent, reads and writes room calendars, and responds to changes. If you want, anny can anonymize event titles in the calendar.
On-premises Exchange through the anny sync service
For Exchange Server, anny runs its own sync service, designed for the current version, Exchange Server SE. If you're on an older version, talk to us first.
The service reaches your Exchange server over EWS via HTTPS on port 443, from fixed anny IP addresses that you allow in your firewall. Your Exchange has to be reachable from those addresses. It doesn't open any connection to anny itself.
For access, you create a service account with the ApplicationImpersonation role for the room mailboxes. anny stores the credentials encrypted in a dedicated vault. Setup runs through a wizard: you enter the details, anny checks them right away against a test mailbox, and you pick the rooms. anny finds the server through Autodiscover, or you can enter the URL by hand.
Sync goes both ways. A booking in anny appears as an event in the room calendar, and an Outlook event blocks the room in anny. Changes arrive through streaming notifications, and a regular full reconcile catches anything that slipped through.
The sync service has these limits:
It only syncs room and resource calendars, not personal calendars, email, or contacts.
This version doesn't sync recurring meetings with complex exceptions yet.
It can't connect a network that's fully cut off from the internet.
What else you get
anny manages rooms, desks, parking, EV chargers, pool cars, and visitors in one system. See room booking with anny. Booking rules let you limit how often one person can book the same desk each week (Professional plan and up). Communities hold rooms and desks for specific teams. You set your own deletion periods, and anny is developed and hosted in Germany.
Checklist: EWS retirement for IT and facilities
Review the EWS usage report for 90 days, and check the allow list.
Match every app ID to a vendor, including door displays, visitor management, and calendar tools.
Get each vendor's answer in writing: are they on Graph for Exchange Online, and since or from when?
For on-premises Exchange, ask which firewall rules and service account the vendor needs.
Check whether either hybrid scenario applies to you.
Treat the allow list as a bridge, and finish your migration by March 2027 at the latest.
If a new booking tool is coming, bring in facilities and your works council early.
Want to see how anny connects your rooms to Exchange? Book a demo or start for free.
Frequently asked questions
When is Microsoft turning off EWS?
Microsoft has been disabling EWS in Exchange Online step by step since October 2026. From April 1, 2027, it's permanently off there, and Microsoft says there will be no exceptions.
Is on-premises Exchange affected by the EWS retirement?
Mostly no. Microsoft isn't changing EWS in Exchange Server. It does name two special cases: hybrid setups with on-premises mailboxes and online archives, and on-premises organizations that share calendars with a separate Exchange Online organization.
How do I know if my room booking system uses EWS?
In the Microsoft 365 admin center, go to Reports → Usage → Exchange → EWS usage. The report shows apps with successful EWS calls over the last 7, 30, or 90 days. Check the allow list too, and ask your vendor.
Can I turn EWS back on after April 2027?
No. Until April 1, 2027, admins can temporarily turn EWS back on with EWSEnabled and an allow list. Microsoft says that won't be possible after that date.
How does anny connect to Exchange?
The anny booking system connects to Exchange Online through Microsoft Graph and to on-premises Exchange through its own sync service. The service syncs room and resource calendars in both directions.
Sources
As of November 8, 2026.
Microsoft Exchange Team: Retirement of Exchange Web Services in Exchange Online
Microsoft Exchange Team: Exchange Online EWS, your time is almost up
Microsoft Exchange Team: EWS deprecation is here – what this means to you
Microsoft Exchange Team: Exchange Online EWS application stopped working? Do this
Microsoft Exchange Team: Introducing EWSAllowedAppIDs
Microsoft Exchange Team: Impact of Exchange Online EWS deprecation on hybrid rich coexistence
Microsoft Learn: Deprecation of EWS in Exchange Online
Microsoft Learn: EWS usage report
Microsoft Learn: Microsoft Graph and hybrid deployments
Microsoft Learn: Delta query for events
Microsoft Learn: Change notifications overview
Microsoft Learn: RBAC for Applications in Exchange Online




