Office 365: Common mistakes when configuring Hybrid Deployment

I am putting together a list of common mistakes made when configuring Hybrid Deployment. Items will be added to the list as I see them or are made aware of their existence, feel free to send me suggestions.

Always use the HCW (Hybrid Configuration Wizard) when configuring Hybrid Deployment.

Admin account not mail enabled

I think that this is probably the most common mistake, especially in hosted environments where multiple people from different organizations are administrators on the the Exchange Organization.

Always mail enable Exchange Admin accounts, or the wizard may fail during Set-HybridConfiguration or Update-HybridConfiguration.

You may see errors such as: “ERROR:Updating hybrid configuration failed with error 'Subtask ValidateConfiguration execution failed: Configure Legacy Exchange Support” as a symptom of the Admin account not being mail enabled.

DNS TXT record

When running the Hybrid Configuration Wizard, you are asked to create a DNS TXT record as proof of domain ownership. Do not ignore this step, as the wizard will fail in the end.

Create the record and wait 15-20 minutes before continuing.

Three strikes and you’re out

If the Hybrid Configuration Wizard fails for any reason; troubleshoot the problem instead of just running the wizard again. If configuring a hybrid relationship fails three times, you need to wait 24 hours before trying again.

I hope this will ease your planning and troubleshooting. Enjoy…


Comments (8)

  1. No, planning is your friend here, and trying it out in a test environment with a test tenant before doing it for the client…

  2. Anonymous says:

    Thanks for your blog, it was the “Admin account not mail enabled” which had got me!

  3. It’s a security feature…

  4. moh10ly says:

    Is there any message that distinguishes the error resulted by the 3 times failure from the hybrid wizard?

  5. anonymous2 says:

    Why does it require to wait 24hrs if it fails 3 times?

  6. anonymous2 says:

    Is there any way to workaround this. Trying to do for a client and is time sensitive. It would also help for troubleshooting.

  7. Todd says:

    No reference to the 24 hr fail limit in the Exchange Server Deployment Assistant either!!

  8. Joost says:

    The software is totally crap. It throws exception after exception with no real clue what is wrong. The autodiscover support is totally inconsistent with the Exchange documentation and the remote connectivity analyzer. Releasing crap like this is a bloody

Skip to main content