Migrating from an existing Symbee Connect Email Setup that used Amazon WorkMail

Earlier versions of Symbee Connect Email used Amazon WorkMail as an intermediate destination for inbound email. Customers configured their existing email provider to forward messages from selected mailboxes to corresponding Amazon WorkMail addresses, which then passed the messages to Amazon SES for processing by Symbee Connect.

Support for Amazon WorkMail

AWS is ending support for Amazon WorkMail. For customers currently using Amazon WorkMail, you will no longer be able to access the Amazon WorkMail console after March 31 2027. Refer to the official AWS WorkMail end of support notice here: Amazon WorkMail end of support

Symbee Connect will continue to support existing Amazon WorkMail-based configurations until AWS ends support for Amazon WorkMail. However, all Symbee Connect Email functionality has been updated to operate without Amazon WorkMail.

The updated email architecture eliminates the dependency on Amazon WorkMail. Instead, your existing email provider forwards messages to a dedicated email routing domain and routes them directly to Amazon SES using an SMTP connector or equivalent mail-routing configuration.

All Email Channel documentation in this portal has been updated to reflect these changes. For an overview of the new architecture and email flow, refer to How Symbee Connect Email Works. The Email Channel Setup and Configuration step-by-step guide has also been refreshed accordingly.

The remainder of this page provides step-by-step instructions for migrating from the previous WorkMail-based configuration to the new architecture.

This migration does not require replacing your existing public-facing email addresses, or creating any additional mailboxes, updating any MX records, or changing how agents service email in Symbee Connect.


What Changes?

The primary change is how incoming email reaches Amazon SES.

Previous configuration:

Customer Email => Existing Email Provider => Amazon WorkMail => Amazon SES => Symbee Connect

Updated configuration:

Customer Email => Existing Email Provider => Amazon SES => Symbee Connect

Assuming your current email domain is example.com, the updated configuration uses a dedicated routing domain (for example, servicing.example.com) to identify messages being forwarded into Amazon SES.

Your existing email provider continues to receive messages sent to your public-facing addresses (such as support@example.com) and can retain copies in those mailboxes, just as before.

Your existing mailbox Forwarding settings remain enabled. However, the forwarding destination changes from the previous Amazon WorkMail address to an equivalent address on the new routing domain.

In your email provider, SMTP Routing is used to have the messages forwarded into Amazon SES.


Important Considerations

  • Existing outbound email configuration: Your existing public-facing email domain (for example, example.com) should already be verified in Amazon SES for outbound sending. This verification must remain in place to support outbound email authentication (DKIM, DMARC, etc.). Migration Step 2 below includes instructions for confirming this.
  • Email content and compliance: Incoming email continues to be stored and processed within your organization's AWS account. The migration away from using Amazon WorkMail does not require routing any email content through Symbee's cloud infrastructure.
  • Email provider settings: Some email providers (notably Microsoft 365) may require additional configuration to ensure forwarded messages sent via SMTP routing (see Migration Step 3) use standard HTML/MIME formatting (as opposed to proprietary formats). Refer to provider-specific documentation related to this. Specifically for Microsoft 365 refer to Appendix: Microsoft 365 – Email Format Compatibility.
    Additionally (related to Migration Step 3), the exact name or term used to refer to the function of SMTP Routing in each mail provider solution differs, but all major enterprise email provider solutions support the concept. As examples: Microsoft 365 refers to it as Mail Flow Routing implemented using two components - an Outbound Connector to an SMTP Smart Host, and Mail Flow Rules; Google Workspace (Gmail) calls it Gmail Routing, Routing rules, and Mail routes (configured under Hosts);
  • Migration timing: Migration Steps 1 through 5 below can all be performed first, and tested with a testing mailbox if needed, without any impact. Migration Step 6 (updating the public-facing mailbox Forwarding) is the first point where the setup transitions from the previous Amazon WorkMail based routing to the non-WorkMail approach. This allows you to migrate email addresses individually, starting with a single address and switching the remaining addresses once you're satisfied that everything is working correctly. This also provides a simple rollback option: if any issues arise, you can temporarily restore the previous Amazon WorkMail Forwarding destination.
    Delay the cleanup in Migration Step 8 until you've confirmed that the new configuration is working correctly.

Once migration is complete, Amazon WorkMail is no longer required for Symbee Connect Email processing.


Migration Steps

The following steps detail the migration process.

Assuming your current email domain is example.com:

Step 1 - Ensure your Symbee Connect Email Channel CloudFormation stack is up to date.

If your existing Email Channel CloudFormation stack in your AWS Account is not up-to-date, download the latest Symbee Connect Email Channel CloudFormation template from the Administration Portal and perform an update on your existing CloudFormation stack first.

Step 2 - Configure a new dedicated inbound Email Routing Domain as a Verified Identity in Amazon SES.

