Study guide

4.3 Microsoft Entra Roles and Role-Based Access Control

Azure SC-900 Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Orientation: SC-900 Audience, Format, Scoring, Retakes, and Study Map

1.1 Credential Purpose and Audience 1.2 Exam Duration, Seat Duration, and Experience 1.3 Scoring, Scaled Score, and Pass-Rate Myths 1.4 Retake Policy and Certification Lifecycle 1.5 Scheduling, Price, and Delivery Options 1.6 Skills Measured and Study Map

2 Security, Compliance, and Identity Concepts: Zero Trust, Shared Responsibility, and GRC

2.1 Shared Responsibility Model 2.2 Defense in Depth and the CIA Triad 2.3 Zero Trust Model 2.4 Encryption, Hashing, and Data States 2.5 Governance, Risk, and Compliance 2.6 Identity Perimeter, Authentication, Authorization, and Federation

3 Microsoft Entra ID: Identities, Hybrid Identity, and Authentication

3.1 Microsoft Entra ID Foundations 3.2 Identity Types and Directory Objects 3.3 Hybrid Identity and Entra Connect Concepts 3.4 Authentication Methods and Sign-in Assurance 3.5 Multifactor Authentication 3.6 Password Protection, Self-Service Password Reset, and External Identities

4 Microsoft Entra Access Management, Governance, PIM, and Identity Protection

4.1 Conditional Access Purpose 4.2 Signals and Controls 4.3 Microsoft Entra Roles and Role-Based Access Control 4.4 Identity Governance, Entitlement Management, and Lifecycle Governance 4.5 Access Reviews and Privileged Identity Management 4.6 Microsoft Entra ID Protection and Risk

5 Azure Infrastructure Security: DDoS, Firewall, WAF, NSGs, Bastion, and Key Vault

5.1 Choose the Right Infrastructure Security Control 5.2 Azure DDoS Protection for Availability 5.3 Azure Firewall for Centralized Network Policy 5.4 Web Application Firewall for HTTP Workloads 5.5 Virtual Networks, Subnets, and Network Security Groups 5.6 Bastion and Key Vault for Administration and Secrets

6 Defender for Cloud: CSPM, Cloud Workload Protection, and Secure Score

6.1 Defender for Cloud Purpose and Exam Role 6.2 CSPM, Foundational Posture, and Defender CSPM 6.3 Policies, Standards, and Security Recommendations 6.4 Secure Score and Remediation Priority 6.5 Regulatory Compliance and Multicloud Posture 6.6 Cloud Workload Protection and Defender Plans

7 Microsoft Sentinel: SIEM, SOAR, Analytics, Hunting, Workbooks, and Playbooks

7.1 Sentinel as SIEM and SOAR 7.2 Data Connectors and Security Signals 7.3 Analytics Rules, Incidents, and Detection 7.4 Workbooks for Visual Review 7.5 Hunting, KQL Awareness, and Notebooks 7.6 Automation Rules and Logic Apps Playbooks

8 Microsoft Defender XDR: Office, Endpoint, Cloud Apps, Identity, Vulnerability, and Threat Intelligence

8.1 Defender XDR Suite and Microsoft Defender Portal 8.2 Defender for Office 365 8.3 Defender for Endpoint 8.4 Defender for Cloud Apps 8.5 Defender for Identity 8.6 Vulnerability Management and Threat Intelligence

9 Microsoft Purview, Service Trust, Privacy, Compliance Manager, and Compliance Score

9.1 Service Trust Portal and Assurance Resources 9.2 Privacy Principles and Microsoft Priva 9.3 Microsoft Purview Portal 9.4 Compliance Manager Assessments 9.5 Compliance Score and Improvement Actions 9.6 Scenario Selection for Trust, Privacy, and Compliance Manager

10 Microsoft Purview Data Classification, Labels, DLP, Retention, eDiscovery, and Audit

10.1 Data Classification Foundations 10.2 Content Explorer and Activity Explorer 10.3 Sensitivity Labels and Label Policies 10.4 Data Loss Prevention 10.5 Retention, Records Management, and Label Policies 10.6 eDiscovery, Audit, and Insider Risk Management

11 SC-900 Product Selection Playbooks and Common Microsoft Rebrand Traps

11.1 Read the Scenario Before Picking a Product 11.2 Entra Playbook for Identity, Access, and Governance 11.3 Defender Playbook for Protection, Detection, and Posture 11.4 Sentinel Playbook for SIEM, SOAR, and Hunting 11.5 Purview Playbook for Compliance, Data, and Risk 11.6 Renamed Products and Similar-Name Traps 11.7 Microsoft Learn Practice Assessment Review Loop

12 Final SC-900 Review, Timed Practice, Exam Day, and Next Certification Path

12.1 Domain-Weighted Final Review Plan 12.2 Timed Practice and Pacing 12.3 Exam Sandbox and Question Experience 12.4 Exam-Day Logistics and Boundaries 12.5 Scoring, Retakes, and After-Exam Decisions 12.6 Final Memory Check and Scenario Drills 12.7 Next Certification Path After SC-900

4.3 Microsoft Entra Roles and Role-Based Access Control

Key Takeaways Explain This Topic AI

Microsoft Entra roles control access to Entra/Microsoft 365 resources (users, groups, apps) and are scoped at the tenant level.

Azure RBAC roles control access to Azure resources (VMs, storage, databases) and can be scoped at management group, subscription, resource group, or individual resource.

Entra and Azure role permissions do not interoperate: Entra permissions cannot be used in Azure custom roles and vice versa, though Global Administrators can elevate to manage Azure subscriptions.

