Azure Management and governance built-in role

Reservations Reader

Reads reservation orders and reservations at the tenant-level Microsoft.Capacity provider scope. It cannot purchase, exchange, refund, split, merge, renew, or change reservation scope and 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: 582fc458-8989-419f-a480-75249bc5db7e

Control-plane actions (2)

Data-plane actions (0)

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

Excluded actions (0)

None

Assignable scopes (1)

Practical scope

The built-in role is assignable only at `/providers/Microsoft.Capacity`, a tenant/provider scope rather than a management group, subscription, resource group, or resource. It provides read access to all reservations in the tenant.

Common use cases (2)

Prerequisites (2)

Best practices (2)

Security considerations (2)

Assignment guidance

Assign at `/providers/Microsoft.Capacity` only to principals authorized for tenant-wide reservation visibility. Use Reservation Purchaser separately for approved purchasing.

Related roles (1)

Common questions

When should I assign the Reservations Reader Azure role?

Assign Reservations Reader when you need to: Inventory tenant reservations, orders, utilization context, terms, quantities, and scope settings.; and Provide FinOps, finance, audit, or capacity teams read-only visibility across reservation commitments.. Practical scope: The built-in role is assignable only at `/providers/Microsoft.Capacity`, a tenant/provider scope rather than a management group, subscription, resource group, or resource. It provides read access to all reservations in the tenant.

What permissions does the Reservations Reader Azure role grant?

The role definition grants 2 combined control-plane and data-plane actions. Representative operations include: Microsoft.Capacity/*/read; and Microsoft.Authorization/roleAssignments/read. Review the permission sections above for the complete definition and exclusions.

What are the security risks of the Reservations Reader Azure role?

Key considerations when assigning Reservations Reader: Tenant-wide reservation information reveals financial commitments, product usage, terms, and organizational purchasing patterns.; and The role is read-only and has no DataActions, but its provider scope is broader than one subscription.. Follow the assignment guidance above and use the narrowest practical scope.

Editorial sources (5)

Official Microsoft Learn documentation →