Use Microsoft Learn - this provides structured learning paths, interactive training, and detailed technical documentation.
Start with the fundamentals of Azure RBAC by understanding the three components of a role assignment: the security principal, which identifies who receives access and can be a user, group, service principal, or managed identity; the role definition, which specifies what permissions are granted; and the scope, which determines where those permissions apply. Scope can be assigned at the management group, subscription, resource group, or individual resource level. Refer to Microsoft Learn: What is Azure role-based access control (Azure RBAC)?
The three fundamental built-in roles to understand are Reader, Contributor, and Owner. Reader can view resources but cannot make changes. Contributor can create, modify, and delete resources but cannot assign permissions to other users. Owner has full control over resources and can also assign Azure RBAC permissions to others. Microsoft Learn: Azure built-in roles.
Another important piece of knowledge is the difference between the Azure control plane and data plane. For example, a user with the Contributor role on an Azure Storage account can perform management operations such as changing resource configuration, but that role does not automatically provide access to the data stored in the account. Data access requires an appropriate data-plane role, such as Storage Blob Data Reader or Storage Blob Data Contributor. Microsoft Learn: Azure Storage data access control model.
Once you grasp the fundamentals, move to more advanced authorization concepts such as attribute-based access control (ABAC). Azure ABAC allows additional conditions to be applied to role assignments, including conditions based on resource attributes. For example, a condition can restrict access to blobs based on their attributes. More at https://learn.microsoft.com/en-us/azure/role-based-access-control/conditions-overview
For hands-on learning, Microsoft Learn has the module Secure your Azure resources with Azure role-based access control , which covers securing Azure resources with RBAC, including understanding access, assigning roles, and reviewing access-related information.
For a practical exercise involving identities and access, Microsoft Learn provides the guided project Set up new employee access, which provides hands-on experience with Microsoft Entra ID, security groups, and access management.
For administrator-level knowledge, the Microsoft Learn AZ-104 learning path includes identity and governance topics relevant to Azure RBAC, Microsoft Entra ID, Azure Policy, governance, and resource management. Microsoft Learn: AZ-104: Manage identities and governance in Azure.
For custom roles and the underlying role-definition structure, Microsoft Learn's Azure custom roles documentation explains how role definitions use permissions such as Actions, NotActions, DataActions, and NotDataActions.
Finally, Microsoft's Best practices for Azure RBAC (https://learn.microsoft.com/en-us/azure/role-based-access-control/best-practices) covers principles such as least privilege, using groups for access management, selecting appropriate scopes, and regularly reviewing and auditing role assignments.
If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.
hth
Marcin