Mailbox data goes straight to Microsoft
Sunsetless EWS runs inside your product and calls Microsoft Graph directly. Mail, tokens and credentials never reach Sunsetless servers.
Your customers’ tenants lose EWS one by one between October 2026 and April 1, 2027. We make the change in your product for a fixed price after a free check, or you swap the EWS Managed API package for Sunsetless EWS yourself. With Sunsetless EWS the same build calls Microsoft Graph for customers on Exchange Online and EWS for customers on Exchange Server.
For .NET products built on the EWS Managed API or its .NET Standard port. See the ISV license
Sunsetless EWS is a build of the EWS Managed API that routes each call by the host in the service URL. Calls to outlook.office365.com and outlook.office.com are translated to Microsoft Graph inside your process. Calls to any other host go out as EWS, unchanged.
A customer in the middle of a migration, with mailboxes on both, gets both from the same code. The list of hosts is a setting, and another setting switches the translation off, which helps when you compare the two paths in a test.
service.Url = new Uri( "https://outlook.office365.com/EWS/Exchange.asmx"); service.FindItems(WellKnownFolderName.Inbox, view); // runs on Microsoft Graph
service.Url = new Uri( "https://mail.contoso.com/EWS/Exchange.asmx"); service.FindItems(WellKnownFolderName.Inbox, view); // stays on EWS
The build that talks to Graph has to reach each customer before Microsoft switches EWS off in that customer’s tenant.
A product with customers on Exchange Online and on Exchange Server needs Microsoft Graph for one group and EWS for the other.
| What matters | Two integrations | Graph only | Sunsetless EWS |
|---|---|---|---|
| What you build | A Graph integration next to the EWS one, and an interface both satisfy. | A Graph integration that replaces the EWS one. | Nothing new. You swap one NuGet package, and the library sends each call to Graph or to EWS. |
| Customers on Exchange Server | Keep EWS through the old integration. | Lose the integration, or stay on your last EWS version. | Keep EWS from the same build. |
| Every later feature or fix | Built and tested twice. The two sides differ in details: meetings, sending, search and stored IDs. | Built once, for Exchange Online only. | Built once, against the EWS Managed API your code already uses. |
| Proof that behavior did not change | Your own comparison tests, written while EWS still answers. | Your own comparison tests, and after April 1, 2027 nothing is left to compare with. | Recorded comparisons with live EWS, field by field, run on every build. The differences are published. |
| What it costs | Developer time for the second integration, then for every change on both sides. | Developer time for the rewrite, and the loss of the integration for your customers on Exchange Server. | $3,590, paid once, for the ISV license, plus the time to test your product. |
Microsoft.Exchange.WebServices with Sunsetless.Ews, or the .NET Standard port with Sunsetless.Ews.NETStandard, and rebuild. Your code compiles unchanged.SunsetlessEws.Configure(service, options) when one process serves many customers.The getting started guide lists the permissions by feature.
Put the Graph consent into your upgrade notes early. In a large organization it can take longer than the upgrade itself.
ExchangeService gets its customer’s tenant in code, with SunsetlessEws.Configure(service, options). Services of one tenant share a sign-in and its token cache.Every area is marked as verified, verified with differences, or not possible in Microsoft Graph. Public folders and online archives in Exchange Online have no Graph API, whichever route you take.
The same library as every other license, for a product you ship to your customers.
The ISV license also covers a component or SDK that other developers build on, for example a mail library that exposes EWS types in its own API.
SunsetlessEws.UseComponentLicense(key). The call switches nothing to Microsoft Graph: code with no tenant configured keeps using EWS.If you need terms this license does not cover, for example access to the source code, write to us.
Sunsetless EWS runs inside your product and calls Microsoft Graph directly. Mail, tokens and credentials never reach Sunsetless servers.
The key is checked offline, before the first call to Exchange Online. The library sends nothing to us.
The app registration, its Graph permissions and its mailbox scope live in the customer’s tenant, where its administrators can review and revoke them.
The getting started guide lists each Graph permission with what it is for, so your documentation can ask for only what your product needs.
Send us the product’s EWS usage report, or tell us what it does with mailboxes, and we check it for free. Then, for a fixed price from $1,000, we rewrite its EWS code for Microsoft Graph, or swap the package and set up the configuration, and test its calls against Exchange Online in our own tenant. After the swap, the product needs the ISV license.
We need no access to your servers or to your customers’ tenants. NDA on request.
Tell us what the product does and we quote a fixed price for the change. Or run it on a free trial key in your own tenant.