What Key Vault renews on its own
Microsoft’s guide to Azure Key Vault certificate renewal puts certificates in three groups, and only two renew by themselves:
- Integrated CAs. Key Vault handles renewal end to end for certificates from its partner CAs, DigiCert and GlobalSign, once the CA is connected to the vault.
- Self-signed certificates. Key Vault can renew these on the schedule in the certificate policy.
- Any other CA. Key Vault does not renew these. It can email the certificate contacts before expiry, but someone has to create a new version, send its certificate signing request (CSR) to the CA and merge the signed certificate back.
Each renewal creates a new version of the certificate with a new identifier. The certificate’s lifetime actions decide when renewal or the email happens.
Why auto renewal does not happen
The usual reasons, based on how renewal works:
- The certificate was imported, or comes from a CA that is not integrated, so there is nothing to renew it automatically.
- The lifetime action is set to email contacts only, or there are no certificate contacts, so the notice goes nowhere.
- The CSR was merged with a different pending request, so the key does not match. Microsoft notes the signed certificate must be merged with the same request that created it.
- The vault renewed the certificate, but the service using it still reads an old version.
Getting the renewed version into use
A new version only helps if the service using the certificate reads it. Azure Application Gateway, for example, polls Key Vault every four hours for a newer version if it references the secret without a version, and disables the listener if it loses access to the vault. A reference that pins a specific version never moves to the renewed one.
So, after each renewal, check that each consumer serves the new certificate, not only that the vault holds it. Our guide to how to stop certificate expiry outages explains why checking the served certificate matters.
Where it gets hard
- Certificates from other CAs. Most organisations have some, and each one is a manual renewal.
- Many vaults. Subscriptions and teams each have their own vaults and contacts.
- Lifetimes. Public certificates are moving toward 47 days, as covered in certificate lifetimes are falling to 200, 100 and 47 days.
How clm.mt handles Key Vault
clm.mt renews the certificate from your chosen CA, imports it into Key Vault as a new version, and on undo disables that version so the previous one is current again.
clm.mt status
Preview for Azure Key Vault. Implemented connectors with contract tests; run a staging pilot on your account first. See the integrations board for every tested scope, and the documentation to plan a pilot.
Other platform guides
- AD CS certificate autoenrollment and auto renewal
- AWS load balancer certificate renewal with ACM
- F5 BIG-IP SSL certificate renewal automation
- FortiGate ACME certificates and automatic renewal
- IIS SSL certificate auto renewal on Windows Server
- Kubernetes certificate management and TLS Secret renewal
- NetScaler ADC SSL certificate renewal and update
- NGINX SSL certificate auto renewal with ACME
- Palo Alto firewall certificate renewal automation