Azure RBAC is an additive allow model built on role definition, security principal, and scope assignment; there are 100+ built-in Azure roles plus custom roles.

Both systems enforce least privilege by granting only the permissions a role requires.

Last updated: June 2026

Two separate role systems

Microsoft maintains two distinct role-based access control systems , and SC-900 specifically tests telling them apart.

Microsoft Entra roles (directory roles) control access to Microsoft Entra and Microsoft 365 resources — users, groups, applications, service principals, and Entra settings — via the Microsoft Graph API. Their scope is the tenant (organization-wide), with optional administrative-unit scoping. Examples include Global Administrator , User Administrator , Security Administrator , Helpdesk Administrator , and Privileged Role Administrator .

Azure roles (Azure RBAC) control access to Azure resources — virtual machines, storage accounts, databases, networks — through Azure Resource Manager. Their scope is flexible: management group → subscription → resource group → individual resource , inheriting downward. Examples include Owner , Contributor , Reader , and User Access Administrator .

  • Aspect Microsoft Entra roles Azure RBAC roles
  • Manages Entra/M365 objects (users, groups, apps) Azure resources (VMs, storage, DBs)
  • Scope Tenant-wide (org level) Mgmt group / subscription / RG / resource
  • Accessed via Microsoft Graph Azure Resource Manager
  • Example Global Administrator Owner, Contributor, Reader

How Azure RBAC is built

An Azure role assignment has three parts that the exam may ask you to name:

Security principal — who gets access (user, group, service principal, or managed identity).

Role definition — what they can do (a collection of permissions, e.g. read, write, delete). Azure ships 100+ built-in roles , and you can author custom roles .

Scope — where the access applies (management group, subscription, resource group, or single resource).

Azure RBAC is an additive, allow-only model : your effective permissions are the sum of all your role assignments at the relevant scope. To take permissions away, you use deny assignments (created by Azure, e.g. by Blueprints/Managed Apps), not by stacking conflicting roles. Assignments inherit downward , so a Contributor at the subscription level is a Contributor on every resource group and resource inside it.

Principal + role definition + scope = a role assignment.

Permissions are cumulative across assignments.

Inheritance flows top-down through the scope hierarchy.

Interoperability and least privilege

A heavily tested fact: the two role systems do not share permissions . Microsoft Entra role permissions cannot be used in Azure custom role definitions, and Azure resource permissions cannot be used in Entra roles. They are administered separately. The one bridge is that a Global Administrator can toggle Access management for Azure resources to temporarily gain User Access Administrator rights over all Azure subscriptions — but that is an elevation action, not shared permissions.

Both systems exist to enforce least privilege : grant an identity only the role it needs for its task. If a scenario says an administrator has too much standing access , the fix is a narrower role plus Privileged Identity Management (Section 4.5), not a stronger authentication method.

  • Scenario clue Right system
  • Grant rights to reset user passwords in the directory Entra role (e.g. Helpdesk Administrator)
  • Grant rights to start/stop a virtual machine Azure RBAC (e.g. Virtual Machine Contributor)
  • Make a user able to manage the whole tenant Entra Global Administrator
  • Give read-only access to one resource group Azure RBAC Reader at RG scope

Common role question traps

Do not answer MFA just because an administrator is involved — if the admin already signed in and the problem is excessive capability , the issue is authorization (roles), not authentication. Do not answer access review when the question asks for the initial model of assigning permissions; access reviews check whether access should continue . And watch the Entra-vs-Azure split: a question about managing Azure storage or VMs is Azure RBAC , while a question about managing directory users and groups is Entra roles .

Sign-in strength problem → MFA / authentication.

Permission model / who-can-do-what → roles and RBAC.

Directory objects (users, groups) → Entra roles.

Azure resources (VMs, storage) → Azure RBAC.

Reducing always-on admin power → PIM.

Built-in roles, least privilege, and scope in practice

Microsoft strongly recommends using built-in roles before creating custom ones, and choosing the most specific role rather than a broad one. On the Azure RBAC side, the three foundational roles illustrate the least-privilege ladder: Reader can view resources but change nothing; Contributor can create and manage resources but cannot grant access to others ; Owner has full control including the ability to assign roles. A frequent exam distinction is exactly that line — only Owner and User Access Administrator can manage other people's access; a Contributor cannot.

Granting Owner when Contributor would do is a least-privilege violation.

On the Entra side, Global Administrator is the most powerful role and should be tightly limited (Microsoft suggests a small number of Global Admins, protected by PIM and MFA). More specific Entra roles — User Administrator , Groups Administrator , Helpdesk Administrator , Security Reader , Security Administrator — let you delegate narrow duties without handing out full tenant control. Choosing Helpdesk Administrator to let a support agent reset passwords, instead of Global Administrator, is the least-privilege answer.

Scope is the other lever. Because Azure RBAC inherits downward, you assign a role at the lowest scope that still covers the need: a single resource group rather than the whole subscription, or one storage account rather than the resource group. The combination of the narrowest role at the narrowest scope is how Azure RBAC operationalizes least privilege.

  • Need Least-privilege choice
  • View, but not change, all resources in a subscription Reader at subscription scope
  • Manage resources in one app's resource group, no access grants Contributor at that resource group
  • Let a help-desk agent reset user passwords Helpdesk Administrator (Entra)
  • Allow assigning roles to others on a resource Owner or User Access Administrator

The takeaway: never pick the broadest role offered; pick the one whose name matches the task at the smallest scope.