Cutover Migration DNS issue using smart host

Question

Hi folks,

I am decommissioning my existing exchange server and creating new mailboxes in the Office 365 portal. No migration of mailboxes is involved from exchange server to Office 365. All new mailboxes are being created in the Office 365 portal. I am currently using a smart host provider for anti spam and mail filtering. I would like to continue to use the smart host services in future by integrating them into Office 365. I have done a test run of the migration process and have a few issues come up

1. DNS section is incomplete - reason my current mx record on the Exchange server point to the smart host. I would like to keep it the same. In the O 365 section is point to domain.mail.protection.outlook.com. I am able to send and receive emails as the mx records remain unchanged and i am ok with it. It is in future when i think of using the additional services involving lync sip and sharepoint do i need to change any of these records to point to Office 365. 
2. I do not have complete control over my dns registrar control panel. I tried adding  a text record to complete the domain verification. I got the message it might take upto 2 hours for the records to be updated. Is there a quickfix to this. I didnt want to change the MX records and had to go via the text record verification process.
3. During the test migration the exchange server was made offline. I am currently hosting the exchange server on a domain controller with dhcp role. While doing a real migration do i just turn off the exchange services. I didnt want to turn off the DC in a real world scenario

Can anyone advise

Answer 1

Hi RM2616, 

The answer is No.

A Cutover migration batch will set up a connection from Office 365 to the local Exchange server to migrate the mailbox. So, during the Cutover migration, the on-premise Exchange server cannot be offline until the migration finishes. 

Thanks,

Claud

Answer 2

Hi RM2616, 

Do you need further assistance?

Thanks,

Claud

Answer 3

Claud thanks for your reply. For Issue 3 , I was told by my smart host provider the exchange server need to be offline. I believe it isn't necessary during a cutover migration. Would it be ok to disable exchange services during the migration.

Answer 4

Hi RM2616, 

I would like to address the issues one by one:

Issue 1: You can ignore it. In this case, the MX record doesn’t need to be pointed to Office 365. If the custom domain has been verified, you can use it with Office 365 services. 

Issue 2: So far, there is no quick fix. From the description, the message you mentioned should occur on your DNS hosting provider. If you want to let the DNS record be updated faster, please contact the DNS hosting provider for assistance. 

Issue 3:  I’m not very clear about “During the test migration the exchange server was made offline.”. Generally, a Cutover migration doesn’t let the on-premise Exchange server be offline. Could you please more detailed information about it, such as the symptom you encountered. 

Thanks,

Claud