Hello,

I’m in the early planning / testing phase of preparing to migrate our staff from on-prem DC’s & Exchange 2013 to MS365 and Exchange Online.

Looking to have a hybrid AD solution in the end so authentication can occur on premise using our DC’s, and when off-net they can use AzureAD. I believe the AzureAD Sync Tool will assist with 2-way synchronization so account records are kept up to date.

We have around 100 staff, that will be migrated, and we’ll be setting up a domain alias because our on-prem domain was a “.local” domain.

Has anyone gone through this sort of process before, if so what was your experience like?

Were there any gotcha’s or major issues that you came across?

After completing your migration, was there something you wish you knew at the beginning that would have saved you time?

Thanks in advance for any feedback.

  • MentallyExhausted@reddthat.comM
    1·
    1 year ago

    If you’ve never done this before, you may want to hire an outside consultant. I’ve done a million of these migrations, and there can be issues, and MS support sucks these days.

    That said, broad overview: first step is installing Azure AD Connect and syncing to your 365 tenant.

    Second step is updating UPN suffixes to match your public domain.

    Third step is installing the Hybrid Wizard on your exchange server and doing a test migration.

    • packetlossOP
      1·
      1 year ago

      I appreciate the bullet point steps.

      I may suggest we look into a consultant, but I wanted to do my due diligence first before adding that expense to the company.

      I have a lab environment setup with a pair of domain controllers and an Exchange 2013 Server with some test mailboxes, public folders, shared calendars, and shared mailboxes on it. Just trying to simulate some of the things we have in our production environment.

      I’ll look into the Hybrid Wizard and see how that differs from the built-in exchange migration tool that lets you batch migrate objects to Exchange Online.