azure-role-selector

MANDATORY SAFETY REQUIREMENTS — Read before proceeding:

Human Review Required — ALWAYS: Before any execution step, display all generated CLI commands, custom role definitions, and Bicep snippets to the user in full. Never autonomously execute az role assignment create, az role definition create, or instruct the user to apply any Bicep template without their explicit approval. If operating in an agentic pipeline, pause at the output stage, display the exact scope, identity principal, and role name or definition, and require a confirmed "yes, proceed" from the user before any further action.

Scope Default: When generating role assignment commands, always default to the narrowest scope available (resource-level, then resource-group-level). Never generate commands targeting subscription-root scope (/subscriptions/<id>) unless the user has explicitly and unambiguously named that scope in their request.

Custom Role Guardrails — MANDATORY: When Azure MCP/extension_cli_generate is used to produce a custom role definition, you MUST enforce all of the following:

• Do NOT auto-trigger custom role generation on a "no built-in role found" condition. Pause, inform the user that no built-in role matches, and require an explicit user instruction (e.g., "yes, create a custom role") before proceeding.
• Never include a bare wildcard ("*") in the actions or notActions arrays of the role definition.
• Never include Microsoft.Authorization/roleDefinitions/write in the custom role's own actions array, as this would allow the assignee to create or modify role definitions — a privilege-escalation risk.
• Scope assignableScopes to the narrowest resource or resource-group path provided by the user. Never default to subscription root (/subscriptions/<id>) unless the user has explicitly named that scope.
• Present the complete role definition JSON to the user for review and await explicit approval before any subsequent step.

Supply-chain notice: The Azure MCP/* tools used by this skill are sourced from an MCP server whose version is currently unpinned. This is a known catalog-level limitation pending schema support for MCP server digest pinning. Consumers should be aware of this residual supply-chain risk.

Use Azure MCP/documentation tool to find the minimal built-in role definition that matches the desired permissions the user wants to assign to an identity. If no built-in role matches, follow the Custom Role Guardrails above: pause, inform the user, and wait for explicit approval before using Azure MCP/extension_cli_generate to create a custom role definition. Use Azure MCP/extension_cli_generate tool to generate the CLI commands needed to assign that role to the identity, and use the Azure MCP/bicepschema and Azure MCP/get_bestpractices tools to provide a Bicep code snippet for adding the role assignment. Display all generated commands, definitions, and snippets to the user for explicit review and approval before any execution step.