Getting started with Amazon WorkMail
After you complete the Prerequisites, you're ready to get started with Amazon WorkMail. For more information, see Getting started with Amazon WorkMail.
You can learn more about migrating existing mailboxes to Amazon WorkMail, interoperability with Microsoft Exchange, and Amazon WorkMail quotas in the following sections.
Topics
- Getting started with Amazon WorkMail
- Migrating to Amazon WorkMail
- Interoperability between Amazon WorkMail and Microsoft Exchange
- Configure availability settings on Amazon WorkMail
- Configure availability settings in Microsoft Exchange
- Enable email routing between Microsoft Exchange and Amazon WorkMail users
- Enable email routing for a user
- Post setup configuration
- Mail client configuration
- Disabling interoperability mode and decommissioning your mail server
- Troubleshooting
- Amazon WorkMail quotas
Enable email routing for a user
We recommend that you complete the following steps first for test users before applying any changes to your organization.
-
Enable the user account that you are migrating to Amazon WorkMail. For more information, see Enable existing users.
In the Amazon WorkMail console, ensure that there are at least two email addresses associated with the enabled user.
-
<workmailuser@orgname.awsapps.com>
(this is added automatically and can be used for tests without your Microsoft Exchange.) -
<workmailuser@yourdomain.com>
(this is added automatically and is the primary Microsoft Exchange address.)For more information, see Edit user email addresses.
-
Ensure that you migrate all data from the mailbox in Microsoft Exchange to the mailbox in Amazon WorkMail. For more information, see Migrating to Amazon WorkMail.
-
After all of the data is migrated, disable the mailbox for the user on Microsoft Exchange. Then, create a mail user (or mail-enabled user) that has the external SMTP address pointed to Amazon WorkMail. To do this, use the following commands in the Exchange Management Shell:
Important
The following steps erase the contents of the mailbox. Ensure that your data has been migrated to Amazon WorkMail before you attempt to enable email routing. Some mail clients don't seamlessly switch to Amazon WorkMail when you run this command. For more information, see Mail client configuration.
$old_mailbox = Get-Mailbox
exchangeuser
Disable-Mailbox $old_mailbox
$new_mailuser = Enable-MailUser $old_mailbox.Identity -ExternalEmailAddress
workmailuser@
-PrimarySmtpAddress $old_mailbox.PrimarySmtpAddressorgname
.awsapps.com.rproxy.goskope.comSet-MailUser $new_mailuser -EmailAddresses $old_mailbox.EmailAddresses -HiddenFromAddressListsEnabled $old_mailbox.HiddenFromAddressListsEnabled
In the above commands,
orgname
represents the name of your Amazon WorkMail organization. For more information, see Disabling mailboxand Enabling mail users on Microsoft TechNet. Send a test email to the user (in the example above,
workmailuser@yourdomain.com
). If email routing has been enabled correctly, the user should be able to log in to their Amazon WorkMail mailbox and receive the email.
Note
Microsoft Exchange remains the primary server for incoming email as long as you would like to have interoperability between the two environments. To ensure interoperability with Microsoft Exchange, the DNS records shouldn't be updated to point to Amazon WorkMail until later.
Post setup configuration
The above steps move a user mailbox from Microsoft Exchange Server to Amazon WorkMail, while keeping the user in Microsoft Exchange as a contact. Because the migrated user is now an external mail user, Microsoft Exchange Server imposes additional constraints. There may also be additional configuration requirements to complete the migration.
The user might not be able to send emails to groups by default. To enable this functionality, you must add the user to a safe sender list for all groups. For more information, see Delivery management
on Microsoft TechNet. The user might not be able to book resources. To enable this functionality, you must set the
ProcessExternalMeetingMessages
of all of the resources that the user needs to access. For more information, see Set-CalendarProcessingon Microsoft TechNet.
Mail client configuration
Some mail clients don't switch seamlessly to Amazon WorkMail. These clients require the user to perform additional setup steps. Different mail clients require different actions to be taken.
-
Microsoft Outlook on Windows – Requires Outlook to be restarted. At startup, you are required to choose whether to keep using the old mailbox or use a temporary mailbox. Choose the temporary mailbox option. Then, reconfigure the Microsoft Exchange mailbox.
-
Microsoft Outlook on MacOS – When Outlook is restarted, it will prompt the following message: Outlook was redirected to server
orgname
.awsapps.com. Do you want this server to configure your settings? Accept the suggestion. -
Mail on iOS – The mail app stops receiving emails and generates a can't get mail error. Recreate and reconfigure the Microsoft Exchange mailbox.