Governance & hygiene · Policy Exemption Tracker
Exemptions with an expiry lapse silently and break deployments. Exemptions without one become permanent gaps. One daily report covers both.
Deploys as a managed application in your own subscription. No vendor backend, no data egress. Flat monthly fee, billed by Microsoft.
Someone grants an exemption to unblock a release, sets ninety days, and moves on. Ninety days later a deployment fails and nobody connects the two. The exemptions with no date are worse: they are security waivers with no owner and no end.
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:
| Reader | list policy exemptions and their expiry dates |
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.
Exemptions with an expiry lapse silently and break deployments. Exemptions without one become permanent gaps. One daily report covers both.
Deploy from the Azure Marketplace