Solved

MX Records

Posted on 2016-07-26
2
55 Views
Last Modified: 2016-08-19
Im currently doing a migration of several users to O365, Ive changed all the DNS records apart from the MX records, however cannot add users alias's until I complete the DNS record, which I dont want to do until we are ready to migrate.

Can I ignore the MX record warnings and then add the alias, then when ready to migrate change the MX records? From my understanding users who send to my users on O365 external to my account O365 will still use the MX records and the emails will goto the current MX record destination. Is that right? This means they can continue to send and recive emails on the old system until I flick the switch and change the MX records, then all the users and alias's are already setup.
0
Comment
Question by:tonelm54
2 Comments
 
LVL 39

Accepted Solution

by:
Vasil Michev (MVP) earned 500 total points
ID: 41729322
Yes, you can ignore the warnings. All you need to do is verify the domain and set its purpose to Exchange Online, which you have already done.

Mail will continue flowing to the old system though, which might or might not be a problem :)
0
 

Expert Comment

by:Steven Rundle
ID: 41729485
I just did an Exchange Online migration.

While in the process, you basically have a hybrid setup. Your on-premise users that you synchronize will become mail contacts to your online exchange organization, and your online users will become mail contacts to your on-premise organization when the mailbox is migrated.

It can get a little  weird when your clients are cached mode and they have outdated OABs or you are missing distribution groups on the online side, and that can be a little bit of a pain as you migrate, but mail should continue to flow between your online and on-premise users without too much trouble. On-premise users will send mail out through your on-premise organization, and online users will send mail out through MS's servers.

Your user accounts will have a couple different attributes that are relevant here. Proxyaddress, which should contain SMTP:<user>@domain.com as well as smtp:<user>@domain,onmicrosoft.com and possibly also smtp:<user>@domain.mail.onmicrosoft.com

External SMTP servers will resolve MX for domain.com and see your on-premise server, and send the mail there. If the the destination user's mailbox has been migrated, they should show up as a mail user and will have a targetAddress attribute that tells your exchange to reroute the mail back out to <user>@domain.onmicrosoft.com.

You just need to have the appropriate connectors set up on each end to handle the mail flow. The Hybrid wizard sets them up for you.
0

Featured Post

[Webinar] Disaster Recovery and Cloud Management

Learn from Unigma and CloudBerry industry veterans which providers are best for certain use cases and how to lower cloud costs, how to grow your Managed Services practice in IaaS clouds, and how to utilize public cloud for Disaster Recovery

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article explains in simple steps how to renew expiring Exchange Server Internal Transport Certificate.
MS Outlook is a world-class email client application that is mainly used for e-communication globally.  In this article, we will discuss the basic idea about MS Outlook, its advanced features, and types of MS Outlook File formats.
Migrating to Microsoft Office 365 is becoming increasingly popular for organizations both large and small. If you have made the leap to Microsoft’s cloud platform, you know that you will need to create a corporate email signature for your Office 365…
This video discusses moving either the default database or any database to a new volume.

863 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

27 Experts available now in Live!

Get 1:1 Help Now