Governance & hygiene · Auto Tagger
Who created this resource and when. Azure never answers that; Auto Tagger stamps it on every new resource within fifteen minutes.
Deploys as a managed application in your own subscription. No vendor backend, no data egress. Flat monthly fee, billed by Microsoft.
Every cost review and every cleanup starts with the same question, who made this, and Azure cannot answer it once the Activity Log ages out. The feedback request has hundreds of votes and a decade of silence.
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 | read the Activity Log and resource metadata |
| Tag Contributor | write the two tags, nothing else |
Alerts go to no channel; this app writes tags rather than sending alerts. 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.
Who created this resource and when. Azure never answers that; Auto Tagger stamps it on every new resource within fifteen minutes.
Deploy from the Azure Marketplace