Cybersecurity · 6 min read · 20 November 2026

Microsoft EWS Ends April 2027: Monaco

Microsoft is shutting down Exchange Web Services in Microsoft 365 by 1 April 2027. What Monaco businesses should check in CRMs, backups and calendar tools.

Microsoft EWS Ends April 2027: Monaco

Microsoft is retiring Exchange Web Services (EWS) in Exchange Online, the email and calendar engine behind Microsoft 365. Phased switch-off started on or soon after 1 October 2026, tenant by tenant. On 1 April 2027, Microsoft says EWS will be permanently disabled, with no exceptions.

Most users won't notice anything. But many of the tools a Monaco business connects to its mailboxes do rely on EWS: CRM email sync, calendar and booking integrations, mailbox backup and archiving products, migration utilities and older custom scripts. When EWS goes, these integrations stop syncing. Often nothing shows an error, so the first sign is an empty CRM timeline or a backup that hasn't run since spring.

You have about four months. For most businesses the fix is a short inventory and one or two conversations with vendors.

What Microsoft is changing, and when

EWS is a long-standing way for software to read and write mail, calendars and contacts in Exchange. It has had no new features since 2018, and Microsoft's replacement is Microsoft Graph. Microsoft's Exchange team has published the timeline, revised several times during 2026:

  • From 1 October 2026: staged disablement. Tenants still on the default setting are being switched to "EWS off" on or soon after that date, tenant by tenant.
  • Until 1 April 2027: administrators can still turn EWS back on and use an allow list of approved applications (the EWSEnabled and EWSAllowedAppIDs settings). Microsoft has also said it may build an allow list automatically from a tenant's recent usage if the tenant hasn't set one up.
  • 1 April 2027: EWS is permanently disabled in Exchange Online. The admin setting goes away.

Some independent Microsoft 365 specialists expect the final removal to run into May 2027, and Microsoft's own wording has changed over the year. Plan around 1 April, and check the latest notice in your Microsoft 365 admin centre's Message centre.

This applies only to Exchange Online (Microsoft 365). Businesses that still run their own on-premises Exchange Server are not affected by this retirement. Hybrid setups are more complicated and need an IT specialist to review them.

Why this matters for Monaco businesses

Microsoft 365 is the default office suite in the Principality. Family offices, fiduciaries, yacht brokers, real estate agencies, law firms and hotels mostly run on Outlook and Exchange Online. Very often a provider set it up years ago and nobody has reviewed it since.

Integrations are where the value sits. In a relationship-driven market, the CRM record of every email with a client, the property viewing that lands in a broker's calendar, and the archived correspondence you keep for compliance are business assets. Connectors built years ago, or by a small vendor, are the most likely to still use EWS.

Record-keeping obligations don't pause. Regulated activities in Monaco, including those subject to anti-money-laundering rules, generally require you to keep certain records. Personal data must also be handled securely under Law No. 1.565 of 3 December 2024, supervised by the APDP. If an email archive or backup tool quietly stops capturing mail, you may not be able to produce correspondence when asked. Which records you must keep, and for how long, depends on your activity, so check with your compliance officer or legal adviser. Our APDP data protection page covers the data-protection side.

The tools most likely to be affected

Microsoft has said its own apps are migrated or nearly done. The risk is mostly third-party and custom software. Check:

  • CRM email and calendar sync: older connectors for HubSpot, Salesforce, Pipedrive, Zoho or sector-specific CRMs for real estate, yachting or wealth management
  • Booking and scheduling tools that read or write Outlook calendars, including some room and resource booking systems
  • Mailbox backup and email archiving products, especially older or on-premises installs
  • Migration and import/export utilities used to move mailboxes between providers
  • Custom scripts and automations written in-house or by a former IT provider, for example to file attachments, read invoices from a mailbox or create calendar events
  • Older email clients or add-ins that you haven't updated in years

What is not in scope: website contact forms that send through SMTP are a separate issue, covered in our article on the Microsoft 365 SMTP cut-off. It's worth checking both at the same time.

How to find out if you are exposed

  1. Open the EWS usage report. In the Microsoft 365 admin centre, Microsoft provides a usage report showing which applications have been calling EWS in your tenant. It is the quickest way to get a factual list.
  2. Check your current setting. Your administrator can see whether EWS is already off, on with an allow list, or still on the default. If something broke in October or November and nobody knew why, this may be the cause.
  3. Ask each vendor one question: "Does your Microsoft 365 integration use Microsoft Graph, and is it fully off EWS before 1 April 2027?" Get the answer in writing.
  4. List anything custom. Scripts and automations built for you by a past provider usually have no vendor to call. Identify them now so they can be rebuilt.

What to do about it

Update or reconnect integrations. Most established vendors have moved to Graph already. Often you only need to update the connector or re-authorise it with the new method. Do this in a quiet week, not the last week of March.

Rebuild custom automations on Graph. A script that files attachments or syncs a calendar can usually be rebuilt cleanly on Microsoft Graph or a supported automation platform. It is also a chance to add proper logging so you know when something stops. Our AI automation team builds and maintains this kind of workflow.

Replace tools that won't migrate. If a vendor has no Graph roadmap, treat 1 April 2027 as that product's end date and choose a replacement with time to move your data properly. For CRM changes, our email marketing & CRM work includes migration and sync setup.

Don't rely on the allow list. Re-enabling EWS for specific apps buys time until April, and nothing more.

A sensible timetable

  • Before Christmas: run the usage report, confirm your tenant setting, and send the vendor question.
  • January–February 2027: update connectors, rebuild custom scripts, and test that CRM timelines, calendars and backups are capturing new data.
  • March 2027: turn off any temporary EWS allow-list entries yourself, before Microsoft does, and confirm everything still works.
  • Ongoing: add "integrations still syncing?" to your monthly IT and website maintenance checklist.

Not sure which of your tools still depend on EWS? Get in touch and we'll help you map your Microsoft 365 integrations and plan the changes before April 2027.

microsoft 365exchange onlinecrmitmonaco

BSS Digital Agency

Digital agency based in Monaco. Web, apps, AI, marketing.

Get in touch