An Azure service that provides fine-grained access management for Azure resources, enabling you to grant users only the rights they need to perform their jobs.
Hello @Joel Rueda Gonzalez
Your custom role already includes most of the data-plane permissions required to query pipeline and activity runs. If users can trigger pipelines but Monitor > Pipeline runs doesn't render, the issue is often related to additional ARM read permissions that Azure Data Factory Studio depends on rather than the pipeline run APIs themselves.
A few things I'd recommend checking:
- Compare your custom role with the built-in Data Factory Contributor role to identify any missing */read permissions that the Studio UI relies on. The built-in role contains several read actions beyond pipeline execution APIs.
- Ensure the role includes read access for child resources that the monitoring experience queries, such as factory-level metadata and monitoring resources.
- Use your browser's Developer Tools (F12) > Network tab while opening Monitor > Pipeline runs. Look for any requests returning 403 Forbidden or 401 Unauthorized. The failed request usually identifies the exact missing ARM action.
- Verify that no Deny Assignments, Azure Policy, or Conditional Access policies are preventing access, even if the RBAC role appears correct.
Could you also confirm:
- Does the page show "Access denied", remain blank, or fail with another error?
- Are there any 403 responses in the browser's Network tab? If so, which REST endpoint is returning the error?
That information will help determine whether this is a missing RBAC permission or a UI dependency within Azure Data Factory Studio.
Please "Accept the Answer" if this information helped you. This will help us and others in the community as well.