SOLVED

Add subdomain to existing federated domain with Exhange Hybrid configured

%3CLINGO-SUB%20id%3D%22lingo-sub-297494%22%20slang%3D%22en-US%22%3EAdd%20subdomain%20to%20existing%20federated%20domain%20with%20Exhange%20Hybrid%20configured%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-297494%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20All%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOur%20Office%20365%20is%20consists%20of%20one%20federated%20domain%3A%20company.com.%20Our%20onpremise%20AD%20domain%20consists%20only%20single-forest%20single-domain%3A%20company.com.%20But%20our%20Exchange%202010%20onpremise%20environment%20has%20two%20accepted%20domains%3A%20company.com%20and%20coworkers.company.com.%20Users%20with%20primary%20smtp%20domain%20%25%40coworkers.company.com%20login%20with%20UPN%20co.user%40company.com%20format.%20Currently%20if%20we%20migrate%20%25%40coworkers.company.com%20user%20to%20Exchange%20Online%2C%20their%20primary%20smtp%20domain%20changed%20to%20%25%40company.com.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20I%20understand%20is%20we%20need%20to%20add%20coworkers.company.com%20domain%20to%20federated%20domain.%20How%20should%20I%20add%20coworkers.company.com%20domain%3F%20Is%20it%20by%20Admin%20portal%2C%20add%20new%20domain%3F%20or%20by%20Azure%20AD%20Powershell%20cmdlet%3F%20If%20I%20add%20coworkers.company.com%20domain%20from%20Admin%20portal%2C%20somehow%20it%20give%20permission%20to%20the%20user%40coworkers.company.com%20we%20add%20on%20wizard%20user%20to%20create%20new%20Office%20365%20tenant.%3C%2FP%3E%3CP%3E%26nbsp%3BWe%20would%20like%20to%20use%20two%20domains%20on%20the%20same%20tenant%2C%20and%20keep%20%25%40coworkers.company.com%20email%20users%20as%20is%20if%20we%20migrate%20their%20mailboxes.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20also%20need%20to%20keep%20all%20users%20%2C%20despite%20their%20primary%20smtp%20domain%2C%20still%20logon%20on%20to%20ADFS%20(adfs.company.com)%20using%20current%20UPN.%20We%20do%20not%20have%20option%20to%20add%20domain%20coworkers.company.com%20on%20our%20onpremise%20AD%20environment%20and%20keep%20%25%40coworkers.company.com%20email%20users'%20UPN%20still%20using%20co.user%40company.com.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20a%20lot%20for%20your%20advice.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-297494%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EHybrid%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-301868%22%20slang%3D%22en-US%22%3ERe%3A%20Add%20subdomain%20to%20existing%20federated%20domain%20with%20Exhange%20Hybrid%20configured%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-301868%22%20slang%3D%22en-US%22%3EOoh!!%20Alright!%20Glad%20this%20worked%20out!!%3CBR%20%2F%3E%3CBR%20%2F%3EAdam%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-301793%22%20slang%3D%22en-US%22%3ERe%3A%20Add%20subdomain%20to%20existing%20federated%20domain%20with%20Exhange%20Hybrid%20configured%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-301793%22%20slang%3D%22en-US%22%3E%3CP%3EI%20opened%20the%20case%20to%20Microsoft%20O365%20Support.%20There%20was%20somebody%20in%20the%20company%20who%20created%20O365%20tenant%20with%20coworkers.company.com%20domain.%20I%20took%20over%20the%20domain%20by%20using%20txt%20record%20verification%2C%20and%20then%20remove%20the%20coworkers.company.com%20domain%20from%20that%20tenant.%20I%20then%20add%20subdomain%20coworkers.company.com%20from%20Azure%20AD%20PowerShell.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-298403%22%20slang%3D%22en-US%22%3ERe%3A%20Add%20subdomain%20to%20existing%20federated%20domain%20with%20Exhange%20Hybrid%20configured%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-298403%22%20slang%3D%22en-US%22%3E%3CP%3EThat%20seems%20like%20another%20stupid%20limitation%20of%20the%20%22add%20domain%22%20wizard%2C%20just%20use%20PowerShell%20(New-MsolDomain).%20Although%20I%20just%20tested%20it%20in%20one%20of%20my%20test%20tenants%20and%20I%20was%20able%20to%20add%20a%20subdomain%20to%20a%20federated%20domain%20just%20fine%20via%20the%20portal.%20So%20perhaps%20it's%20something%20specific%20to%20your%20setup.%20Anyway%2C%20just%20use%20PowerShell%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ENew-MsolDomain%20-Name%20sub2.domain.com%20-Authentication%20federated%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-298285%22%20slang%3D%22en-US%22%3ERe%3A%20Add%20subdomain%20to%20existing%20federated%20domain%20with%20Exhange%20Hybrid%20configured%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-298285%22%20slang%3D%22en-US%22%3E%3CP%3Ehmm..the%20domain%20should%20be%20visible!%20And%20a%20new%20tenant%20should%20definitely%20not%20be%20created!%20It's%20been%20awhile%20since%20I%20added%20a%20subdomain%20but%20basically%20it%20should%20be%20as%20usual%20when%20adding%20a%20domain!%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F60%22%20target%3D%22_blank%22%3E%40Juan%20Carlos%20Gonz%C3%A1lez%20Mart%C3%ADn%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F869%22%20target%3D%22_blank%22%3E%40Chris%20Webb%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F58%22%20target%3D%22_blank%22%3E%40Vasil%20Michev%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-298137%22%20slang%3D%22en-US%22%3ERe%3A%20Add%20subdomain%20to%20existing%20federated%20domain%20with%20Exhange%20Hybrid%20configured%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-298137%22%20slang%3D%22en-US%22%3E%3CP%3ESorry%2C%20forgot%20to%20explain.%20It%20display%20user%20test4%40coworkers.company.com%20logged%20on%20to%20office.com%20with%20Admin%20center%20shortcut%20icon%20displayed.%20I%20assumed%20new%20tenant%20for%20coworkers.company.com%20subdomain%20created%20as%20test4%20has%20Adminc%20center%20shortcut%20icon.%3C%2FP%3E%3CP%3EWe%20have%20added%20txt%20record%20for%20coworkers.company.com%20subdomain.%20And%20until%20now%2C%20the%20subdomain%20still%20not%20displayed%20on%20Admin%20center%20%26gt%3B%20setup%20%26gt%3B%20domains%20of%20tenant%20hosting%20company.com.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-298127%22%20slang%3D%22en-US%22%3ERe%3A%20Add%20subdomain%20to%20existing%20federated%20domain%20with%20Exhange%20Hybrid%20configured%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-298127%22%20slang%3D%22en-US%22%3ECan%E2%80%99t%20see%20any%20reference%20to%20creating%20a%20new%20tenant%20on%20your%20screenshot%3F%3CBR%20%2F%3EIs%20the%20subdomain%20listed%20under%20domains%3F%3CBR%20%2F%3EFurthermore%20you%20have%20to%20edit%20the%20dns%20for%20the%20subdomain%20to%20include%20the%20records%20necessary%20for%20the%20services%20you%20will%20use%20it%20for!%3CBR%20%2F%3EYou%20can%20check%20your%20records%20if%20you%20click%20the%20domain%20in%20office%20365%20(%20same%20place%20were%20you%20hopefully%20added%20it%20)%3CBR%20%2F%3EWhen%20everything%20is%20set%20you%20can%20federate%20it%20with%20your%20powershell%20cmdlet%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-298124%22%20slang%3D%22en-US%22%3ERe%3A%20Add%20subdomain%20to%20existing%20federated%20domain%20with%20Exhange%20Hybrid%20configured%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-298124%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20use%20third%20party%20domain%20hosting.%20We%20can%20send%20request%20to%20them%20to%20add%20txt%20record%20as%20we%20have%20done%20for%20company.com%20domain.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-298122%22%20slang%3D%22en-US%22%3ERe%3A%20Add%20subdomain%20to%20existing%20federated%20domain%20with%20Exhange%20Hybrid%20configured%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-298122%22%20slang%3D%22en-US%22%3EWho%20is%20managing%20your%20DNS%E2%80%99s%20or%20you%20domain%20%3F%20Is%20it%20Microsoft%20or%20somewhere%20else%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-298118%22%20slang%3D%22en-US%22%3ERe%3A%20Add%20subdomain%20to%20existing%20federated%20domain%20with%20Exhange%20Hybrid%20configured%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-298118%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20want%20to%20add%20subdomain%20coworkers.company.com%20and%20currently%20we%20already%20have%20federated%20our%20company.com%20domain.%20If%20we%20add%20coworkers.company.com%20from%20admin%20center%20%26gt%3B%20setup%20%26gt%3B%20domains%20%26gt%3B%26nbsp%3B%20add%20domain%2C%20it%20requests%20email%20address%20of%20%40coworkers.company.com%20to%20complete.%20Furthermore%2C%20if%20I%20click%20okay%2C%20I've%20added%20txt%20record%2C%20it%20redirect%20user%40coworkers.company.com%20to%20create%20new%20tenant%20as%20screenshot%20I%20attached.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDoes%20it%20the%20right%20way%20to%20add%20subdomain%20of%20existing%20federated%20domain%3F%20Or%20I%20can%20just%20add%20subdomain%20using%20Azure%20AD%20powershell%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-298115%22%20slang%3D%22en-US%22%3ERe%3A%20Add%20subdomain%20to%20existing%20federated%20domain%20with%20Exhange%20Hybrid%20configured%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-298115%22%20slang%3D%22en-US%22%3Ewhat%20is%20the%20MDL%20server%20url%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-298114%22%20slang%3D%22en-US%22%3ERe%3A%20Add%20subdomain%20to%20existing%20federated%20domain%20with%20Exhange%20Hybrid%20configured%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-298114%22%20slang%3D%22en-US%22%3EHi!%3CBR%20%2F%3EWhat%20is%20your%20question%3F%3CBR%20%2F%3EWhat%20arw%20tou%20trying%20to%20accomplish%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-298070%22%20slang%3D%22en-US%22%3ERe%3A%20Add%20subdomain%20to%20existing%20federated%20domain%20with%20Exhange%20Hybrid%20configured%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-298070%22%20slang%3D%22en-US%22%3E%3CP%3EAttached%20is%20the%20screenshot%20after%20the%20step%20of%20%22become%20the%20admin%22%20subdomain%20coworkers.company.com.%20I%20click%20okay%2C%20i've%20added%20the%20record%2C%20then%20it%20seems%20like%20new%20tenant%20and%20new%20admin%20for%20user%40coworkers.company.com.%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20602px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F62284i29353F135D15127F%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22add%20subdomain.png%22%20title%3D%22add%20subdomain.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eor%20shoud%20I%20just%20run%20this%20on%20powershell%20azure%20AD%20module%3F%3A%3C%2FP%3E%3CP%3Enew-msolfederateddomain%3C%2FP%3E%3CP%3Eprompt%20for%20domainname%3A%20coworkers.company.com%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-297827%22%20slang%3D%22en-US%22%3ERe%3A%20Add%20subdomain%20to%20existing%20federated%20domain%20with%20Exhange%20Hybrid%20configured%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-297827%22%20slang%3D%22en-US%22%3EVasil%20is%20absolutely%20correct%20here!%20No%20verification%20needed%20because%20it%E2%80%99s%20a%20sub%20domain%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-297818%22%20slang%3D%22en-US%22%3ERe%3A%20Add%20subdomain%20to%20existing%20federated%20domain%20with%20Exhange%20Hybrid%20configured%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-297818%22%20slang%3D%22en-US%22%3E%3CP%3EAll%20you%20need%20to%20do%20is%20to%20add%20the%20subdomain%20in%20the%20O365%20admin%20center.%20It%20will%20automatically%20verify%20it%20and%20it%20will%20also%20automatically%20inherit%20the%20authentication%20settings%20of%20the%20primary%20domain.%20PowerShell%20should%20work%20just%20fine%20as%20well.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20part%20I%20don't%20understand%20though%2C%20can%20you%20clarify%3F%3C%2FP%3E%0A%3CBLOCKQUOTE%3E%0A%3CP%3EIf%20I%20add%20coworkers.company.com%20domain%20from%20Admin%20portal%2C%20somehow%20it%20give%20permission%20to%20the%20user%40coworkers.company.com%20we%20add%20on%20wizard%20user%20to%20create%20new%20Office%20365%20tenant.%3C%2FP%3E%0A%3C%2FBLOCKQUOTE%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-297702%22%20slang%3D%22en-US%22%3ERe%3A%20Add%20subdomain%20to%20existing%20federated%20domain%20with%20Exhange%20Hybrid%20configured%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-297702%22%20slang%3D%22en-US%22%3EYes!%20You%20add%20the%20domain%20under%20the%20admin%20portal%20-%26gt%3B%20domains!%20You%20have%20to%20have%20access%20to%20the%20dns%20server%20of%20the%20domain%20also%20though%20to%20proof%20that%20it%E2%80%99s%20yours%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-297694%22%20slang%3D%22en-US%22%3ERe%3A%20Add%20subdomain%20to%20existing%20federated%20domain%20with%20Exhange%20Hybrid%20configured%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-297694%22%20slang%3D%22en-US%22%3EI%20cannot%20add%20coworkers.company.com%20on%20Exchange%20online%20settings%3A%20accepted%20domain.%20It%20gives%20me%20direction%20to%20add%20the%20domain%20on%20tenant%20domain%20settings.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-297503%22%20slang%3D%22en-US%22%3ERe%3A%20Add%20subdomain%20to%20existing%20federated%20domain%20with%20Exhange%20Hybrid%20configured%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-297503%22%20slang%3D%22en-US%22%3EHi!%3CBR%20%2F%3EYou%20can%E2%80%99t%20federate%20a%20domain%20not%20present%20in%20ad!%3CBR%20%2F%3EYou%20could%20add%20the%20domain%20coworker.domain.com%20in%20office%20365%20then%20set%20the%20primary%20mail%20address%20in%20AD%20to%20correct%20address%20via%20the%20proxy%20addresses%20attribute!%3CBR%20%2F%3EI%20might%20have%20missed%20something%20though%3CBR%20%2F%3E%3CBR%20%2F%3EAdam%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Hi All,

 

