Expiry
The expiry module tracks everything with a date that can take production down: secrets, keys and certificates in Azure Key Vault, client secrets of app registrations, public domain registrations, SQL Server evaluation editions and old service account passwords. It warns early enough for someone to renew them in a normal working day.
What it monitors
| Area | Checks | Why it matters |
|---|---|---|
| Azure Key Vault | Secrets, keys and certificates that expire, read as metadata only, never their values | An expired secret breaks every application that reads it |
| App registrations | Client secrets and certificates of Entra ID app registrations | Service principals used by pipelines and integrations stop signing in |
| Domains | Public domain registration expiry, through RDAP | An expired domain takes down the web site and e-mail at once |
| Licensing | SQL Server edition and evaluation state | An evaluation edition stops after 180 days |
| Service accounts | Password age of Active Directory service accounts, over WinRM (experimental) | Old passwords are a risk, and a forced change breaks services |
Secrets, keys, certificates and app registration credentials follow a 30, 14 and 7 day ladder: a warning at 30 days, a reminder at 14 days (a new notification on the same alert) and critical at 7 days. Domains warn at 60 days and are critical at 14. Everything that expires within 30 days is listed under Expiry and risk on the Overview.
TLS certificates of web endpoints are checked by the synthetic checks. The catalog also lists storage SAS tokens, but the Azure Monitor source does not compute them: Azure cannot list SAS tokens.
Every check, with its rule, cause and action, is in the reference for expiry checks.
Before you begin
- The module is on. The feature
monitoring.expirycovers this module.
| For | You need |
|---|---|
| Key Vault | The Azure Monitor source with Key vaults among its resource types and Key Vault secret expiry selected, and Key Vault Reader (21090545-7ca7-4776-b22c-e363652d74d2) on each vault with Azure RBAC, or an access policy with List on secrets, keys and certificates |
| App registrations | The Azure Monitor source with App registration secret expiry selected, and the Microsoft Graph application permission Application.Read.All with admin consent |
| Domains | A Web endpoint / portal resource with its domain attribute set to the registrable domain, such as ciguapa.example. The Excubius server reaches data.iana.org and the registry's RDAP server on 443. Registries without RDAP are not covered |
| Licensing | The SQL Server monitoring login; the check runs on every SQL Server instance |
| Service accounts | An Entra ID tenant / domain services resource, a read-only domain account over WinRM on a host with the Active Directory PowerShell module, and the check parameter service_accounts_ou set to the organizational unit of the service accounts |
Add a resource
- Key vaults come from the Azure Monitor source. With App registration secret expiry selected, the source also adds a resource for the Entra ID tenant and reports the app registration credentials on it.
- For a domain, add or edit a web endpoint and set its
domain. See Add a resource. - SQL Server instances get the licensing check when you add them.