Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
Hello @Nasir Ahmed
Thank you for your detailed follow-up and for referencing the official documentation.
Based on the latest updates to App Service Managed Certificates (ASMC), the behavior you’re observing can be clarified as follows:
Cloudflare-proxied CNAME is not an officially unsupported scenario for ASMC. Current Microsoft documentation does not list Cloudflare, DNS proxying, or CDN-fronted domains as unsupported for either certificate issuance or renewal.
What changed (July–November 2025 updates):
- From July 28, 2025, ASMC uses HTTP token validation instead of relying solely on DNS validation
- From November 2025, validation requests from DigiCert are handled directly by the App Service front-end layer, not your app
- Validation is performed via:
https://<your-domain>/.well-known/pki-validation/...
Implications for Cloudflare-proxied domains:
- Since validation is now HTTP-based and handled at the platform level, Cloudflare proxying (orange cloud) should not block certificate issuance or renewal, as long as:
- The domain publicly resolves
- HTTPS traffic can reach Azure App Service endpoints
- The earlier issue you observed (CNAME validation failing when proxied) is tied to the custom domain verification step in App Service, not the ASMC issuance/renewal process itself
- The domain publicly resolves
Regarding renewals:
- If the certificate was successfully issued under the new validation model and all requirements remain satisfied, automatic renewal should continue to work, even with Cloudflare proxying enabled.
Reference:
https://techcommunity.microsoft.com/blog/appsonazureblog/important-changes-to-app-service-managed-certificates-is-your-certificate-affect/4435193
If the answer is helpful, Please do click "Accept the answer” and Yes, this can be beneficial to other community members.
If you have any other questions, let me know in the "comments" and I would be happy to help you