Keep your product’s EWS integration working for every customer

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

Runs on
.NET Framework 3.5 to 4.8 and .NET 8, 9 and 10
Works with
Exchange Online and Exchange Server
Tested
212 scenarios compared with live EWS

One build for customers on Exchange Online and on Exchange Server

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.

One code base for Exchange Server and Exchange Online

MailboxSync.cs
Customer A: mailboxes in Exchange Online
service.Url = new Uri(
    "https://outlook.office365.com/EWS/Exchange.asmx");
service.FindItems(WellKnownFolderName.Inbox, view);
// runs on Microsoft Graph
Customer B: mailboxes on Exchange Server
service.Url = new Uri(
    "https://mail.contoso.com/EWS/Exchange.asmx");
service.FindItems(WellKnownFolderName.Inbox, view);
// stays on EWS

Each customer tenant loses EWS on its own date

The build that talks to Graph has to reach each customer before Microsoft switches EWS off in that customer’s tenant.

October 10, 2026
In a Worldwide tenant with EWSEnabled set to True, an application that is not on the EWSAllowedAppIDs list loses EWS. Where Microsoft filled the list itself, it used 60 days of usage, so a product that calls EWS less often can be missing from it.
Second phase, from October 2026
Tenants that never set EWSEnabled are switched off in waves, each with a 7-day warning in Message Center. EWS then stays off for every application until an administrator turns it back on.
April 1, 2027
EWS in Exchange Online is retired, with no exceptions for any tenant. Exchange Server keeps it.

Three ways to serve both kinds of customers

A product with customers on Exchange Online and on Exchange Server needs Microsoft Graph for one group and EWS for the other.

Three ways to serve both kinds of customers
What mattersTwo integrationsGraph onlySunsetless EWS
What you buildA 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 ServerKeep 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 fixBuilt 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 changeYour 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 costsDeveloper 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.

What changes in your product, and what your customers do

What you do, once

  1. Replace Microsoft.Exchange.WebServices with Sunsetless.Ews, or the .NET Standard port with Sunsetless.Ews.NETStandard, and rebuild. Your code compiles unchanged.
  2. Put your ISV key into the product, in its configuration or in code. The same key serves every customer.
  3. Give the library each customer’s tenant ID, client ID and certificate or client secret: in the settings of an installed product, or in code with SunsetlessEws.Configure(service, options) when one process serves many customers.
  4. Test with a free trial key in your own tenant, then release.

What each customer does

  • A customer on Exchange Online registers an app in Microsoft Entra ID, or consents to yours, and grants it the Microsoft Graph application permissions your product needs.
  • Its administrators can limit the app to the mailboxes your product uses, with RBAC for Applications in Exchange Online.
  • A customer on Exchange Server changes nothing.
  • Customers buy nothing from us and need no key of their own.

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.

Where your product runs

  • Installed by your customers, on their servers or desktopsEach installation is configured for its customer’s tenant.
  • Hosted by you, one deployment per customerEach deployment has its own configuration.
  • Hosted by you, many customers in one processEach 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.

57 EWS operations covered, and a plain list of the rest

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 ISV license

The same library as every other license, for a product you ship to your customers.

Product
One product of yours, which can be a component or SDK that other developers build on. Each further product needs its own license.
Customers
Any number, each in its own Microsoft 365 tenant. They use the library only through your product, including the EWS types a component exposes, and never on its own.
Redistribution
Royalty-free. You ship the package inside your product and keep our copyright and license notices. Developers who build on your component may ship it, with the library inside, in their own applications.
License key
One key for the product, not tied to a tenant. Right after payment you get a 30-day test key, and from 14 days after the purchase you create the permanent key in your account. It does not expire. Keep it inside your product; a component on a public feed gets a key bound to it.
Developers and servers
No limit on either.
Updates
Every future version, at no extra cost. You pay once and the license never expires.
If development stops
If no release comes out for 12 months, or the business stops trading, every license holder gets the full source code of the latest release under the MIT license.

If your product is a component or SDK

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.

  • Developers who build on your component configure their own tenant, as with any other installation. They buy nothing from us and need no key of their own.
  • For a component anyone can download, such as a package on NuGet.org, send us its name and public key token, and we bind your key to the component’s strong-name key. That key works only inside your component, so it can ship in the package.
  • Your component supplies the key in its own code with SunsetlessEws.UseComponentLicense(key). The call switches nothing to Microsoft Graph: code with no tenant configured keeps using EWS.
  • The component has to be your own product, with a purpose of its own. A thin wrapper whose main value is the library is not covered.

If you need terms this license does not cover, for example access to the source code, write to us.

For your customers’ security review

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.

No telemetry and no license server

The key is checked offline, before the first call to Exchange Online. The library sends nothing to us.

The customer keeps control

The app registration, its Graph permissions and its mailbox scope live in the customer’s tenant, where its administrators can review and revoke them.

Only the permissions you use

The getting started guide lists each Graph permission with what it is for, so your documentation can ask for only what your product needs.

Security and data flow in detail

We can make the change in your product

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.

Questions from software vendors

Do our customers need to buy anything from you?
No. The ISV license covers every customer that uses your product, including developers who build on your component or SDK. They need no key and no account with us.
Do we need a key for each customer?
No. Your product carries one ISV key, which works in any tenant. The tenant each installation or each service signs in to comes from your own settings.
Does it work with the .NET Standard port of the EWS Managed API?
Yes. Sunsetless.Ews.NETStandard replaces Microsoft.Exchange.WebServices.NETStandard, and your await calls stay as they are. The same license key works with both packages.
Our product still targets .NET Framework 3.5, 4.0 or 4.5. Does it work?
Yes. For those targets Sunsetless.Ews is a single Microsoft.Exchange.WebServices.dll with no dependencies. Calls to Exchange Online need .NET Framework 4.7.2 or newer on the computer, and an application built for .NET Framework 3.5 has to run on the .NET Framework 4 runtime. Calls to Exchange Server work without either.
Do we pay again for later versions?
No. The license is a one-time payment and never expires, and every future version works with your key. There is no subscription or renewal fee.
Can we test it with our product before we buy?
Yes. A free trial key runs the full library in one tenant for 14 days, which is enough for your own test tenant. After you buy, a 30-day test key works in any tenant, and every license has a 14-day money-back guarantee.
What if our product calls something Microsoft Graph cannot do?
That call returns an EWS error that names the operation; the library never returns partial data silently. Run your EWS usage report through the checker on this site to see which of your calls are covered.
We have two products that use EWS. Is one license enough?
No. An ISV license covers one product, so each product needs its own.
Can we pay by invoice or purchase order?
Paddle, our reseller, takes the payment and sends the invoice. For a quote or a purchase order, write to [email protected].

Get the Graph build to your customers before Microsoft switches EWS off in their tenants.

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.