Azure Management and governance built-in role
Azure Center for SAP solutions reader
Reads Azure Center for SAP solutions Virtual Instance for SAP solutions resources and the supporting compute, network, storage, and workload configuration needed to display SAP system health and status. It has no write Actions or 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: 05352d14-a920-4328-a0de-4cbe7430e26b
Control-plane actions (43)
Microsoft.Advisor/configurations/readMicrosoft.Advisor/recommendations/readMicrosoft.Workloads/sapvirtualInstances/*/readMicrosoft.Workloads/Locations/*/readMicrosoft.Workloads/Operations/readMicrosoft.Workloads/Locations/OperationStatuses/readMicrosoft.Resources/subscriptions/resourceGroups/readMicrosoft.Insights/alertRules/readMicrosoft.Insights/metrics/readMicrosoft.Insights/metricDefinitions/readMicrosoft.Resources/deployments/readMicrosoft.Authorization/*/readMicrosoft.Resources/subscriptions/readMicrosoft.Resources/subscriptions/resourcegroups/deployments/readMicrosoft.ResourceHealth/availabilityStatuses/readMicrosoft.Network/virtualNetworks/readMicrosoft.Network/virtualNetworks/providers/Microsoft.Insights/metricDefinitions/readMicrosoft.Network/virtualNetworks/subnets/readMicrosoft.Network/virtualNetworks/subnets/virtualMachines/readMicrosoft.Network/networkInterfaces/readMicrosoft.Network/networkInterfaces/ipconfigurations/readMicrosoft.Network/networkInterfaces/loadBalancers/readMicrosoft.Network/networkInterfaces/providers/Microsoft.Insights/metricDefinitions/readMicrosoft.Network/loadBalancers/readMicrosoft.Network/loadBalancers/backendAddressPools/readMicrosoft.Network/loadBalancers/frontendIPConfigurations/readMicrosoft.Network/loadBalancers/loadBalancingRules/readMicrosoft.Network/loadBalancers/inboundNatRules/readMicrosoft.Network/loadBalancers/providers/Microsoft.Insights/logDefinitions/readMicrosoft.Network/loadBalancers/networkInterfaces/readMicrosoft.Network/loadBalancers/outboundRules/readMicrosoft.Network/loadBalancers/virtualMachines/readMicrosoft.Network/loadBalancers/providers/Microsoft.Insights/metricDefinitions/readMicrosoft.Network/privateEndpoints/readMicrosoft.Storage/storageAccounts/readMicrosoft.Storage/storageAccounts/blobServices/readMicrosoft.Storage/storageAccounts/blobServices/containers/readMicrosoft.Storage/storageAccounts/fileServices/readMicrosoft.Storage/storageAccounts/fileServices/shares/readMicrosoft.Compute/virtualMachines/readMicrosoft.Compute/availabilitySets/readMicrosoft.Compute/virtualMachines/extensions/readMicrosoft.Compute/disks/read
Data-plane actions (0)
None — this role grants no data-plane (data access) actions.
Excluded actions (0)
None
Assignable scopes (1)
/
Practical scope
Azure RBAC assignments apply at the selected scope and are inherited by child scopes. Keep the assignment at the narrowest resource, resource group, subscription, or management-group boundary that contains the intended resources. Assign on the VIS or the dedicated resource groups whose SAP system the principal must inspect; broader scope exposes supporting infrastructure metadata for every inherited SAP estate.
Common use cases (2)
- View registered SAP systems, component discovery, health, status, and supporting Azure resource configuration.
- Provide SAP operations, audit, or support visibility without start, stop, registration, deployment, or deletion authority.
Prerequisites (2)
- The SAP system must be registered as a VIS resource for Azure Center for SAP solutions visibility.
- The principal must need observation only; start, stop, registration, and deployment require Administrator.
Best practices (2)
- Assign at the VIS or SAP resource-group boundary instead of a broad subscription when possible.
- Treat infrastructure and SAP component metadata as sensitive operational information.
Security considerations (2)
- The role exposes SAP topology, VM, disk, load-balancer, storage, network, and system health metadata.
- It has no DataActions and does not start, stop, deploy, install, register, or delete SAP resources.
Assignment guidance
Assign to SAP support, audit, or operations principals that need VIS visibility only. Escalate to Administrator only for a documented management action, and keep the service identity role separate.
Related roles (1)
- Azure Center for SAP solutions administrator: Adds deployment, installation, registration, lifecycle, and VIS operations.
Common questions
When should I assign the Azure Center for SAP solutions reader Azure role?
Assign Azure Center for SAP solutions reader when you need to: View registered SAP systems, component discovery, health, status, and supporting Azure resource configuration.; and Provide SAP operations, audit, or support visibility without start, stop, registration, deployment, or deletion authority.. Practical scope: Azure RBAC assignments apply at the selected scope and are inherited by child scopes. Keep the assignment at the narrowest resource, resource group, subscription, or management-group boundary that contains the intended resources. Assign on the VIS or the dedicated resource groups whose SAP system the principal must inspect; broader scope exposes supporting infrastructure metadata for every inherited SAP estate.
What permissions does the Azure Center for SAP solutions reader Azure role grant?
The role definition grants 43 combined control-plane and data-plane actions. Representative operations include: Microsoft.Advisor/configurations/read; Microsoft.Advisor/recommendations/read; Microsoft.Workloads/sapvirtualInstances/*/read; Microsoft.Workloads/Locations/*/read; Microsoft.Workloads/Operations/read; and Microsoft.Workloads/Locations/OperationStatuses/read. Review the permission sections above for the complete definition and exclusions.
What are the security risks of the Azure Center for SAP solutions reader Azure role?
Key considerations when assigning Azure Center for SAP solutions reader: The role exposes SAP topology, VM, disk, load-balancer, storage, network, and system health metadata.; and It has no DataActions and does not start, stop, deploy, install, register, or delete SAP resources.. Follow the assignment guidance above and use the narrowest practical scope.
Editorial sources (6)
- Azure built-in roles for Management and governance →
Supports: Description, Practical scope, Security considerations. Retrieved 2026-07-16.
- Steps to assign an Azure role →
Supports: Prerequisites, Assignment guidance. Retrieved 2026-07-16.
- Understand scope for Azure RBAC →
Supports: Practical scope, Assignment guidance. Retrieved 2026-07-16.
- Best practices for Azure RBAC →
Supports: Best practices, Assignment guidance. Retrieved 2026-07-16.
- Azure RBAC for Azure Center for SAP solutions →
Supports: Description, Practical scope, Common use cases, Prerequisites, Best practices, Security considerations, Assignment guidance, Related roles. Retrieved 2026-07-16.
- Register an existing SAP system →
Supports: Common use cases, Prerequisites, Best practices, Security considerations. Retrieved 2026-07-16.