Skip to main content Skip to complementary content

Home > Identity and access > Permission and role review

Permission and role review

Last updated: 2026-11-03

Cadence: Quarterly

Subscription model: All

Roles: Tenant Admin (TA)

Last verified: 2026-09

Initial Recurring
Estimated time 2 hr 1 hr

Benefits:

  • Removes orphaned Tenant Admin assignments
  • Detects custom-role drift and unused assignments
  • Plans migration off deprecated built-in roles before they're removed

Goal

A quarterly deep-review of every Tenant Admin assignment, every custom role, and every Auto-assign toggle complements the monthly audit. This is also when migration off deprecated built-in roles should be planned and executed: the Developer role was deprecated in June 2025 and removed on January 26, 2026—along with the Enable API keys toggle in tenant settings and the api_keys_enabled option in the API keys API—replaced by a custom role with the Manage API keys permission. The Automation Creator role is scheduled for deprecation later in 2026 in favor of new Private automations permissions in User Default settings (administrators can create custom roles using the new permissions or apply them to User Default).

Tasks

Task TA AA DA AuA
Review every Tenant Admin assignment with the security team; remove anyone who no longer needs it (but always retain ≥ 1, ideally ≥ 2) ✓
Review every custom role for permission drift and unused assignments ✓
Review Auto-assign toggles for built-in roles (for example, Data Services Contributor, Private Analytics Content Creator, Shared Space Creator, Steward, AutoML Experiment Contributor, AutoML Deployment Contributor) ✓
Plan migration off any deprecated built-in roles (for example, Developer → custom role with the Manage API keys permission, deprecated June 2025 and removed on January 26, 2026; Automation Creator → new Private automations permissions applied via custom role or User Default) ✓

References

Tags: #quarterly #identity_and_access #roles #custom_roles #deprecation

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!