I'm in a tricky situation where the domain I need to use is provided by a third party that isn't willing to add a TXT record for validation. I need to access services like Entra ID, with or without Copilot, but renaming my Windows domain isn't an option I'm considering. Are there any workarounds or alternatives available besides the usual dead ends?
5 Answers
Just a quick note: the domain validation requirement doesn't relate to your Windows domain name, so you might be worrying about the wrong thing.
You technically don’t need to validate your domain since you can create user accounts using the [tenantname].onmicrosoft.com UPN. Just a heads up, though, those accounts might struggle with spam filters when sending emails.
Look, if this is causing you major headaches, maybe it’s time to consider changing your domain registrar.
It's really necessary to own your domain to make things work smoothly. One suggestion could be to migrate your endpoints and users to a different domain first, then move your server infrastructure later. Alternatively, there’s something called alternate ID for authentication, but it’s not the best option. To utilize all the modern authentication features, you'd want your users' UPNs to match their email addresses and have control over the domain.
Owning your domain is crucial here. Is this third party someone like a parent company? It might help to talk to them if that's the case.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures