This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(76.8, 98%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ED%3C/text%3E%3C/svg%3E)
i have started migrating the mailboxes but i have not completed the batches yet . so they mail is in sync (up to 95%) when is the ideal time fore the MX record to be updated Should i complete the batches and wait a few days or can i complete the batches and update MX records all in one shot?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(25.6, 67%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJS%3C/text%3E%3C/svg%3E)
Hi @dirkdigs
Do suggestions below help? If an Answer is helpful, please click "Accept Answer" and upvote it.
In a hybrid environment, you can change the MX anytime to point to 365. In fact, I would change before moving mailboxes. then send a test message and verify the on-prem mailbox got it, then move the mailboxes.
Same thing with autodiscover?
That is different. Autodiscover should not be changed until ALL the mailboxes have been moved :)
You will notice they speak to the MX record. That is not really accurate however. I prefer to change it before moving mailboxes so everything goes through EOP before moving - but you can really move it anytime.
https://learn.microsoft.com/en-us/exchange/decommission-on-premises-exchange
Hi @dirkdigs
Do suggestions above from Andy help? Yes, we need point autodiscover record to on-premise Exchange server during hybrid environment.
For On-premise mailbox, it remain use previous autodiscover lookup behavior to find endpoint and access to Exchange.
For migrated mailbox, autodiscover service will redirect On-premise autodiscover record to Office 365 (autodiscover-s.outlook.com), and access to Office 365.
If you have migrated all the mailboxes to cloud, you could follow the steps above to change the autodiscover record point.
In addition, some more links below introduce about the MX record in hybrid for your reference as well:
MX Records for Exchange Hybrid Deployments .
Official document here: Transport routing in Exchange hybrid deployments
If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
one of the migrated mailboxes is showing disconnected in outlook client . The Outlook client has been restarted several times.
How do we fix it? Do we need to create a new profile?
Yes, create a new Outlook profile. If the user can access the mailbox via Outlook Web Access, then you know the mailbox itself is good
looks like all the users for a particular domain had outlook as being disconnected after the mailbox was moved .
on-premise exchange is version 2013.
Any idea why this happened.?
From what i understand outlook should have reconnected automatically and found the new mailbox on it's own .
It should, but Outlook profiles also break pretty easily at times :)