Our Office 365 is consists of one federated domain: company.com. Our onpremise AD domain consists only single-forest single-domain: company.com. But our Exchange 2010 onpremise environment has two accepted domains: company.com and coworkers.company.com. Users with primary smtp domain %@coworkers.company.com login with UPN co.user@company.com format. Currently if we migrate %@coworkers.company.com user to Exchange Online, their primary smtp domain changed to %@company.com.

 

What I understand is we need to add coworkers.company.com domain to federated domain. How should I add coworkers.company.com domain? Is it by Admin portal, add new domain? or by Azure AD Powershell cmdlet? If I add coworkers.company.com domain from Admin portal, somehow it give permission to the user@coworkers.company.com we add on wizard user to create new Office 365 tenant.

 We would like to use two domains on the same tenant, and keep %@coworkers.company.com email users as is if we migrate their mailboxes.

 

We also need to keep all users , despite their primary smtp domain, still logon on to ADFS (adfs.company.com) using current UPN. We do not have option to add domain coworkers.company.com on our onpremise AD environment and keep %@coworkers.company.com email users' UPN still using co.user@company.com.

 

Thanks a lot for your advice.

17 Replies
Highlighted
Hi!
You can’t federate a domain not present in ad!
You could add the domain coworker.domain.com in office 365 then set the primary mail address in AD to correct address via the proxy addresses attribute!
I might have missed something though

