An Azure communication platform for deploying applications across devices and platforms.
Hi @Subroto M
Addition to praneeth response If the custom domain verification is failing even though the DNS record matches, the most common cause is that Azure cannot yet resolve the verification record from public DNS. Ensure that the DNS record is created exactly as required in the Azure portal (usually a TXT record such as asuid.<subdomain> with the verification value or the required CNAME/A record depending on the service). Then verify that the record is publicly visible by running a DNS lookup (for example nslookup -type=TXT yourdomain.com or using an online DNS checker). Also confirm that the record is added in the correct DNS zone, there are no duplicate or conflicting records, and the domain is not already mapped to another Azure resource or tenant. If the record was recently created, allow time for DNS propagation, then refresh and retry the verification in the Azure portal. Once Azure can resolve the correct record from public DNS, the custom domain verification should complete successfully.
https://learn.microsoft.com/en-us/troubleshoot/azure/app-service/connection-issues-with-ssl-or-tls/troubleshoot-custom-domain-issues-azure-app-service
https://learn.microsoft.com/en-us/azure/app-service/app-service-web-tutorial-custom-domain?
let me know if you have any further assistances needed