
In April 2025, the CA/Browser Forum, the industry group of public certification authorities (CAs), browser vendors, and other stakeholders that sets the rules for publicly trusted certificates, approved Ballot SC-081v3. The ballot reduces the maximum lifetime of public TLS certificates from 398 days to 47 days in three phases between 2026 and 2029. It also shortens how long a CA can reuse domain validation, which ultimately means proving control of a domain for nearly every certificate issued. The first phase took effect on March 15, 2026.
Last updated: November 9, 2026
Implementation Timeline
The reduction happens in three phases. Each phase applies to certificates issued on or after the date shown.
- March 15, 2026: 200 days (in effect now)
- March 15, 2027: 100 days
- March 15, 2029: 47 days
Many CAs issue certificates a day or two shorter than the maximum to stay safely within each limit.
Domain Validation Changes
The ballot also shortens how long a CA can reuse validation data, including the following.
- Domain and IP address validation: 398 days before March 15, 2026, then 200 days. It drops to 100 days on March 15, 2027, and to 10 days on March 15, 2029.
- Organization information for OV and EV certificates: 825 days before March 15, 2026, and 398 days after.
For many organizations, the 10-day domain validation window will matter more than the 47-day certificate lifetime. Once it takes effect, domain control must be proven again for nearly every certificate issued, so manual validation steps, such as adding DNS records by hand or responding to validation emails, will no longer be practical.
Why Is This Happening?
Shorter lifetimes address several long-standing problems with publicly trusted certificates, including the following.
- Unreliable revocation: Certificate revocation doesn’t work reliably at internet scale. Shorter lifetimes reduce reliance on it by limiting how long a compromised or misissued certificate remains usable.
- Stale validation data: Shorter reuse periods ensure certificates are issued only to whoever controls the domain today, for example after a domain changes hands.
- Cryptographic agility: Frequent, automated replacement makes it easier to move to new algorithms, which will be essential for the transition to post-quantum cryptography.
This continues a long-term trend. Public certificate lifetimes have already dropped from multiple years to 398 days, and now to 200 days.
Scope
These changes apply only to publicly trusted TLS server certificates. Certificates issued by your own private PKI, such as Microsoft Active Directory Certificate Services (AD CS), are not affected. For workloads accessed only by domain-joined or managed devices, AD CS certificates with autoenrollment may be a simpler option than public certificates. Learn more about enterprise PKI with Microsoft AD CS.
Implications
A 47-day lifetime means at least eight renewals per year for every certificate, and closer to twelve when certificates are renewed about two-thirds of the way through their lifetime, which is common practice. For organizations with hundreds or thousands of public endpoints, manual renewal is no longer feasible. Enrollment, validation, renewal, and deployment must all be automated.
What This Means for Windows Workloads
Many Windows workloads use public TLS certificates, and each one needs a way to install the renewed certificate, not just obtain it. Pay particular attention to the following.
- IIS: Renewed certificates must be bound to each site. simple-acme and Certify The Web update IIS bindings automatically.
- RRAS SSTP: Always On VPN servers using SSTP need the new certificate assigned to the SSTP listener after every renewal. See Always On VPN SSTP and 47-Day Public TLS Certificates for details.
- Remote Desktop: RD Gateway and other Remote Desktop services must be reconfigured to use each new certificate.
- AD FS and Web Application Proxy: The service communications certificate must be updated on every AD FS and Web Application Proxy server in the farm.
- Entra Application Proxy: Certificates for custom domains are uploaded to each application, and there is no built-in renewal, so updates must be scripted with Microsoft Graph. My Update-EntraAppProxyCertificate.ps1 PowerShell script does this from a PFX file. It validates the certificate against each app’s external URL, can update every matching app in the tenant at once with a wildcard or multi-SAN certificate, and returns exit codes for use in scheduled tasks. Install it from the PowerShell Gallery with
Install-Script -Name Update-EntraAppProxyCertificate. - Azure Key Vault: Key Vault renews certificates automatically only when they come from its integrated CAs, DigiCert and GlobalSign. Certificates from other CAs, including ACME CAs such as Let’s Encrypt, require your own automation.
- Load balancers and appliances: Certificates on load balancers and other network appliances need automation too, using the vendor’s API or built-in ACME support.
How to Prepare
Preparing for 47-day certificates involves the following steps.
- Inventory: Find every public certificate, where it’s installed, and who owns it. Certificate Transparency logs are a good starting point.
- Automate with ACME: The Automatic Certificate Management Environment (ACME) protocol is the standard for automated issuance and renewal. Let’s Encrypt, Google Trust Services, and many commercial CAs support it.
- Use DNS validation: DNS validation works for wildcard certificates and for servers that aren’t reachable from the internet. Use a DNS provider with an API, or delegate the _acme-challenge record with a CNAME so automation doesn’t need full access to your DNS zone.
- Use ACME Renewal Information (ARI): ARI lets the CA tell clients when to renew, including early renewal ahead of a mass revocation event. Choose clients that support it.
- Automate deployment: Obtaining a certificate is only half the job. Installing it, updating bindings, and restarting services must be automated as well.
- Monitor: Alert on approaching expirations and failed renewals so a broken process is caught before a certificate expires.
- Remove certificate pinning: Applications that pin a specific certificate will break with frequent renewals. Pin to a CA or remove pinning entirely.
Automation Tools for Windows
Several tools automate public TLS certificates on Windows, including the following.
- simple-acme: An ACME client for Windows and the backward-compatible, drop-in replacement for win-acme, built by the same developer. It installs certificates in IIS automatically and supports scripted installation for other workloads.
- Certify The Web: Certify Certificate Manager is a graphical ACME client for Windows with built-in IIS integration and deployment tasks for other services. The free Community Edition manages up to five certificates and is intended for evaluation, and licensed editions are available for production use.
- Posh-ACME: A PowerShell module ACME client that’s ideal for scripted, unattended automation, with DNS validation plugins for many DNS providers.
- CertKit: A certificate lifecycle management service that discovers, issues, renews, and deploys certificates. Its agent automatically configures IIS, Remote Desktop, DirectAccess, and RRAS SSTP.
Summary
Public TLS certificate lifetimes are already down to 200 days. They drop to 100 days in March 2027 and reach 47 days in March 2029, when domain validation will be required for nearly every certificate. Manual processes won’t keep up. Now is the time to inventory your public certificates and automate their enrollment, validation, renewal, and deployment.
Additional Information
Introduce Schedule of Reducing Validity and Data Reuse Periods (CA/B Forum Ballot SC-081v3)
Automatic Certificate Management Environment (RFC 8555)
ACME Renewal Information (ARI) Extension (RFC 9773)
Always On VPN SSTP and 47-Day Public TLS Certificates
Update-EntraAppProxyCertificate PowerShell Script (GitHub)
Enterprise PKI with Microsoft Active Directory Certificate Services
Get Help with TLS Certificate Automation
I help organizations automate public TLS certificates across Windows, Azure, and network infrastructure. Tell me about your environment, and I’ll follow up, typically within one business day.