Adam
Highlighted
I cannot add coworkers.company.com on Exchange online settings: accepted domain. It gives me direction to add the domain on tenant domain settings.
Highlighted
Yes! You add the domain under the admin portal -> domains! You have to have access to the dns server of the domain also though to proof that it’s yours
Highlighted

All you need to do is to add the subdomain in the O365 admin center. It will automatically verify it and it will also automatically inherit the authentication settings of the primary domain. PowerShell should work just fine as well.

 

This part I don't understand though, can you clarify?

If I add coworkers.company.com domain from Admin portal, somehow it give permission to the user@coworkers.company.com we add on wizard user to create new Office 365 tenant.

Highlighted
Vasil is absolutely correct here! No verification needed because it’s a sub domain
Highlighted

Attached is the screenshot after the step of "become the admin" subdomain coworkers.company.com. I click okay, i've added the record, then it seems like new tenant and new admin for user@coworkers.company.com.add subdomain.png

 

or shoud I just run this on powershell azure AD module?:

new-msolfederateddomain

prompt for domainname: coworkers.company.com

 

Highlighted
Hi!
What is your question?
What arw tou trying to accomplish?
Highlighted
Highlighted

We want to add subdomain coworkers.company.com and currently we already have federated our company.com domain. If we add coworkers.company.com from admin center > setup > domains >  add domain, it requests email address of @coworkers.company.com to complete. Furthermore, if I click okay, I've added txt record, it redirect user@coworkers.company.com to create new tenant as screenshot I attached.

 

