This chapter explains how to move a domain between two Microsoft tenants using On Demand Migration with the following steps:
Steps:
Introduction
Differences between Basic and Advanced Email Relay Service
Requirements
On Demand Migration Project Setup
Moving a Domain
Step 1: Starting the Domain Cutover
Step 2: Enabling Email Relay
Step 3: Redirect MX
Step 4: Move Domain
Step 5: Restoring MX
Step 6: Completing Domain Move(Step 6)
Validating the Result
Frequently Asked Questions
Can I remove Global Administrator from my account after creating my project?
Can I use a wild card certificate for Advanced Email Relay Service?
Domain Move Relay Service being discontinued after Dec 31, 2025.
I am receiving an error during the remove addresses step related to duplicated addresses. How can I locate the duplicate accounts?
I am using the Basic Mode Email Relay Service for my domain move project. What is the best method to hold the email during the domain move and resume the delivery after the domain is moved?
My company security policy does not allow the global administrator role to be assigned the account, can I still move my domain?
The remove address step cannot continue because my hybrid objects in the cloud are still associated with my domain, what should I do?
Will my end-users have to update or recreate their target Outlook Profiles when their Primary Email address is updated during a domain move?
Moving a Domain
Step 1: Starting the Domain Cutover
- Log in to Quest On Demand.
- Navigate to Migration.
- Select the Domain Move project previously configured.
- Select the Domain from the Domain Cutover Dashboard and click on Start Cutover.
- Review the Before You Begin Guide in the pop-up window, and once finished click Start.
- Review the Warning messages regarding unmatched objects and Click Next
- Select a replacement domain from the dropdown menu and then choose As Primary Address from the list of options below and click Next
- As Primary Address – Domain will be added as the primary email address and will replace the existing primary email address for matched objects.
- As Secondary Address only – Domain will be added as a secondary email address for matched objects
- Do not update – Domain will not be added for matched objects
NOTE Do not install local agents on AD domain controllers in a production environment.
Step 2: Enabling Email Relay
- On Demand Migration for Active Directory will now start the Email Relay provisioning process. The screen will automatically refresh and move to the next step once the Email Relay is provisioned.
Step 3: Redirect MX
- Update the DNS MX record for the domain being moved and point it to the Email Relay Service. Select the checkbox and click Next when the MX record is updated.
NOTE Once the MX record has been updated, external incoming email messages will be delivered to the Email Relay Service (ERS) first. Once the message is processed by ERS it will be sent to the target tenant for final delivery.
