You're encountering a known issue that sometimes affects Power Pages when adding a custom domain with an SSL certificate, particularly when the process gets stuck at the "Create SSL Binding" step. Based on Microsoft's documentation and community reports, here are the most likely causes and best practices to resolve it:
Ensure your .pfx
certificate meets all of the following:
OID = 1.3.6.1.5.5.7.3.1
)
.If any of these are missing, the binding may silently fail.
Even if the TXT record is validated, the CNAME record must also be fully propagated. Use tools like https://dnschecker.org to confirm that your CNAME is resolving globally.
Some users have reported that the UI silently fails due to caching or browser issues. Try:
You mentioned trying the older admin center — this is good. If the new UI fails, the classic experience sometimes works better for SSL binding.
Power Pages uses Azure CDN under the hood. If the certificate is not binding correctly, the CDN might still be serving the default *.azureedge.net
certificate. This can happen if:
If DNS and certificate are correct, but the UI still fails, it may be a backend propagation delay. Wait 15–30 minutes and try again.
You're encountering a known issue that sometimes affects Power Pages when adding a custom domain with an SSL certificate, particularly when the process gets stuck at the "Create SSL Binding" step. Based on Microsoft's documentation and community reports, here are the most likely causes and best practices to resolve it:
Ensure your .pfx
certificate meets all of the following:
OID = 1.3.6.1.5.5.7.3.1
)
.If any of these are missing, the binding may silently fail.
Even if the TXT record is validated, the CNAME record must also be fully propagated. Use tools like https://dnschecker.org to confirm that your CNAME is resolving globally.
Some users have reported that the UI silently fails due to caching or browser issues. Try:
You mentioned trying the older admin center — this is good. If the new UI fails, the classic experience sometimes works better for SSL binding.
Power Pages uses Azure CDN under the hood. If the certificate is not binding correctly, the CDN might still be serving the default *.azureedge.net
certificate . This can happen if:
If DNS and certificate are correct, but the UI still fails, it may be a backend propagation delay. Wait 15–30 minutes and try again.
Jon Unzueta
18
Fubar
15
Super User 2025 Season 1
Michael E. Gernaey
13
Super User 2025 Season 1