As discussed in the updated How Email Works sections of the Email Overview, a new dedicated email routing domain, such as servicing.example.com (where example.com is your organization's existing email domain), is used to route inbound email from your public-facing mailbox through your Email Provider to the regional Amazon SES SMTP Endpoint.

Throughout the following migration steps, your Email Routing Domain refers to this.

Notes on this:

  • The use of 'servicing.' in the above example here is only a suggestion - if 'servicing.' is already being used as a subdomain in your DNS environment, choose another unique name, such as 'routing.' or 'contactcenter.'

  • This new Email Routing Domain does not need to actually exist as a publicly accessible domain or independently configured subdomain on the internet. No separate DNS hosted zone, public MX or DMARC records, or actual email mailboxes are required. It is simply a dedicated domain name (string) that will be used internally within your existing Email Provider configuration to identify and route email destined for the Contact Center through to Amazon SES.

    Decide on a unique name for this Email Routing Domain and use that consistently when configuring your Email Provider, Amazon SES, and Symbee Connect.

Follow the below to configure your decided Email Routing Domain in SES as a verified Identity:

  1. Log in to your AWS Management Console and navigate to the Amazon SES console. Make sure you are in the correct AWS Region (top right of the navigation bar) for your existing Email setup.
  2. From the Amazon SES console, select Identities (under Configuration) in the left-hand navigation bar.
  3. Click Create identity in the top-right.

  4. On the Create identity screen, under Identity type, select Domain.

  5. In the resulting fields that appear, in the Domain field, enter the Email Routing Domain you decided on above. For example: servicing.example.com

  6. Under the Verifying your domain section, leave the default Easy DKIM Identity type selection.

  7. Under Advanced DKIM settings, for DKIM signing key length, select RSA_2048_BIT.

  8. Leave the remaining defaults and click Create Identity in the bottom right.

  9. After your domain has been created, you will be in the details page of the domain. It will be in a status of Verification pending. Below the Summary and Recommendations sections, there are a set of tabs - select the Authentication tab.

  10. In the Authentication tab, expand the Publish DNS Settings section, it will list the Name and Value of 3 CNAME records that need to be created/configured in your DNS Provider system.

  11. Log into (or have someone that has access to) your DNS Provider system and add these 3 additional CNAME records under your Primary Domain configuration (you don't need a separate Hosted Zone / subdomain in your DNS for this).

  12. Once the CNAME records have been created in your DNS System, wait for Amazon SES to update its verification status. Eventually Amazon SES should change the domain status to Verified.

Check your Primary Email Domain is also declared as a Verified Identity in Amazon SES

In addition to your Email Routing Domain, your Primary Email Domain (e.g. example.com) must also be configured as a verified identity in Amazon SES. This allows outbound emails and replies to use your organization's actual email domain in their "From:" address.

Your Primary Email Domain was likely verified during the original Email Channel setup. Check it appears in the Amazon SES list of verified identities. If not, follow the same steps above to verify it.

Step 3 - Configure an Outbound SMTP Connector/Route-Path in your Email Provider, over to Amazon SES.

Create an outbound SMTP connector (or equivalent configuration) within your Email Provider solution that delivers/redirects any messages addressed to your Email Routing Domain (see previous step) - for example, 'servicing.example.com' - directly over to the AWS Regional Amazon SES Email Receiving endpoint.

Specifically, the SMTP destination for the messages will be the AWS Regional Amazon SES Email Receiving SMTP Endpoint associated with the same AWS Region you are using Amazon SES in. Refer to Amazon SES documentation here for the exact names of each regional endpoint. For example, if you are using the "us-east-1" AWS Region, you would use "inbound-smtp.us-east-1.amazonaws.com" as the SMTP destination here.

For example, if your Email Provider is Microsoft 365 / Exchange Online, follow the below:

  1. Log in to your Microsoft 365 Admin Center and navigate to Exchange Admin Center.

  2. Select Connectors, under Mail Flow, from the left side navigation menu

  3. Click "+ Add a connector"

  4. On the New connector page:

    • Select Connection from: Office 365
    • Select Connection to: Your organization's email server
  5. On the Connector name page:

    • Give the connector a name: For example "AWS SES Inbound receiving email ([the AWS Region you are using])"
    • Give the connector a description: For example "Send email to the AWS SES receiving email SMTP endpoint in [the AWS Region you are using] region"
    • Leave Turn it on checked
    • Leave Retain internal Exchange headers unchecked
  6. On the Use of connector page:

    • Select: Only when I have a transport rule set up that redirects messages to this connector
  7. On the Routing page:

    • Enter the AWS Regional Amazon SES Email Receiving SMTP Endpoint that you determined from the link above, and click "+". For example: inbound-smtp.us-east-1.amazonaws.com (if you are using the us-east-1 region)
  8. On the Security Restrictions page:

    • Select the Always use Transport Layer Security (TLS)... option
    • And: Issued by a trusted certificate authority (CA)
  9. On the Validation page

    • Note: This validation is expected to fail because you haven't yet duplicated your Email Configurations in Symbee Connect (see Step 4 below). This is normal, but you must still run the validation to proceed with creating the connector.
    • Enter a valid email address to send the test message from (just use your personal email address)
    • Click '+", then Validate
    • The validation process will take a couple of minutes and then fail, but allows you to then progress and save the connector. When it asks if you Are sure you want to proceed after failure anyway, select Yes
  10. On the Review connector page, select Create connector at the bottom, and Done. This completes the creation of the Connector - the remaining actions below establish a Mail Flow Transport Rule that uses this connector...



  11. Still in Exchange Admin Center, select Rules, under Mail Flow, from the left side navigation menu

  12. Click "+ Add a rule"

  13. On the Set rule conditions page of the New transport rule dialog:

    • Give the rule a name: For example "Contact Center - Route all @servicing.example.com email to Amazon SES" or something similarly appropriate for your environment
    • For Apply this rule if:
      • Set The recipient, then domain is,
      • And at the resulting specify domain prompt, set the value to your decided Email Routing Domain. For example: servicing.example.com
    • For Do the following:
      • Set Redirect the message to, then the following connector,
      • And at the resulting select connector prompt, select the connector you just created above.
      • Save, and click Next
  14. On the Set rule settings page:

    • Set Run mode to Enforce
    • Check/enable the Stop processing more rules checkbox
    • Leave all the remaining defaults, and click Next
  15. On Review and finish, click Confirm, and then Finish at the bottom

  16. The new Rule will initially be created in a "Disabled" state - click into the new rule and enable it.

This completes the functionality to route messages for your Email Routing Domain from your Email Provider over to Amazon SES.

Step 4 - Update (duplicate) your Email Configurations in your Symbee Connect Administration Portal.

In your previous Amazon WorkMail setup, incoming email is routed using Email Forwarding from your public-facing mailbox into Amazon SES and through to Symbee Connect using the email address on your Amazon WorkMail domain. For example: support@example.awsapps.com. Therefore your Email Configurations defined in Symbee Connect will be using the WorkMail-based email addresses.

In the new configuration, incoming email will continue to be forwarded from your public-facing mailbox, but will arrive in Amazon SES using an address associated with the new Email Routing Domain established in Step 2. You'll update the forwarding destination in Step 6. To prepare for this, you need to duplicate each WorkMail-based Email Configuration defined in Symbee Connect to the equivalent email address on the Email Routing Domain. For example, you would duplicate the Email Configuration for support@example.awsapps.com to support@servicing.example.com.


  1. Log in to the Symbee Connect Administration Portal.
  2. Click on the Channels menu in the left side navigation bar.
  3. Select Email Configuration located under the Email section.
  4. For each of your Amazon WorkMail based email addresses, complete the following:
    • Select the Amazon WorkMail based email address, and click on the Duplicate Configuration action at the top
    • Complete the Duplicate Email Configuration dialog with the following fields:
      • Email Address: Enter the equivalent email address with the domain part set to your Email Routing Domain. For example: support@servicing.example.com
      • Description: A short description for this new Email Configuration - we suggest, for documentation purposes, the description contains the equivalent public-facing email address (e.g. support@example.com) this Configuration relates to.
    • Click Save.

Nothing else needs to change on the new duplicated Configurations. The Outbound Email Address on each new duplicated configuration will be copied over, and should remain set to the true public-facing outbound From address (e.g. support@example.com) so that replies and new outbound emails continue to use the familiar public-facing address.

Step 5 - AWS SES receiving rules are updated automatically.

The AWS SES receiving rules will automatically get augmented to include the matching rules for the new duplicated routing addresses (for example, support@servicing.example.com) and continue to perform the existing S3 storage and Lambda invocation actions. This automatic update gets performed by Symbee Connect as you duplicate each Email Configuration in the Symbee Connect Admin portal in the previous step. No additional action is required for this.

Step 6 - Update Mailbox Forwarding.

In your existing email provider / public-facing mailboxes, change the Email Forwarding destination for each mailbox being serviced by Symbee Connect from its former Amazon WorkMail address to its new Email Routing Domain address (for example, change the forwarding destination from support@example.awsapps.com** to support@servicing.example.com**).

On the Forward settings, you can continue to retain copies in the original mailboxes if required.

Step 7 - Verify inbound and outbound email processing.

Send test messages to your existing public-facing addresses and confirm that they reach Symbee Connect, while any configured local mailbox copies are retained. Also verify that agent replies and unsolicited outbound emails are delivered using the correct public-facing From addresses.

Step 8 - Remove the obsolete Amazon WorkMail related configuration.

After confirming that email is successfully flowing through the new configuration, remove the former Amazon WorkMail mailboxes in your AWS Account, and delete the associated old Email Configuration entries from within your Symbee Connect Administration Portal.