SOLVED
Home

Exchange Hybrid Wizard stuck at Adding Federated Domain

%3CLINGO-SUB%20id%3D%22lingo-sub-7872%22%20slang%3D%22en-US%22%3EExchange%20Hybrid%20Wizard%20stuck%20at%20Adding%20Federated%20Domain%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-7872%22%20slang%3D%22en-US%22%3E%3CP%3ESo%2C%20we%20trying%20to%20setup%20a%20full%20hybrid%20configuration%20between%20our%20Exchange%202013%20onPrem%20and%20Office%20365.%3C%2FP%3E%3CP%3EUnfortunately%20we're%20stuck%20a%20%22Adding%20Federated%20Domain%22.%20This%20is%20the%20step%20that%20follows%20after%20verifying%20the%20TXT%20record.%3C%2FP%3E%3CP%3EI've%20left%20it%20running%20over%20the%20weekend%2C%20but%20still%20nothing.%20Tried%20it%20today%20today%20again%2C%20same%20result.%3C%2FP%3E%3CP%3EUnfortunately%20I%20wasn't%20able%20to%20find%20any%20helpful%20log%20entries.%20Am%20I%20missing%20something%3F%3C%2FP%3E%3CP%3EThe%20Exchange%20Connectivity%20Analyzer%20runs%20through%20just%20fine%20to%20our%20onPrem%20environment.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-13286%22%20slang%3D%22en-US%22%3ERE%3A%20Exchange%20Hybrid%20Wizard%20stuck%20at%20Adding%20Federated%20Domain%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-13286%22%20slang%3D%22en-US%22%3EThanks%20for%20sharing%20the%20solution!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-12993%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Hybrid%20Wizard%20stuck%20at%20Adding%20Federated%20Domain%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-12993%22%20slang%3D%22en-US%22%3EReally%20interesting%20collection%20of%20issues%20Ivan%20-%20thanks%20for%20posting!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-11938%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Hybrid%20Wizard%20stuck%20at%20Adding%20Federated%20Domain%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-11938%22%20slang%3D%22en-US%22%3EHad%20the%20issue%20solved%20with%20the%20help%20of%20Microsoft%20CSP%20Support%2C%20since%20our%20CSP%20also%20wasn't%20able%20to%20solve%20the%20issue.%3CBR%20%2F%3EFor%20those%20interested%2C%20since%20there%20isn't%20much%20about%20this%20specific%20error%20on%20the%20web%3A%3CBR%20%2F%3E%3CBR%20%2F%3EIssue%201%20-%20Timezone%3CBR%20%2F%3EIt%20looks%20like%20the%20logs%20recommend%20you%20to%20have%20your%20AD%20Servers%20and%20the%20Exchange%20Server%20(where%20we've%20run%20the%20Hybrid%20Wizard)%20set%20to%20the%20UTC%20Timezone.%20Not%20sure%20if%20this%20is%20really%20needed%2C%20but%20it%20was%20highlighted%20as%20an%20error%20in%20the%20hybrid%20wizard%20log%3CBR%20%2F%3E%3CBR%20%2F%3EIssue%202%20-%20DNS%20Lookup%3CBR%20%2F%3EEven%20though%20our%20TXT%20record%20for%20verification%20was%20properly%20set%2C%20all%20parties%20where%20unaware%2C%20that%20the%20specific%20DNS%20Server%20that%20hosted%20our%20DNS%20records%20(external%20provider)%20was%20stuck%20and%20didn't%20really%20resolve%20the%20DNS%20lookup%20from%20the%20Hybrid%20Wizard.%20Our%20provider%20had%20to%20restart%20their%20DNS%20services%2C%20after%20that%20everything%20worked%20again.%3C%2FLINGO-BODY%3E
Highlighted
Ivan Unger
Valued Contributor

So, we trying to setup a full hybrid configuration between our Exchange 2013 onPrem and Office 365.

Unfortunately we're stuck a "Adding Federated Domain". This is the step that follows after verifying the TXT record.

I've left it running over the weekend, but still nothing. Tried it today today again, same result.

Unfortunately I wasn't able to find any helpful log entries. Am I missing something?

The Exchange Connectivity Analyzer runs through just fine to our onPrem environment.

3 Replies
Highlighted
Solution
Had the issue solved with the help of Microsoft CSP Support, since our CSP also wasn't able to solve the issue.
For those interested, since there isn't much about this specific error on the web:

Issue 1 - Timezone
It looks like the logs recommend you to have your AD Servers and the Exchange Server (where we've run the Hybrid Wizard) set to the UTC Timezone. Not sure if this is really needed, but it was highlighted as an error in the hybrid wizard log

Issue 2 - DNS Lookup
Even though our TXT record for verification was properly set, all parties where unaware, that the specific DNS Server that hosted our DNS records (external provider) was stuck and didn't really resolve the DNS lookup from the Hybrid Wizard. Our provider had to restart their DNS services, after that everything worked again.
Highlighted
Really interesting collection of issues Ivan - thanks for posting!
Thanks for sharing the solution!
Related Conversations
Office 365 Sending Limit Clarification
jab9417 in Office 365 on
0 Replies
SharePoint 2016 / sharepoint online
Share24x7 in SharePoint on
1 Replies
Office 365 domain using external email server
SimonNZ in Office 365 on
1 Replies
Group and User Mix-up
Ruby_Monday in Office 365 on
3 Replies
Ports
Rising Flight in Office 365 on
0 Replies
Exchange Hybrid Best Practises about autodiscover
woelki in Exchange on
0 Replies