EWS → Microsoft Graph Bridge
Your application keeps speaking EWS SOAP. The bridge performs each call through Microsoft Graph with an app-only token of your tenant and answers exactly like Exchange would — including Exchange error codes.
EWSAllowedAppIDs); after 1 April 2027 EWS access is removed with no way to turn it back on. Exchange Server on-premises is not affected.What the bridge translates today
18 of 96 EWS operations: GetFolder, FindFolder, FindItem, GetItem, GetAttachment, ResolveNames, CreateItem, UpdateItem, DeleteItem, SendItem, MoveItem, CopyItem, MarkAllItemsAsRead, CreateAttachment, DeleteAttachment, GetUserAvailability, GetUserOofSettings, SetUserOofSettings.
Next: SyncFolderItems, SyncFolderHierarchy (synchronization via Graph delta). Everything else answers with a clear EWS error and appears in your coverage report.
Check your traffic first — free
Upload the Microsoft 365 admin center “EWS usage” export, Exchange EWS or IIS logs, or an EWS trace. You get the list of operations your applications call and the share the bridge covers today. Nothing is stored.
How it connects
- Your Microsoft 365 administrator grants admin consent to the “Avakode EWS Bridge” application (Graph application permissions for mail, calendars, contacts and mailbox settings).
- Your application sends EWS requests to the bridge URL with a bridge key instead of the Exchange credential; Autodiscover (POX, JSON and SOAP) points it there.
- The console shows usage and the gap report; mail content is never stored.
Pricing
Tenant
One Microsoft 365 tenant, up to 50,000 requests a month.
Tenant Plus
One Microsoft 365 tenant, up to 500,000 requests a month.
Self-hosted
Run the bridge on your own server (Docker), no tenant limit.
Online checkout opens soon. Already have an Avakode licence key (FRG-…)? Open the console to create your bridge.