Azure AI + machine learning built-in role
Cognitive Services Metrics Advisor Administrator
Formerly provided full Metrics Advisor project and system-configuration access through resource read Actions and Metrics Advisor DataActions. Azure AI Metrics Advisor retired on May 18, 2026. This overlay is retained only for migration and access cleanup; it is not a recommendation for a new assignment.
Role-definition permissions are imported from Microsoft Learn. Practical scope, use cases, prerequisites, best practices, security considerations, assignment guidance, and relationships have been reviewed against the official sources below.
Role definition ID: cb43c632-a144-4ec5-977c-e80c4affc34a
Control-plane actions (1)
Microsoft.CognitiveServices/*/read
Data-plane actions (1)
Microsoft.CognitiveServices/accounts/MetricsAdvisor/*
Excluded actions (0)
None
Assignable scopes (1)
/
Practical scope
Azure role assignments apply at the selected scope and are inherited by child scopes. Use the narrowest supported resource, resource-group, subscription, or management-group scope that contains the intended resources. Existing assignments for this retired service must be removed at the scope where they were created; an inherited assignment cannot be removed from a child resource.
Common use cases (2)
- Inventory principals and automation that still hold this legacy role before migration or cleanup begins. Migrate anomaly detection and analysis to a supported alternative documented by Microsoft, such as Azure Monitor or Microsoft Fabric, and select roles from that product's current access model.
- Remove stale direct or inherited assignments after the replacement workload and rollback plan have been verified.
Prerequisites (2)
- Identify the legacy resource, every direct and inherited assignment, and the principal or group that received the role.
- The cleanup administrator needs Microsoft.Authorization/roleAssignments/delete at the scope where each assignment was created.
Best practices (4)
- Do not create a new assignment for this retired service.
- Migrate anomaly detection and analysis to a supported alternative documented by Microsoft, such as Azure Monitor or Microsoft Fabric, and select roles from that product's current access model.
- Select roles for the replacement service from its current product documentation rather than carrying this legacy role forward.
- Remove assignments at their originating scopes after migration validation and retain an auditable record of the cleanup.
Security considerations (2)
- The legacy role could change data feeds, anomaly configurations, alerts, and system-level project settings.
- A stale parent-scope assignment remains inherited by child resources until it is removed at the originating scope.
Assignment guidance
Do not assign this role. Locate existing assignments in Access control (IAM), confirm the retired workload no longer depends on them, and remove each assignment at its originating scope. Reassess access separately for the replacement service.
Editorial sources (6)
- Azure built-in roles for AI + machine learning - Azure RBAC | Microsoft Learn →
Supports: Description, Security considerations. Retrieved 2026-07-17.
- Understand scope for Azure RBAC | Microsoft Learn →
Supports: Practical scope, Assignment guidance. Retrieved 2026-07-17.
- Best practices for Azure RBAC | Microsoft Learn →
Supports: Best practices. Retrieved 2026-07-17.
- Understand Azure role definitions - Azure RBAC | Microsoft Learn →
Supports: Security considerations. Retrieved 2026-07-17.
- Remove Azure role assignments - Azure RBAC | Microsoft Learn →
Supports: Practical scope, Common use cases, Prerequisites, Best practices, Assignment guidance. Retrieved 2026-07-17.
- What is the Azure AI Metrics Advisor service? - Azure AI services | Microsoft Learn →
Supports: Description, Common use cases, Best practices, Security considerations, Assignment guidance. Retrieved 2026-07-17.