Office 365 Hybrid Configuration

I have a user running SBS 2011 and using Exchange Server. I need to start migrating them over to Outlook 365. They have something like 30 users. I have their Office 365 account set up and want to "play" with migration. The changes to their DNS have not been made so everything is still coming in to their Exchange Server and everything done on their Office 365 account should be temporary.

   So... the last time I did this I used what they called a "Cutover Migration". Worked well simply because it would continually sync their SBS Account to their Office 365 Account until I decided to stop the sync. I guess that type of migration is no longer available. Now from their Office 365 account I have gone under "Migration" and downloaded the "Office 365 Hybrid Configuration". Have installed it on a on-site workstation and it looks interesting but not sure what it is going to do. I have connected it to the SNS Server and to their Office 365 account and am sitting at the point where I need to select the Hybrid Features and don't want to go any farther because I am in fear of doing something  permanent I don't want to do.

   Is this "Office 365 Hybrid Configuration" a continual Sync? A one shot deal? Exactly what will happen if I click "Next" and turn it loose?
LVL 15
LockDown32OwnerAsked:
Who is Participating?
 
Cliff GaliherCommented:
Cutover migrations are still a thing:

https://support.office.com/en-us/article/cutover-migration-to-office-365-9496e93c-1e59-41a8-9bb3-6e8df0cd81b4?ui=en-US&rs=en-US&ad=US

Hybrid migrations don't sync.  They move mailboxes from one to the other (or back) much like moving a mailbox is done with multiple on-premises servers.  

Both involve irrevocable changes so if you aren't familiar with the process, set up a test bed with a fake domain and tenant. Don't even play on a live system.  Or find a migration partner.
0
 
LockDown32OwnerAuthor Commented:
That's exactly what I don't want to do. Their Exchange Server is running flawlessly and I don't want to change a thing. Can you refresh my memory? It was the cutover migration that did a one direction sync from the On-Premise to the Cloud wasn't it? You could let it run for weeks after changing the MX records to pick up any straggler emails that came in to the On-Premise?

   You could even go as far as deleting Office 365 accounts and it would re-add it from the sync? It was pretty easy and didn't make any changes to the actual On-Premise Exchange Server. Is my memory correct?
0
 
Cliff GaliherCommented:
Cutovers are one-way sync, yes. And yes, it will do differential syncing to catch stragglers after you update the MX record.

But to properly sync and not burn bandwidth, even a cutover does make changes to the on-premises server.  Only an IMAP migration would be 100% unobtrusive, and has many other drawbacks.  Thus backups and caution are always recommended, and even a backup in this case has the potential for emails lost after the latest backup.  Gaining experience on a test platform is essential when doing things like this.  The risk is low (if the environment is healthy and instructions are followed) but the risk is there.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
LockDown32OwnerAuthor Commented:
The cutover still sounds like the way to go even after reading your link. The problem is that the Office 365 console use to allow you to set up and start a cutover migration. That option no longer seems to exist. The link didn't have it either. Where do you set up and start a cutover migration at this point?
0
 
Cliff GaliherCommented:
It is in the esxhange admin console (it has always been there), not the office 365 admin console. Open up EAC, then find migration under recipients  then hit the plus sign to add a migration plan.

I also highly recommend using the planning tools available from Microsoft to create a migration plan and follow it. The planner will create very details steps to follow including how to add a cutover migration.
0
 
LockDown32OwnerAuthor Commented:
It has been a while since I have done one. I can select 3 out of four migration types. Unfortunately the one I can't select is the cutover. No error messages or prompts. The button is simply not checkable....
0
 
Cliff GaliherCommented:
Usually a good sign that your environment isn't ready for it.  As I said, a cutover does require some on-prem connectivity and that the environment meet a certain minimum requirements as well.  The planner tool will get you there, but there are enough that I don't recall them all off the top of my head.
0
 
Cliff GaliherCommented:
You are following the steps in the link I posted?  The web page has TWO tabs.  The first is just "considerations" and the second" is the "running a cutover migration" including steps.

It calls out that this is done in the EAC (as I mentioned) and calls out prerequisite steps (including creating a migration endpoint.)  You can't create a cutover batch job if the endpoint doesn't exist for starters.

-Cliff
0
 
LockDown32OwnerAuthor Commented:
Must be blind. Didn't see two tabs or any reference to EAC in that link. I called M$. The problem turn out to be that by default the Tenant has directory sync enabled and you can't run a Cutover with directory sync enabled. They did a lot of PowerShell commands to disable directory sync and the Cutover became a selectable option. Thanks for the help.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.