Azure Networking built-in role

Azure Front Door Profile Reader

Reads Azure Front Door Standard and Premium profiles and their endpoints without Microsoft.Cdn profile write permissions. The role definition also grants deployment and classic alert-rule wildcards and lists additional Microsoft.Cdn Actions whose operation descriptions are blank. It has no DataActions.

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: 662802e2-50f6-46b0-aed2-e834bacc6d12

Control-plane actions (17)

Data-plane actions (0)

None — this role grants no data-plane (data access) actions.

Excluded actions (0)

None

Assignable scopes (1)

Practical scope

The definition is assignable throughout the Azure hierarchy. Assignments are effective at the selected scope and inherited by child resources. At resource-group, subscription, or management-group scope, the deployment and classic alert-rule Actions are not confined to a single Front Door profile.

Common use cases (2)

Prerequisites (2)

Best practices (3)

Security considerations (3)

Assignment guidance

Use Azure Front Door Profile Reader for principals that must inspect Standard or Premium profiles and endpoints without changing Microsoft.Cdn profile resources. Keep the scope to the profile or its dedicated resource group and explicitly review the ancillary deployment and alert permissions before approval.

Related roles (1)

Common questions

When should I assign the Azure Front Door Profile Reader Azure role?

Assign Azure Front Door Profile Reader when you need to: Inspect the endpoints, routes, domains, origin groups, and security-policy associations configured in a Front Door Standard or Premium profile without granting Microsoft.Cdn profile writes.; and Review a Front Door profile and its child endpoints as a read-only Front Door operator or auditor.. Practical scope: The definition is assignable throughout the Azure hierarchy. Assignments are effective at the selected scope and inherited by child resources. At resource-group, subscription, or management-group scope, the deployment and classic alert-rule Actions are not confined to a single Front Door profile.

What permissions does the Azure Front Door Profile Reader Azure role grant?

The role definition grants 17 combined control-plane and data-plane actions. Representative operations include: Microsoft.Authorization/*/read; Microsoft.Cdn/edgenodes/read; Microsoft.Cdn/operationresults/*; Microsoft.Cdn/profiles/*/read; Microsoft.Insights/alertRules/*; and Microsoft.Resources/deployments/*. Review the permission sections above for the complete definition and exclusions.

What are the security risks of the Azure Front Door Profile Reader Azure role?

Key considerations when assigning Azure Front Door Profile Reader: Profile reads expose delivery topology, origins, routes, custom domains, WAF associations, and other configuration relevant to application security.; The role includes wildcard deployment and classic-alert Actions even though it cannot write Microsoft.Cdn profile resources.; and It has no DataActions and does not itself grant access to origin application data or customer traffic.. Follow the assignment guidance above and use the narrowest practical scope.

Editorial sources (5)

Official Microsoft Learn documentation →