SaaS
Amazon Web Services
AWS is ending support for Amazon WorkMail, its managed business email and calendar service. WorkMail stops accepting new customers on 30 April 2026, and on 31 March 2027 existing customers can no longer use it or access the WorkMail console and resources. AWS points customers to third-party email services and a mailbox export path.
departs 31 Mar 2027
Quick answers
- Is it true that Amazon WorkMail end of support — the managed email and calendar service shuts down 31 March 2027?
- Yes. Amazon Web Services has officially announced it, effective 31 Mar 2027. Amazon WorkMail is AWS's managed business email and calendar service — Exchange-compatible mailboxes hosted in AWS, reachable over IMAP/SMTP, Outlook, the WorkMail web client, and Exchange ActiveSync, often wired into an AWS Directory Service or Microsoft AD setup.
- When does it take effect?
- 31 Mar 2027. Verified against the vendor's own announcement.
- What should I use instead?
- Plan a mailbox migration off WorkMail well before 31 March 2027, and note the earlier 30 April 2026 date if you were counting on creating new WorkMail organizations — after it, you cannot.
What this means for you
Amazon WorkMail is AWS's managed business email and calendar service — Exchange-compatible mailboxes hosted in AWS, reachable over IMAP/SMTP, Outlook, the WorkMail web client, and Exchange ActiveSync, often wired into an AWS Directory Service or Microsoft AD setup. AWS is shutting it down. On its official end-of-support page AWS says the decision is "effective March 31, 2027", that WorkMail "will no longer accept new customers beginning April 30, 2026", and that existing customers who signed up before that date can keep using it until the end date — after which "you will no longer be able to use Amazon WorkMail" or access the WorkMail console and resources. This is a full service retirement, not a version bump: organizations that run their company mailboxes on WorkMail need to migrate every mailbox to another provider and cut over MX/mail routing before the cutoff, or lose access to their mail. Two dates matter — 30 April 2026 (no new organizations or accounts can be created on WorkMail) and 31 March 2027 (the hard end for everyone). The exposure is anything that depends on WorkMail: user and resource mailboxes, calendar data, any application that sends or reads mail through the WorkMail Message Flow or WorkMail APIs, and automation built on the WorkMail SDK/CLI.
Where to go
Plan a mailbox migration off WorkMail well before 31 March 2027, and note the earlier 30 April 2026 date if you were counting on creating new WorkMail organizations — after it, you cannot. AWS recommends moving to third-party email services and names Kopano Cloud, Zoho Mail, and Zoom Mail as comparable options "with tooling for easy migration", while noting you can also move to any other in-market solution (Microsoft 365 and Google Workspace being the obvious mainstream choices). Export first: AWS points to its mailbox export guide so you can pull each mailbox's content out before the service goes away. The practical sequence is to stand up the new email platform, migrate mailboxes and calendars, repoint your domain's MX (and SPF/DKIM/DMARC) records, and then decommission WorkMail. If you have code or automation on the WorkMail APIs — for example the WorkMail Message Flow used to intercept or process inbound and outbound mail — retarget that to the new provider's equivalent (or to SES for programmatic sending) as part of the move.
- Kopano Cloud, Zoho Mail, or Zoom Mail — the third-party services AWS names as comparable, with migration tooling
- Microsoft 365 or Google Workspace — mainstream managed email/calendar suites to migrate mailboxes to
- Amazon SES — for the programmatic email-sending piece if you only used WorkMail's APIs to send mail
Amazon WorkMail — AWS’s managed business email and calendar service — is being shut down. On its official end-of-support page, AWS says it “decided to end support for Amazon WorkMail, effective March 31, 2027.” Two dates bracket the wind-down:
- 30 April 2026 — WorkMail stops accepting new customers. After this, you can’t create new WorkMail organizations.
- 31 March 2027 — the hard end. Existing customers can use WorkMail until this date; after it, per AWS, “you will no longer be able to use Amazon WorkMail,” including the console and your WorkMail resources.
Who this hits
WorkMail runs company mailboxes for organizations that wanted Exchange-compatible email inside AWS — reachable over Outlook, IMAP/SMTP, the web client, and ActiveSync, often tied into AWS Directory Service. This is a full service retirement, so every one of those mailboxes has to move. The exposure is your users’ and resources’ mail and calendars, plus any application built on the WorkMail APIs — notably WorkMail Message Flow, used to intercept and process inbound/outbound mail — and any automation on the WorkMail SDK or CLI.
What to move to
AWS recommends migrating to a third-party email service and names Kopano Cloud, Zoho Mail, and Zoom Mail as comparable options with migration tooling; you can equally move to a mainstream suite like Microsoft 365 or Google Workspace. AWS also points to its mailbox export guide — export each mailbox’s content before the service goes away.
The practical order of operations: stand up the new platform, migrate mailboxes and calendars, repoint your domain’s MX (and SPF/DKIM/DMARC) records, then decommission WorkMail. If you only used WorkMail’s APIs to send mail programmatically, Amazon SES covers that piece.
This entry tracks AWS’s official end-of-support page; if AWS changes either date or the guidance, the entry will be updated with a changelog note.
Entry changelog
- — last reviewed.
- — Entry created from AWS's official end-of-support page in the Amazon WorkMail Administrator Guide. Two dates recorded exactly as stated: no new customers from 30 April 2026, and full end of support / loss of access on 31 March 2027 (recorded as the sunset date). Recommended alternatives (Kopano Cloud, Zoho Mail, Zoom Mail) and the mailbox export path taken directly from the page. Detectable via the AWS SDK v3 per-service npm clients @aws-sdk/client-workmail and @aws-sdk/client-workmailmessageflow — precise package names that only appear in code using WorkMail's APIs (boto3 has no per-service package, so no pypi fingerprint; a bare text:workmail literal would be too generic to be safe). Archive backfill toward depth (former B-081).
Put this countdown in your README
Building on Amazon Web Services? Drop this badge into a project’s README or docs — it shows the days left and
refreshes on its own every night from this page. 
[](https://lastcall.dev/entries/amazon-workmail-end-of-support)Spot an error or a changed date? Tell us and it’s corrected the same night.