Does it the right way to add subdomain of existing federated domain? Or I can just add subdomain using Azure AD powershell?

Highlighted
Who is managing your DNS’s or you domain ? Is it Microsoft or somewhere else?
Highlighted

We use third party domain hosting. We can send request to them to add txt record as we have done for company.com domain.

Highlighted
Can’t see any reference to creating a new tenant on your screenshot?
Is the subdomain listed under domains?
Furthermore you have to edit the dns for the subdomain to include the records necessary for the services you will use it for!
You can check your records if you click the domain in office 365 ( same place were you hopefully added it )
When everything is set you can federate it with your powershell cmdlet
Highlighted

Sorry, forgot to explain. It display user test4@coworkers.company.com logged on to office.com with Admin center shortcut icon displayed. I assumed new tenant for coworkers.company.com subdomain created as test4 has Adminc center shortcut icon.

We have added txt record for coworkers.company.com subdomain. And until now, the subdomain still not displayed on Admin center > setup > domains of tenant hosting company.com.

Highlighted

hmm..the domain should be visible! And a new tenant should definitely not be created! It's been awhile since I added a subdomain but basically it should be as usual when adding a domain! 

@Juan Carlos González Martín @Chris Webb @Vasil Michev

Highlighted
Solution

That seems like another stupid limitation of the "add domain" wizard, just use PowerShell (New-MsolDomain). Although I just tested it in one of my test tenants and I was able to add a subdomain to a federated domain just fine via the portal. So perhaps it's something specific to your setup. Anyway, just use PowerShell:

 

New-MsolDomain -Name sub2.domain.com -Authentication federated

Highlighted

I opened the case to Microsoft O365 Support. There was somebody in the company who created O365 tenant with coworkers.company.com domain. I took over the domain by using txt record verification, and then remove the coworkers.company.com domain from that tenant. I then add subdomain coworkers.company.com from Azure AD PowerShell.

Highlighted
Ooh!! Alright! Glad this worked out!!

Adam