Exchange Web Services (EWS) in Exchange Online is fully disabled on April 1, 2027. We fix the price and the delivery date in writing before work starts, and every step lands as its own pull request, or as a patch when we work from a copy of your code. Email us the EWS operations of one app for a free estimate. Or book the $490 audit: every EWS app and script in your tenant, with a fixed quote within 3 business days after we get access.
Book the audit · $490Free estimate for one appTools already stopped working? An admin can switch EWS back on until April 1, 2027 (how). Then fix them for good.
First keep them running: an admin can switch EWS back on until April 1, 2027 (how). Then book the audit with just your EWS usage report and the names of the tools; no code needed. It tells you who has to fix each tool and what your admin does next, and prices a replacement for any tool whose vendor won't move to Microsoft Graph in time.
| Package | What you get | Price |
|---|---|---|
| Complex app | Calendar or contact sync, impersonation across many mailboxes moved to application permissions scoped with RBAC for Applications, streaming or pull notifications moved to Graph change notifications and delta queries, stored EWS item IDs translated, MIME export. | from $2,900 |
| App or service | An app that reads, sends, moves or files mail with attachments, moved from the EWS Managed API to the Microsoft Graph SDK, with tests. | from $1,490 |
| Script or scheduled job | A PowerShell, Python (exchangelib) or scheduled job moved to Microsoft Graph PowerShell or the Graph SDK, signing in with a certificate instead of a password. | from $690 |
| Audit (start here) | Every application in your EWS usage report and every app, script and service account you tell us about: who has to fix each one (Microsoft, a vendor or you); for your own code, each EWS operation mapped to its Graph call, what Graph can't do and the alternative, and the permissions each app needs; and a fixed price and timeline. PDF report within 3 business days after we get access. | $490 |
Only one app? Email us the EWS operations it calls: its rows from your EWS usage report export, or, for C# code, the output of Microsoft's EWS Analyzer. We don't need the code for the estimate, and we reply with a fixed price within 2 business days, free. Want us to read the code instead? Send your NDA first and we sign it, and remove passwords, client secrets and connection strings before you send the code.
Every quote names the price and the delivery date, and we only take work we can finish before April 1, 2027, so the earlier you book, the more room there is. Migrations are invoiced at the fixed price the audit or estimate names. Every change lands as a pull request in your repository, or as a patch when we work from a copy of your code.
Book the audit · $490If your product reaches your customers' Exchange Online through EWS, it stops working in each customer's tenant when Microsoft switches EWS off there, and in every tenant on April 1, 2027. We move the product to Microsoft Graph, priced like the packages above:
Until your Graph version ships, a customer's admin can keep your product on EWS until April 1, 2027 by switching EWS on and adding your application ID to the tenant's EWS allow list (EwsAllowedAppIDs). Setting the list replaces all of it, so the IDs already on it must be included, and a change takes up to 24 hours. Tenants in sovereign clouds such as GCC High, DoD and 21Vianet get their own timeline from Microsoft; tell us if you have customers there. Start with the free estimate: email us the EWS operations your product calls.
A senior .NET engineer with 18+ years in C#, ASP.NET and enterprise integrations, holding 16 Microsoft certifications. AI-assisted tooling handles the mechanical edits, as Microsoft's own migration tutorial recommends; the engineer reviews and tests every change. That keeps the price fixed and the timeline short.
Until April 1, 2027, yes. A tenant admin can do it in the Microsoft 365 admin center (Baseline security mode) or with Set-OrganizationConfig -EWSEnabled $true (Microsoft's steps). It usually takes effect within an hour, four at most. Since October 2026 that lets through only the apps on the tenant's EWS allow list (EwsAllowedAppIDs), and an empty list lets nothing through. If Microsoft switched EWS off for you, it built that list from the previous 60 days of usage, so a tool that calls EWS rarely can be missing; check it with Get-OrganizationConfig -RetrieveEwsOperationAccessPolicy | Fl EwsAllowedAppIDs. Setting the list replaces all of it, so include the IDs already on it; a change takes up to 24 hours. Microsoft also documents Set-OrganizationConfig -EWSEnabled $null (Exchange Online PowerShell), which ignores the allow list and lets every app use EWS again until the final shutdown. On April 1, 2027 the switch goes away for every tenant, and Microsoft says there will be no exceptions.
Mailboxes that stay on Exchange Server keep EWS: Microsoft is not retiring it there. Three setups are affected anyway (Exchange Team). Hybrid: free/busy and MailTips between on-premises and Exchange Online users need Exchange Server SE with the May 2026 update or later, which uses Microsoft Graph; until April 1, 2027 they also keep working over EWS if the tenant keeps EWS on with your Exchange hybrid app on its allow list. On-premises mailboxes with archives in Exchange Online: for now, keep EWS on in the tenant with the hybrid app on the allow list; Microsoft says Graph support for that case is coming. And if your Exchange Server shares free/busy with another company's Exchange Online through an organization relationship, that company's tenant must keep EWS on. Any mailbox you move to Exchange Online loses EWS.
No. You create the app registration and grant consent in your tenant, limited to the mailboxes the app needs. We build and test against a test mailbox, and production secrets stay with you.
The audit names it and proposes the alternative before any work starts, for example a shared mailbox instead of a public folder, or Microsoft Purview eDiscovery instead of a discovery mailbox.
We can't change a vendor's code: the fix for good is the vendor's version that uses Microsoft Graph. The audit names every application ID in your EWS usage report as a Microsoft app, a vendor product or your own code, and for each vendor product checks the vendor's published documentation for a Graph version and the steps your admin takes to switch. If a vendor is gone or won't update in time, the audit prices a replacement built on Microsoft Graph.
Yes, before we get access to code or data.
For drafting, yes: we use AI tools, including Anthropic's Claude. If your NDA or policy rules that out, tell us before you send anything, and your code stays off third-party AI services. Apart from that, we share your code with no one, and we delete our copy when you accept the delivery.