October 2025 Update: App Service Managed Certificates Support for Non-Publicly Accessible Sites
YutangLin summarizes the latest Azure App Service Managed Certificates (ASMC) changes as of October 2025, emphasizing new support for non-publicly accessible sites and key requirements for successful certificate issuance.
October 2025 Update: App Service Managed Certificates Support for Non-Publicly Accessible Sites
Author: YutangLin
This article presents the recent updates to Azure App Service Managed Certificates (ASMC), building on the prior Tech Community post ‘Important Changes to App Service Managed Certificates: Is Your Certificate Affected?’. It explains how recent changes affect certificate issuance, what exceptions exist, and what site administrators need to know to ensure smooth certificate validation and renewal.
Key Changes Since July and October 2025
- HTTP Token Validation Is Mandatory:
    
- Since July 2025, all ASMC certificate issuance and renewals require HTTP token validation.
 - DigiCert must reach the endpoint 
https://<hostname>/.well-known/pki-validation/fileauth.txtwhere App Service automatically places a domain validation token. - If this endpoint is inaccessible, domain validation fails.
 
 - Support for Non-Publicly Accessible Sites (October/November 2025):
    
- App Service now allows DigiCert’s requests to the validation endpoint even if public access to the site is blocked.
 - DigiCert’s request terminates at the App Service front end; the application itself is not exposed.
 - No need to specifically allow DigiCert’s IP addresses anymore.
 
 
Requirements and Exceptions
- A public DNS record remains required for domain validation and issuance.
 - Unsupported scenarios:
    
- Sites on private endpoints with custom domains using only private DNS (no public DNS record).
 - Sites configured as “Nested” or “External” endpoints behind Azure Traffic Manager (only “Azure” endpoints are supported).
 - Certificates for domains ending in 
*.trafficmanager.net. 
 
Validation and Testing
- Site owners can test if their configuration supports ASMC by attempting certificate issuance. Success with an initial request means renewals are also likely to work, assuming all requirements are maintained.
 
Practical Implications
- Security:
    
- The update improves security by enabling certificate validation without requiring the entire application to be public, adhering to access restrictions while meeting operational requirements.
 
 - Operational Ease:
    
- Customers no longer need to manage DigiCert IP allowlists.
 - Exception handling for complex traffic management scenarios helps clarify required configurations.
 
 
Summary Table
| Scenario | Supported for ASMC? | 
|---|---|
| Public site with DNS | Yes | 
| Non-public site with public DNS | Yes | 
| Private endpoint, custom domain without public DNS | No | 
| Nested or External endpoints behind Traffic Manager | No | 
| Domains ending in *.trafficmanager.net | No | 
References and Further Reading
- Important Changes to App Service Managed Certificates: Is Your Certificate Affected?
 - Inside the Azure App Service Architecture
 
Updated Nov 01, 2025
This post appeared first on “Microsoft Tech Community”. Read the entire article here