How to monitor Azure Key Vault expiry across many client tenants

Secrets, keys and certificates in Key Vault expire silently. Here is what Azure gives you for free, where it stops, and how to cover every vault across every client tenant you manage.

An expired Key Vault secret rarely fails loudly. An app keeps running until the next time it reaches for the secret, and then a payment integration, a nightly sync or a customer login stops working. If you manage Azure for other people, that outage arrives as a support call, and the first question is usually "why didn't you know?"

This guide covers what Azure already gives you for free, where each option stops, and what it takes to watch every vault in every client tenant you look after.

What actually expires in Key Vault

Public TLS certificates are also getting shorter-lived every year. Under CA/Browser Forum Ballot SC-081v3, the longest a publicly trusted certificate may be valid is 200 days for certificates issued from 15 March 2026, 100 days from 15 March 2027, and 47 days from 15 March 2029. That applies to certificates Key Vault obtains from an integrated public CA too. Where renewal is automated, that is a smaller problem. Where a person renews by hand, the same certificate now has to be renewed two or more times a year, and every renewal is a chance to miss one.

Because the expiry date on secrets and keys is optional, an inventory has to cover items that have no expiry too. Those are usually the long-lived credentials nobody remembers creating.

What Azure gives you for free

1. Event Grid near-expiry events

Key Vault publishes SecretNearExpiry and CertificateNearExpiry events, which Microsoft documents as triggered 30 days before the expiration date. For keys, the timing of KeyNearExpiry comes from the key rotation policy. To use any of them, you subscribe to the events on each vault and route them to a handler, such as a Logic App, an Azure Function or your own webhook.

Where it stops: you get one documented warning window, you build and run the handler yourself, and you repeat the subscription on every vault in every tenant. A vault created next month is uncovered until someone remembers to wire it up.

2. Certificate contacts and lifetime actions

A certificate policy can email the vault's certificate contacts at a set number of days before expiry, or at a percentage of the certificate's lifetime. It can also auto-renew certificates from an integrated issuer.

Where it stops: it covers certificates only, not secrets or keys. The contacts are set per vault, and they are usually whoever created the vault, which may not be anyone on your team.

3. Azure Policy

Built-in definitions such as "Key Vault secrets should have an expiration date", "Secrets should have more than the specified number of days before expiration" and "Certificates should not expire within the specified number of days" can audit or deny.

Where it stops: their effects are Audit, Deny or Disabled. Policy reports compliance; it doesn't warn anyone on a schedule. It is also a per-tenant assignment you maintain in each client.

4. Microsoft Entra recommendations

For app registrations and service principals, rather than Key Vault, Entra has recommendations such as "Renew expiring application credentials". Microsoft lists them as Preview. They look 30 days ahead and email the Application Administrator role when a new recommendation is generated.

The MSP problem: Lighthouse can't see secrets

If you manage clients through Azure Lighthouse, it is natural to assume you can inventory their vaults from your own tenant. You can see the vaults, but not what's in them. Microsoft's documentation says Lighthouse doesn't support requests handled by an instance of a resource type, such as Key Vault secrets access, and only supports requests handled by Azure Resource Manager. Listing secrets, keys and certificates is a data-plane request, so each client tenant needs its own read access.

A checklist that holds up across 50 tenants

  1. Inventory everything, including items with no expiry date. Those are the risky ones.
  2. Read metadata, never values. Listing properties needs read permission on metadata only. Nothing that monitors expiry needs to read a secret's value.
  3. Warn early and more than once. A single 30-day notice lands during someone's holiday. A ladder of reminders that gets more urgent as the date nears gets acted on.
  4. Send the warning to whoever will fix it, such as a shared mailbox, a Teams or Slack channel or your PSA, rather than to whoever created the vault.
  5. Cover new vaults automatically. Anything that has to be wired up per vault will miss one eventually.
  6. See all clients in one list, sorted by what expires first.

How CloudMonitor does it

CloudMonitor connects read-only to each client's Azure tenant, using the Reader role on the subscription and Key Vault Reader on the vaults you want watched. Key Vault Reader is an Azure RBAC role, so it only covers vaults that use the RBAC permission model, which is the default for vaults created with Key Vault API version 2026-02-01 or later. A vault still on legacy access policies needs a policy that allows listing secrets, keys and certificates instead, and CloudMonitor flags vaults still on access policies. It lists the properties of every secret, key and certificate, including the ones with no expiry, and never reads a secret's value. It finds vaults by listing each connected subscription once a day. If you grant Key Vault Reader at the subscription rather than on individual vaults, a vault created later is picked up on the next daily scan without anyone wiring it in.

Alerts go out at 90, 60, 30, 14, 7 and 1 day before expiry, once at each step, and once more when an item has expired, by email, Slack, Microsoft Teams, Discord, PagerDuty or a webhook. You can turn each alert type on or off. For MSPs, a client roll-up lists every client account your team has been given access to, worst first, with counts of what is expiring within 30 days and what has already expired. Access is granted per person and per client, and every change is recorded.

See how to connect Azure and how pricing works. A secret, key or certificate is a supporting resource, five of which make one billing unit.

Microsoft behavior described here was checked against learn.microsoft.com on 3 October 2026: Key Vault Event Grid schema, Key Vault certificate lifetime actions, the Key Vault Azure Policy reference, Microsoft Entra recommendations, and Azure Lighthouse's cross-tenant limitations. On 4 October 2026 we re-checked the Event Grid overview (still 30 days), the Entra recommendations table (both credential-expiry recommendations still Preview, emailing the Application Administrator role) and Key Vault's RBAC default, and read the certificate schedule in the CA/Browser Forum Baseline Requirements.

← Back to all posts