Secrets & certificates · Secret Sentinel
Every app registration in your tenant, every client secret and certificate, one Teams alert before any of them expires. Runs in your own tenant.
Deploys as a managed application in your own subscription. No vendor backend, no data egress. Flat monthly fee, billed by Microsoft.
An expired client secret takes an integration down silently, and the first sign is usually a failing pipeline or a support ticket. Entra shows every expiry date on the app registration blade and does nothing with it. The feedback request for native alerting has been open for years with hundreds of votes.
A serverless function on a schedule, with a system-assigned managed identity, deployed into your subscription by the Azure Marketplace. Roles are granted by you after deployment with the one-line script in the package, so nothing runs until you say so. Every role it asks for, and why:
| Microsoft Graph Application.Read.All | read app registrations and their credential metadata |
Alerts go to the Teams webhook you configure. Nothing is sent anywhere else.
No. The function runs in your subscription and writes only to your configured alert destination. Katabarwa Labs operates no backend and receives nothing.
A flat monthly fee on your Azure bill through the Marketplace, plus the small consumption cost of the function itself. No per-resource or per-user pricing.
Delete the managed application from the Azure portal. Its resource group and identity go with it, and any role you granted can be removed the same way.
support@llmgraph.ai, or the support page.
Every app registration in your tenant, every client secret and certificate, one Teams alert before any of them expires. Runs in your own tenant.
Deploy from the Azure Marketplace