Microsoft Entra ID Domain Verification - Urgent Resolution Required

Question

Microsoft Entra ID Domain Verification - Urgent Resolution Required Our custom domain [xxxxxx.info] has been pending verification in Microsoft Entra ID for over 35 hours despite proper DNS configuration and global propagation confirmation. Technical Details: Custom Entra Domain: [coolbiz.info] Required TXT record: MS=xxxxxxxxxx DNS propagation: Confirmed within 30 minutes via Google Public DNS/cname lookup Current status: Record visible globally for 35+ hours, Entra ID still shows "unverified" Verification Evidence: Microsoft Copilot provided the following DNS validation command, which we executed successfully: curl "https://dns.google/resolve?name=xxxxx.info&type=TXT" Command Output from Windows CLI: json {"Status":0,"TC":false,"RD":true,"RA":true,"AD":false,"CD":false,"Question":[{"name":"[xxxxx.info].","type":16}],"Answer":[{"name":"[xxxxxxxx.info].","type":16,"TTL":14400,"data":"google-site-verification=T7KP8YQ_EsrnemThj1N_3wYnApbDVjrEQpRMjf9ftq0"},{"name":"[xxxxxxxx.info].","type":16,"TTL":3600,"data":"MS=ms73896553"},{"name":"[xxxxxxxx.info].","type":16,"TTL":14400,"data":"google-site-verification: googlee2dd70b33aa63327.html"},{"name":"[controlbiz.info].","type":16,"TTL":14400,"data":"v=spf1 a mx include:[websitewelcome.com] ~all"}],"Comment":"Response from 162.159.24.80."} The TXT record MS=xxxxxxxxis clearly present and propagated globally. Critical Support Issue: This integration problem required me to independently discover the fundamental requirement for matching custom domains across separate Microsoft 365 and Entra ID accounts - critical information that was never provided during extensive support correspondence. My development team has been going back and forth with support day after day after day on my behalf, receiving suggestions about E1/E3/E5 licenses and other irrelevant solutions, while the actual requirement (custom domains set as primary on both platforms to connect licensing) was never mentioned. I've invested an additional 15 hours of independent research beyond the 50+ combined hours between myself and my development team, creating and canceling multiple Microsoft 365 subscriptions trying to understand why the services wouldn't connect. Only through Microsoft Copilot did I discover that matching custom domains set as primary are required to apply Microsoft 365 licensing to Entra ID registered applications. Business Impact: This verification delay is blocking our Microsoft 365/Entra ID integration for calendar API functionality. The combined time investment represents hundreds of dollars in development costs, and each day of delay represents potential revenue loss from our SaaS product launch. As a paying professional support customer, I expect guidance that prevents such extensive trial-and-error troubleshooting. Immediate Action Required: Please manually verify our domain or clear Microsoft's server-side cache to recognize the properly configured TXT record. The DNS configuration is correct and validated by your own platform's recommended verification method. This appears to be a Microsoft infrastructure caching issue, not a customer configuration error, and requires immediate resolution given the extensive time already invested in this integration.

Also attaching below the screenshot of it.