Hybrid Migration from Exchange 2016 to office365

Anonymous
2018-02-15T08:36:09+00:00

Hi MS,

I am in the planing phase of doing 10 users Pilot Hybrid migration to office 365 in E3 plan using our Volume licence.

We have two 2016 exchange servers running in DAG

We also have email filtering done via Mimecast and for purpose of this exercise i want to leave email filtering to mimecast and not use EOP.

I want to get a clear idea of exact steps I need to take to configure this.

However, before I do anything i want to make sure it does't affect our SMTP or any other users from reading tons of articles and some previous experience with office 365 this are the steps i think needs to be performed.

  1. use exchange server deployment assistance

 - check prereq - all good

My questions  Questions are 

On step 14

If i add this TXT record this will not affect any mail flow this is purely for domain verification? 

Question 2

on the step 15 -29 here 

https://technet.microsoft.com/en-us/exdeploy2013/Checklist?state=3229-W-EwAIAAAAQAAAAAEAAAAAACAAAABEaAOFAAA~

will that affect any existing mail flow or existing connectors as we have few there

Question 3 

overall understanding is mailflow will still be going through exsting exchange server and other 240 users will not be affected and not other server or services such as smtp, scanning service will be affected due to this. 

We never need to change MX records and we don't have to make any changes to mimecast?

Please clarify these ASAP, would be really appreciated.

Microsoft 365 and Office | Subscription, account, billing | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

58 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2018-02-16T09:27:48+00:00

    Hi Solution_Pro,

    If you don’t have any internal DNS, you just need to point the autodiscover record to your on-premise Exchange servers. If you have internal DNS, you need to make them the same one as external DNS records.

    Please feel free to let me know if you have further questions.

    Best Regards,

    Erick

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-02-15T11:00:50+00:00

    Thanks Leo,

    Regarding the auto discover, i have to create a DNS entry on my exchange server for autodiscovery resolving to local exchange?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-02-15T09:57:55+00:00

    Hi Solution_Pro,

    Please kindly check following answers and feel free to let us know if there is anything unclear.

    1. No, it won't affect any mail flow and it's pure for domain verification.
    2. No, actually HCW (hybrid Configuration Wizard ) will create two new connectors.
    3. MX records depends mail routing. If you point it to on premise server, then the emails will be routed to on premise server first. Vice versa, if you point it to Exchange online, then the emails will be routed to online server first. So you can leave it there or point to Exchange online. But there is one thing you do need to notice that Autodiscover records need to point to on premise server.

    Regards,

    Leo

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments