CloudMonitor's real competitor is free. Azure already has several ways to learn that something in Key Vault is about to expire. If one of them covers you, use it. This post sets out where each one fits.
Side by side
| Event Grid near-expiry events | Certificate contacts | Azure Policy | CloudMonitor | |
|---|---|---|---|---|
| Covers | Secrets and certificates (30 days); keys (timing set by rotation policy) | Certificates only | Secrets, keys, certificates | Secrets, keys, certificates, including items with no expiry |
| Warns you | One documented window | At a set day count or lifetime percentage | Doesn't alert: audit or deny | 90, 60, 30, 14, 7 and 1 day out, once each, and on expiry |
| Setup | Event subscription plus your own handler, per vault | Contacts and policy per vault | Assignment per scope | One read-only connection per tenant |
| Delivery | Whatever your handler does | Email to the vault's contacts | Compliance view | Email, Slack, Teams, Discord, PagerDuty, webhook |
| Across many client tenants | Rebuilt in each | Rebuilt in each | Assigned in each | One roll-up, worst first |
| Cost | Free, plus the handler's running cost | Free | Free | Paid; see pricing |
When the built-in options are enough
- You run one tenant and a handful of vaults, and someone owns a Logic App that turns the Event Grid event into a ticket.
- Your exposure is mainly certificates from an integrated issuer, which Key Vault can auto-renew.
- You mainly want to enforce hygiene, for example that every secret has an expiry date. Azure Policy with Deny does that well, and you should use it either way.
When they stop being enough
- Many tenants. Each option is configured inside each client tenant. With 30 clients, that is 30 sets of subscriptions, handlers and contact lists to keep correct. Azure Lighthouse doesn't help with the inventory: Microsoft documents that it doesn't support Key Vault secrets access, only Azure Resource Manager requests.
- New vaults. A vault created after the wiring was done is silent until someone notices.
- Secrets with no expiry date. Near-expiry events need an expiry date to fire on. An inventory shows you the credentials that have none.
- One warning is easy to miss. A single notice can land on a holiday or in a mailbox nobody reads.
Use both
They don't conflict. Keep Azure Policy denying secrets with no expiry date, keep certificate auto-renewal where you have it, and use CloudMonitor as the one cross-tenant list and reminder ladder that covers whatever slips through. CloudMonitor reads metadata only, with the Reader and Key Vault Reader roles, and never reads a secret's value.
Microsoft behavior was checked against learn.microsoft.com on 3 October 2026: Key Vault Event Grid event schema and overview, Key Vault certificate lifetime actions, the Key Vault Azure Policy reference, and Azure Lighthouse's cross-tenant limitations. Microsoft changes these features over time, so check the current docs before relying on a detail.