https://catalogartifact.azureedge.net/publicartifacts/katabarwalabs.rbac-janitor-f9e4deab-ac97-4122-b2a9-a5ceee5c3f7a/image3_logo216.png
RBAC Janitor — Orphaned Role Assignment Cleanup
بواسطة Katabarwa Labs Inc.
Just a moment, logging you in...
Just a moment, logging you in...
Find and clean orphaned "Identity not found" Azure role assignments — with a hard fail-safe against
When a user, group, or service principal is deleted, its Azure role assignments don't disappear — they linger as "Identity not found" entries that clutter access reviews and count toward the hard 4,000-assignment-per-subscription limit. Azure has no built-in bulk cleanup. RBAC Janitor provides one, safely.
WHAT IT DOES
RBAC Janitor deploys into your own Azure subscription as a managed application. Every day it lists role assignments, resolves each principal via Microsoft Graph, flags the orphaned ones, warns as you approach the 4,000-assignment limit, and — only if you explicitly enable it — removes them.
WHY IT IS SAFE
Deletion ships OFF: the app is report-only and dry-run by default. It is fail-closed — a Graph error never causes a deletion (unverified principals are quarantined, never treated as orphaned), and an orphan-fraction circuit breaker aborts a run that looks wrong. Management-group-inherited and cross-tenant assignments are excluded from cleanup.
WHO IT IS FOR
Identity and platform teams and MSPs managing subscriptions where deleted principals accumulate and the assignment limit is a real risk.
SETUP
Deploy from the marketplace, paste a Teams webhook URL, and run one script to grant read-only Reader plus Directory.Read.All. Add User Access Administrator and flip the flags only when you have reviewed the dry-run report.
لمحة سريعة
https://catalogartifact.azureedge.net/publicartifacts/katabarwalabs.rbac-janitor-f9e4deab-ac97-4122-b2a9-a5ceee5c3f7a/image4_shot1.png