Azure App Service: custom domain SSL binding failed (certificate not found, thumbprint or hostname validation)
Binding a TLS/SSL certificate to a custom domain in App Service fails or the domain isn't validated.
Azure App Service custom domain SSL binding failedHostname validation failed asuidCannot bind certificate to hostname App ServiceFailed to create managed certificate for App ServiceThe certificate does not have a private key Meaning
Verify domain ownership with the TXT (asuid) and CNAME/A records, use a Basic tier or higher plan, import the certificate with its private key (PFX with password), choose SNI SSL, and ensure the certificate's SAN covers the hostname. App Service Managed Certificates need public DNS reachable.
Common causes
- Missing/wrong
asuidTXT or CNAME record - Free/Shared tier plan
- PFX without private key or weak algorithm
- SAN doesn't include the hostname
- Proxy (CDN) blocking validation
⚡ Quick fix
- Add DNS records shown in the portal
- Scale up to Basic+
- Upload a PFX with the private key and bind with SNI
Detailed fix by platform
Shell
az webapp config ssl bind --certificate-thumbprint THUMBPRINT --ssl-type SNI --name APP --resource-group RG
How to diagnose
- DNS records — Verified?
- Plan — Basic+?
- PFX — Has key?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- 40615 Azure SQL: Cannot open server 'x' requested by the login. Client with IP address 'y' is not allowed to access the server (Error 40615)
- 553 5.1.8 553 5.1.8 Domain of sender address <x> does not exist (sendmail/Exim sender verification)
- ACM region CloudFront can't use my ACM certificate: it must be requested in us-east-1 (N. Virginia)
Most viewed in SSL / TLS
- HTTPSConnectionPool: Max retries exceeded (SSLError) Python requests: HTTPSConnectionPool(host='api.example.com', port=443): Max retries exceeded with url: /v1 (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] ...')))
- DST Root CA X3 expired (old clients fail) Old clients: certificate has expired — Let's Encrypt chain uses expired DST Root CA X3 (OpenSSL 1.0.x, Android < 7.1.1)
- Keystore was tampered with, or password was incorrect Java keytool: java.io.IOException: Keystore was tampered with, or password was incorrect
Other ways to find it
Where this error sits
Origin: Network. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 18 Nov 2026