unable to validate a domain. txt records propagating. cant do a take over because it wont validate. im in a loop. powershell wont find microsoftonline.com changing from get to push has me in a login loop with microsoft. im stuck.

Could you clarify what kind of domain validation you're doing?

There are a couple of different scenarios here, and the fix depends on which one applies:

1. Microsoft Entra tenant custom domain validation

If you're adding the domain to a Microsoft Entra tenant, validation is done with a TXT or MX record to prove ownership.

A few things to keep in mind:

• DNS propagation can take an hour or more, and sometimes a few days depending on the registrar
• A domain can only be verified in one directory at a time
• If the domain is already verified in another tenant, it must be removed there before it can be added here

Related docs:

• Add your custom domain - Microsoft Entra
• Manage custom domain names in Microsoft Entra ID

2. PaaS custom domain validation

If you're mapping the domain to a service such as Azure App Service, the validation flow is different. In that case, Azure checks for the required A/CNAME record and the verification TXT record for the app.

Useful points:

• Root domains typically use an A record
• Subdomains typically use a CNAME record
• DNS changes can take time to propagate
• The domain may already be attached to another Azure resource

Related docs:

• Set up an existing custom domain in Azure App Service
• Troubleshoot custom domain issues in Azure App Service

One important note

If the domain was previously attached to another tenant, there usually isn't an instant "release" from Microsoft's side. In practice, you should allow at least an hour, and sometimes longer, for the old association and DNS changes to fully clear.

If you can confirm whether this is tenant-level domain verification or PaaS custom domain mapping, I can help narrow it down further.