web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Pages
Unanswered

SSL Binding Issue

(0) ShareShare
ReportReport
Posted on by 42
Dear Community, 
 
I'd like to ask for help regarding our Power Pages custom domain where we've successfully provisioned our password-protected SSL certificate and the host name is validated through its TXT on our end. Like with this forum post, Add a custom domain stuck at "Create SSL Binding", we're stuck at the SSL binding step. However, we've already checked and our host name is exactly what is typewritten on our end. In the forum post, he noticed that his host name was typed incorrectly and it still passed through and did not produce an error. 
 
We refreshed the page, and clicking on the pencil icon in the custom domain editor, trying to bind the set host name and SSL certificate still isn't pushing through. The page just refreshes and does nothing. What is happening?
 
Could anyone please help us out as we're already taking a lot of time just trying to figure out this final step prior release.
 
EDIT: 
We've already tried it with the previous version of admin center rather than the new version but it still did not bind.
 
Categories:
I have the same question (0)
  • Suggested answer
    Jon Unzueta Profile Picture
    1,827 Super User 2025 Season 2 on at
     

    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:


    Checklist to Resolve "Create SSL Binding" Stuck Issue

    🔹 1. Verify SSL Certificate Requirements

    Ensure your .pfx certificate meets all of the following:

    • Signed by a trusted certificate authority.
    • Exported as a password-protected PFX file.
    • Contains a private key (2048 bits or more).
    • Includes all intermediate certificates in the chain.
    • Uses SHA2 (not SHA1).
    • Encrypted with TripleDES (Power Pages does not support AES-256).
    • Contains Extended Key Usage for server authentication (OID = 1.3.6.1.5.5.7.3.1)  .

    If any of these are missing, the binding may silently fail.


    🔹 2. Check DNS Propagation

    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.


    🔹 3. Try a Different Browser or Clear Cache

    Some users have reported that the UI silently fails due to caching or browser issues. Try:

    • Using Incognito/Private mode.
    • Switching to a different browser (e.g., Edge if using Chrome).
    • Clearing cookies and cache.

    🔹 4. Use the Classic Admin Center (Fallback)

    You mentioned trying the older admin center — this is good. If the new UI fails, the classic experience sometimes works better for SSL binding.


    🔹 5. Check for Azure CDN Conflicts

    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:

    • The binding was not completed.
    • The certificate is not correctly associated with the CDN endpoint.

    🔹 6. Wait and Retry

    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.


    🛠️ If All Else Fails

    • Delete and re-add the custom domain and certificate.
    • Open a Microsoft support ticket via the Power Platform Admin Center.
     
    🏷️ Tag me if you have any further questions or if the issue persists.
    ✅ Click "Accept as Solution" if my post helped resolve your issue—it helps others facing similar problems.
    ❤️ Give it a Like if you found the approach useful in any way.
  • Suggested answer
    Jon Unzueta Profile Picture
    1,827 Super User 2025 Season 2 on at
     

    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:


    Checklist to Resolve "Create SSL Binding" Stuck Issue

    🔹 1. Verify SSL Certificate Requirements

    Ensure your .pfx certificate meets all of the following:

    • Signed by a trusted certificate authority.
    • Exported as a password-protected PFX file.
    • Contains a private key (2048 bits or more).
    • Includes all intermediate certificates in the chain.
    • Uses SHA2 (not SHA1).
    • Encrypted with TripleDES (Power Pages does not support AES-256).
    • Contains Extended Key Usage for server authentication (OID = 1.3.6.1.5.5.7.3.1)  .

    If any of these are missing, the binding may silently fail.


    🔹 2. Check DNS Propagation

    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.


    🔹 3. Try a Different Browser or Clear Cache

    Some users have reported that the UI silently fails due to caching or browser issues. Try:

    • Using Incognito/Private mode.
    • Switching to a different browser (e.g., Edge if using Chrome).
    • Clearing cookies and cache.

    🔹 4. Use the Classic Admin Center (Fallback)

    You mentioned trying the older admin center — this is good. If the new UI fails, the classic experience sometimes works better for SSL binding.


    🔹 5. Check for Azure CDN Conflicts

    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:

    • The binding was not completed.
    • The certificate is not correctly associated with the CDN endpoint.

    🔹 6. Wait and Retry

    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.


    If All Else Fails

    • Delete and re-add the custom domain and certificate.
    • Open a Microsoft support ticket via the Power Platform Admin Center.
     
    🏷️ Tag me if you have any further questions or if the issue persists.
    ✅ Click "Accept as Solution" if my post helped resolve your issue—it helps others facing similar problems.
    ❤️ Give it a Like if you found the approach useful in any way.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Ajay Kumar Gannamaneni – Community Spotlight

We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…

Leaderboard > Power Pages

#1
Jerry-IN Profile Picture

Jerry-IN 71

#2
Fubar Profile Picture

Fubar 62 Super User 2025 Season 2

#3
sannavajjala87 Profile Picture

sannavajjala87 31

Last 30 days Overall leaderboard