Home

Godaddy to Office 365 domain move

%3CLINGO-SUB%20id%3D%22lingo-sub-266682%22%20slang%3D%22en-US%22%3EGodaddy%20to%20Office%20365%20domain%20move%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-266682%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20I%20currently%20cannot%20verify%20my%20domain%20in%20a%20new%20office%20365%20tenant%20after%20removing%20it%20from%20a%20godaddy%20tenant.%20The%20office%20365%20helpdesk%20have%20identified%20it%20as%20a%20known%20issue%20that%20has%20to%20be%20fixed%20by%20next%20level%20engineers%20but%20they%20have%20said%20it%20could%20be%2072%20hours%20before%20the%20engineers%20contact%20me%20and%20they%20have%20no%20way%20of%20speaking%20to%20them%20and%20confirming%20what%20is%20going%20on.%20I%20have%20clients%20now%20who%20have%20been%20without%20services%20for%2024%20hours%20for%20reasons%20completely%20out%20of%20my%20control.%20Is%20there%20another%20number%20I%20can%20call%20that%20will%20get%20me%26nbsp%3Ba%20better%26nbsp%3Bexplanation%20of%20what%20is%20happening%3F%20This%20is%20an%20enterprise%20level%20product%20with%20a%20known%20issue%20that%20is%20leaving%20me%20without%20a%20domain%20for%20my%20email%20accounts%20for%20over%2072%20hours%2C%20there%20must%20be%20another%20avenue%20for%20me%20to%20take%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-266682%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-267175%22%20slang%3D%22en-US%22%3ERe%3A%20Godaddy%20to%20Office%20365%20domain%20move%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-267175%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3E%22We%20couldn't%20verify%20domain%20'domainname.com'.%20Please%20close%20the%20wizard%20and%20refresh%20the%20page%2C%20then%20try%20again.%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ESame%20error%20from%20TXT%2C%20MX%20and%20Godaddy%20authorization%20methods.%20I%20have%20also%20tried%20doing%20it%20with%20the%20msol%20module%20in%20power%20shell%20and%20got%20the%20same%20error.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20have%20tried%20multiple%20browsers%20and%20removing%20and%20re-adding%20the%20domain.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20have%20confirmed%20the%20TXT%20record%20is%20coming%20through%20correctly%20via%20nslookup.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E365%20Support%20are%20happy%20that%20it's%20beyond%20a%20configuration%20setting.%20This%20is%20a%20known%20issue%20that%20needs%20next%20level%20support%20to%20resolve.%20But%20the%20front%20line%20support%20cannot%20tell%20me%20what%20the%20actual%20issue%20is%20on%20their%20end%20or%20how%20long%20it%20will%20take%20to%20resolve%2C%20I've%20been%20told%20I'm%20waiting%20up%20to%2072%20hours%20just%20to%20get%20a%20response%20from%20an%20engineer%20who%20can%20fix%20the%20issue.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-266714%22%20slang%3D%22en-US%22%3ERe%3A%20Godaddy%20to%20Office%20365%20domain%20move%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-266714%22%20slang%3D%22en-US%22%3E%3CP%3EHey%2C%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20you%20please%20confirm%20the%20error%20which%20you%20are%20getting%2C%20when%20trying%20to%20verify%20the%20domain%20in%20the%20new%20tenant%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1075237%22%20slang%3D%22en-US%22%3ERe%3A%20Godaddy%20to%20Office%20365%20domain%20move%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1075237%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F222675%22%20target%3D%22_blank%22%3E%40Liam%20Hodges%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20this%20issue%20solved%3F%3C%2FP%3E%3CP%3EWhat%20was%20the%20issue%3F%3C%2FP%3E%3CP%3EHow%20long%20did%20it%20take%20to%20solve%20it%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1075263%22%20slang%3D%22en-US%22%3ERe%3A%20Godaddy%20to%20Office%20365%20domain%20move%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1075263%22%20slang%3D%22en-US%22%3EIt%20was%20solved.%3CBR%20%2F%3E%3CBR%20%2F%3EFrom%20memory%2C%20the%20MX%20method%20worked%20after%20a%20about%2048%20hours%20off%20waiting.%3C%2FLINGO-BODY%3E
Highlighted
Liam Hodges
New Contributor

Hi I currently cannot verify my domain in a new office 365 tenant after removing it from a godaddy tenant. The office 365 helpdesk have identified it as a known issue that has to be fixed by next level engineers but they have said it could be 72 hours before the engineers contact me and they have no way of speaking to them and confirming what is going on. I have clients now who have been without services for 24 hours for reasons completely out of my control. Is there another number I can call that will get me a better explanation of what is happening? This is an enterprise level product with a known issue that is leaving me without a domain for my email accounts for over 72 hours, there must be another avenue for me to take?

4 Replies
Highlighted

Hey, 

 

Can you please confirm the error which you are getting, when trying to verify the domain in the new tenant?

 

Thanks.

 

 

Highlighted

"We couldn't verify domain 'domainname.com'. Please close the wizard and refresh the page, then try again."

 

Same error from TXT, MX and Godaddy authorization methods. I have also tried doing it with the msol module in power shell and got the same error.

 

I have tried multiple browsers and removing and re-adding the domain.

 

I have confirmed the TXT record is coming through correctly via nslookup.

 

365 Support are happy that it's beyond a configuration setting. This is a known issue that needs next level support to resolve. But the front line support cannot tell me what the actual issue is on their end or how long it will take to resolve, I've been told I'm waiting up to 72 hours just to get a response from an engineer who can fix the issue.

Highlighted

@Liam Hodges

 

Is this issue solved?

What was the issue?

How long did it take to solve it?

 

Highlighted
It was solved.

From memory, the MX method worked after a about 48 hours off waiting.
Related Conversations
Office Deployment: Pin to START Menu
Brian LeFlem in Microsoft Intune on
1 Replies
I can't open a Macro enable excel and word file
Roxanne26 in Office 365 on
2 Replies
Content and files in office.com not loading
Nomnomburger25 in Discussions on
3 Replies
Access Takes a Trip: News From Around the Globe
Ebo_Quansah in Access on
0 Replies
Multiple email addresses
MikeInTokyo in Office 365 on
1 Replies