Not able to create any managed ssl certificate in managed app hosted on linux,

Tarek Alhamad 25 Reputation points
2025-08-30T09:20:57.27+00:00

Hi
I have a problem that I am not able to create any ssl certificate on my managed app service plan hosted on linux, Premium v3 P1mv3 (Change). I have one domain, main site that the certificate was generated successfully for it, but when I try to add any of the sub domains such as www.* the certificate takes so long-time during creation and eventually fails with error code
Create Managed Certificate | Failed | Pending certificate expired., Can you please support, I tried everything including purchasing azure support plan to contact support and still I cannot do that,

TimeStamp 8/29/2025 11:07:24 PM
TimeStamp 8/29/2025 11:07:24 PM
Certificate Name portal.***.com
Cause Create free cert failed
Recommended Action Please try again
Azure Managed Applications
Azure Managed Applications
An Azure service that enables managed service providers, independent software vendors, and enterprise IT teams to deliver turnkey solutions through the Azure Marketplace or service catalog.
{count} vote

Accepted answer
  1. Suwarna S Kale 4,421 Reputation points
    2025-08-30T12:35:09.41+00:00

    Hello Tarek Alhamad,

    Thank you for posting your question in the Microsoft Q&A forum. 

    This recurring failure during the creation of a managed certificate for your subdomain, specifically the "Pending certificate expired" error, typically indicates a problem with the domain validation process managed by Azure's certificate authority (CA), Let's Encrypt. The issue often stems from DNS configuration or validation challenges that prevent the CA from successfully verifying your domain ownership before the temporary validation token expires. 

    Firstly, ensure that your subdomain (e.g., www) has a correct CNAME record pointing to your Azure App Service. The record must be properly propagated and resolvable globally, as Let's Encrypt’s validation servers might fail to resolve it due to delays or misconfigurations. Additionally, if your domain uses any DNSSEC, ensure it is correctly configured, as validation failures there can also disrupt the process. 

    Secondly, review your App Service configuration to confirm that the subdomain is explicitly listed as a custom domain within your App Service settings. Azure requires the domain to be bound to the App Service before it can issue a certificate, and any discrepancy here can cause the validation to hang and eventually time out. 

    If these steps do not resolve the issue, consider creating the certificate manually using a different CA, such as via App Service Certificates (which integrates with Key Vault) or a third-party certificate imported into Azure. This bypasses the automated validation challenges while still securing your subdomain. Given you have a support plan, escalate the case with Azure support, providing detailed logs and DNS configurations, as they can investigate backend validation attempts and identify specific failures. 

     

    Please, let me know the response helps answer your question? If the above answer helped, please do not forget to "Accept Answer" as this may help other community members to refer the info if facing a similar issue. 🙂 


1 additional answer

Sort by: Most helpful
  1. Tarek Alhamad 25 Reputation points
    2025-08-31T22:29:18.2533333+00:00

    My guess it was only a hidden limit that microsoft enforce on the number of certificates a subscription can have. In my case, I had a windows app plan with 5 certificates. I decided to switch to linux machine and used the same urls and same dns configuration for the same apps and kept trying for two days and nothing happened. Only when I open the support ticket and start typing here and on twitter, suddenly everything started working smooth. So it could be that or it could be delays or an intermediate bug, I can’t really tell.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.