Microsoft Azure · AZ-104 study guide

Microsoft Entra ID & Azure RBAC: Complete Guide to Secure Cloud Access

Learn how Azure identity, authentication and authorization fit together. Work through realistic role and scope decisions, managed identity failures, privileged access and AZ-104 preparation.

A signed-in Azure user can still be unable to restart a virtual machine. A managed identity can obtain a token and still receive a storage 403. These are not contradictions: identity and access operate in layers. This guide gives administrators and certification learners a practical way to identify the failed layer, grant only the access needed and explain the result.

Start with identity, authentication and authorization

A cloud permission problem is easier to solve when you separate three questions. Who or what is making the request? How was that identity authenticated? Which operation is it authorized to perform on the target? Microsoft Entra ID answers the identity and sign-in questions for many Azure and Microsoft cloud workloads. Azure role-based access control, usually shortened to Azure RBAC, answers whether a principal can perform a particular Azure Resource Manager operation at a particular resource scope. These systems cooperate, but neither one replaces the other.

Consider a person opening the Azure portal to restart a virtual machine. Microsoft Entra ID establishes the signed-in identity and may require multifactor authentication. The Azure Resource Manager request then reaches an authorization check. Azure RBAC evaluates the person's applicable role assignments and the VM's scope. A successful sign-in is not proof that a restart is allowed. Conversely, a role assignment cannot help someone who cannot complete the required authentication. This distinction tells an administrator where to look when a real access request fails.

The same separation matters for applications. A managed identity can obtain a token without an application-managed password, yet the target service still needs to authorize the operation. A token is evidence of identity, not a universal permit. If an App Service needs to read a blob, check the identity attached to that app, the target storage account and container, and a data-access role assigned at an appropriate scope. Do not solve the failure by granting broad subscription ownership or by copying a storage key into source code.

Microsoft Learn: Azure RBAC overview · Azure roles versus Microsoft Entra roles · Managed identities for Azure resources

What Microsoft Entra ID actually manages

Microsoft Entra ID is the identity system that contains users, groups, applications, service principals and managed identities for a tenant. A user account represents a person. A group can collect people who need a common access pattern. An application registration describes an application's identity configuration, while a service principal is the application's identity in a tenant. A managed identity is a specialized service principal managed with an Azure resource. Each has a different lifecycle and administration path, so the first practical question is often which object is named in the access request.

Entra authentication establishes that a caller is who it claims to be under configured sign-in controls. Depending on the application and tenant, those controls may include a passwordless method, multifactor authentication or a Conditional Access policy. Authentication can fail because the account is disabled, a sign-in is blocked, a credential is invalid or a required control was not satisfied. None of these failures is fixed by giving the account Owner on a resource group. Investigate the sign-in plane before changing authorization.

Entra administrative roles govern directory work: creating users, managing groups, resetting eligible passwords, managing applications or changing tenant settings. For example, User Administrator may cover specified user-management tasks but does not confer permission to restart an Azure VM. Global Administrator is powerful in the directory and should be tightly controlled, but it is not Azure RBAC Owner. Microsoft documents a special access-elevation mechanism for some recovery circumstances; that exception is not a reason to treat the two role systems as identical.

Microsoft Learn: Microsoft Entra role-based access control · Azure roles versus Microsoft Entra roles · Microsoft Entra Conditional Access

Read the request path as a sequence, not a single permission

The conceptual flow below is intentionally simplified. A user, group-backed account, application or managed identity initiates a request. Microsoft Entra ID supplies the identity and, for the relevant sign-in or token request, evaluates applicable authentication controls. An Azure operation then requires an Azure RBAC decision about the principal, allowed operation and resource scope. Some services have additional data-plane authorization, network, policy or application checks. Do not assume every request passes through every box in exactly the same implementation order.

Take a developer who can sign in but cannot list a blob container. The first box tells you the account exists and authentication succeeded. The next question is not automatically whether that developer has Reader on the storage account. Azure RBAC distinguishes control-plane actions, such as reading a storage account's configuration, from data-plane actions, such as reading blob content. A data role and any service-specific network restrictions deserve investigation. The diagram is a diagnostic map: it identifies the boundary that could have rejected the request.

For an application workload, replace the human in the first box with the application's service principal or managed identity. The box labelled Microsoft Entra ID still explains how the workload obtains an identity token. The RBAC box still asks what that identity may do at the target. A team can securely remove secrets from an application by using a managed identity, yet still experience a 403 because it never gave that identity a suitable role on the target. That outcome is expected, not evidence that managed identity is broken.

RequesterUser or workload identity; group membership may affect RBAC
Microsoft Entra IDIdentity, sign-in and token; MFA or Conditional Access when applicable
Azure RBACPrincipal + role + scope; applicable inherited grants
Target resourceAzure management action or service data operation
A simplified access path. Authentication and authorization are distinct checks; service data-plane and networking rules may add further decisions.

Microsoft Learn: Azure RBAC overview · Azure role definitions · Managed identities for Azure resources

Azure RBAC is principal plus role plus scope

An Azure role assignment joins three elements. The security principal is a user, group, service principal or managed identity. The role definition states which actions are included. The scope identifies the Azure resources to which the assignment applies. To evaluate a proposed assignment, say all three elements aloud. 'The operations group may perform VM operations in the application resource group' is specific. 'Give the engineer admin' is not. The former can be reviewed against a job requirement; the latter hides both permission and boundary.

A role definition is a reusable permission set, not a grant by itself. Assigning a built-in role or an approved custom role to a principal at a scope creates the grant. Reader can view Azure resource configuration, but it does not automatically read every underlying data object. Contributor can manage many resources within scope but cannot create Azure RBAC role assignments. Owner includes that access-management capability, which is why granting it for routine application deployment is usually excessive.

When troubleshooting, capture the actual principal object, requested action and full target resource ID. Display names can be duplicated or renamed; object IDs identify the security principal more reliably. An authorization error can point to a control-plane permission, while a blob or queue operation may need a role with a DataActions entry. Avoid guessing from a portal button label alone. The same visible task can invoke several underlying operations, and the role must cover the required ones without accidentally covering unrelated administration.

Which access system answers which question?
QuestionMicrosoft Entra IDAzure RBAC
Who is acting?Identifies a user or workload and supports authentication.Uses that principal in a resource role assignment.
Can they sign in?Applies sign-in and Conditional Access decisions where configured.Does not replace sign-in or issue the identity.
Can they change a VM?Directory roles alone do not normally grant this resource operation.Evaluates applicable role, action and resource scope.
Can they administer users?Directory administrative roles control relevant Entra tasks.Azure resource roles do not substitute for directory administration.

Microsoft Learn: Azure RBAC overview · Azure role definitions · Azure built-in roles

Choose the narrowest Azure scope that meets the task

Azure RBAC scopes form a hierarchy: management group, subscription, resource group and individual resource. An assignment at a parent generally applies to its children. If an employee receives Reader at subscription scope, assigning Reader again on one resource group does not remove access to the others. The inherited assignment remains effective. This is a common reason an access review finds more visibility than the local resource group's IAM view first appeared to show.

Start with the job's boundary. If an engineer manages only the web workload in one resource group, choose a role at that resource group rather than at subscription scope. If an engineer must operate one storage account, a resource-scoped assignment may be appropriate. Management-group assignments can apply across subscriptions, so reserve them for documented platform-wide needs. Narrowing scope limits the effect of a compromised identity and makes ownership changes easier to reason about.

Do not confuse a role definition's assignable scopes with an assignment's actual scope. Assignable scopes describe where a custom role can be assigned; they do not grant anyone access. Likewise, moving a resource to another resource group or subscription can change inherited access. Recheck the permission graph after structural changes. A role assignment that looks harmless at creation can become inappropriate when the parent scope grows to include new resources.

Microsoft Learn: Azure RBAC scope · Azure RBAC overview · Azure role definitions

Owner, Contributor and Reader are starting points, not universal answers

The three broad Azure roles are useful mental anchors. Owner can manage resources and assign Azure RBAC roles within its scope. Contributor can manage resources but cannot assign those roles. Reader can view Azure resource configuration without changing it. Their names are simple; their consequences are not. A role at subscription level affects far more than the same role at one resource, and a broad action wildcard can cover services the requester never mentioned.

Use a service-specific role when it fits. A virtual-machine operator does not automatically need access to storage, networking and everything else in a resource group. A data analyst who needs blob contents may require Storage Blob Data Reader rather than generic Reader. A person tasked only with delegating Azure role assignments may need an access-administration role rather than Owner's full resource-management reach. Confirm the current built-in definition and scope; a familiar title is not a substitute for reading included actions.

A practical selection exercise begins with verbs and nouns. Write 'restart virtual machines in resource group A,' 'read blobs in container B,' or 'review subscription activity logs.' Identify the actual operations in Microsoft Learn. Compare candidate roles for required actions and unwanted extras. Choose the narrowest scope, document the reason, and arrange a review date. If no built-in role fits, consider a custom role only after an access owner evaluates its maintenance burden.

Microsoft Learn: Azure roles versus Microsoft Entra roles · Azure built-in roles · Azure RBAC scope

Read Actions, DataActions and custom-role trade-offs

Azure role definitions distinguish control-plane operations from data-plane operations. Actions describe Azure Resource Manager management operations such as reading resource configuration or changing a setting. DataActions describe operations on data inside a service, such as reading a blob. NotActions and NotDataActions remove listed operations from a definition, but they are not universal explicit denies against other assignments. If another applicable role grants the operation, the principal may still be able to perform it.

This explains a frequent storage puzzle. A person with Reader can see a storage account and its properties in the portal but may receive an authorization error while opening private blobs. The task crossed from management visibility into data access. Conversely, a blob-data role should not be mistaken for permission to redesign the storage account. State which plane a request uses before selecting a role; do not give Contributor merely because a portal message says access denied.

Custom roles help when built-ins expose too many operations, but they require maintenance. Review action strings, assignable scopes and data operations. Test in a sandbox using a non-privileged identity; record both expected allowed and expected denied tasks. Re-evaluate when the service or application changes. A custom role with a broad wildcard can expand when Azure adds operations, while a narrowly enumerated role may need an update when a legitimate workflow adds a new action.

Do not build a custom role solely to avoid understanding a failure. First confirm the principal, assigned role, scope, data-plane requirements and possible separate service controls. Once the path is clear, decide whether a new definition is the best long-term fit. The objective is durable least privilege, not a quick green indicator in a portal screenshot.

Microsoft Learn: Azure role definitions · Azure RBAC overview · Azure built-in roles

Entra administrative roles protect directory work

Microsoft Entra administrative roles authorize directory and identity-service tasks. Examples include managing users, groups, application registrations and tenant settings. Those roles are separate from Azure RBAC definitions for Azure resources. One person can hold both types, but that represents two explicit decisions for two different jobs. Do not grant Global Administrator because an operator cannot start a VM; do not grant Azure Owner because a help-desk employee needs to reset a password.

A least-privilege design for support starts with the precise task. Can the team reset passwords for ordinary users, privileged users, or both? Does it need to create groups, assign licenses or manage application consent? Those are not interchangeable operations. Review the actual Entra role permissions and available administrative scope in your tenant, then test the approved role with a representative low-risk case. Avoid a tenant-wide role when narrower administration meets the requirement.

Some organizations use administrative units or custom directory roles to refine identity administration. Their availability and exact behavior depend on the task and licensing. The word scope does not have identical meaning to an Azure resource-group scope: one concerns directory objects, while the other concerns the Azure resource hierarchy. A diagram that displays both layers without this distinction can teach an unsafe shortcut.

Global Administrator does not automatically equal Azure Owner. Microsoft documents a deliberate elevation procedure that can grant an administrator User Access Administrator at root scope for access recovery. Treat that as a separate, powerful action requiring authorization and review, not an implicit entitlement of every directory administrator. Document any elevation, complete the repair, and remove unnecessary privilege according to organizational policy.

Microsoft Learn: Microsoft Entra role-based access control · Azure roles versus Microsoft Entra roles · Elevate access to manage Azure subscriptions · Privileged Identity Management

Use managed identities without assuming automatic permission

A managed identity gives an Azure-hosted workload a Microsoft Entra identity without requiring developers to store a password or client secret in application configuration. The workload obtains a token for a supported target service. That reduces credential handling, but the identity must still be authorized to perform the target operation. If a web app receives a token and then gets a 403 from Storage, investigate the target's role assignment, scope, data permissions and network access before changing authentication code.

A system-assigned managed identity is tied to the host resource's lifecycle. Deleting the host removes that identity. A user-assigned managed identity is an independent Azure resource that can be attached to more than one supporting workload and survives the deletion of one host. Choose according to ownership and lifecycle: a single disposable app may fit a system-assigned identity, while several related workers needing the same identity or a stable lifecycle may fit a user-assigned identity. A shared identity also enlarges the blast radius if one workload is compromised, so document that trade-off.

In an approved lab, inspect the identity shown on the workload, record its principal object ID and the downstream resource it must contact. Ask what exact action is needed: read one blob, write to a queue or retrieve a secret? Assign a suitable role at the narrowest valid scope, then test an allowed operation and a deliberately out-of-scope one. Do not copy a token into logs, grant Owner to make an experiment pass, or turn an application key into a permanent workaround.

Managed identity is one part of a broader architecture. The target service may require firewall rules, private networking, data-plane permissions or an application-specific authorization check. A successful token request confirms the identity path, not end-to-end authorization. Keeping separate observations for authentication and authorization helps teams diagnose failures without weakening unrelated controls.

Microsoft Learn: Managed identities for Azure resources · Azure RBAC overview · Azure role definitions

Conditional Access and MFA decide sign-in conditions, not resource roles

Microsoft Entra Conditional Access uses sign-in signals and policy conditions to decide whether a relevant access attempt should proceed and what controls must be satisfied. A policy may require multifactor authentication, a compliant device or another permitted control. It can also block access in a defined situation. Conditional Access operates in the identity and sign-in part of the story; it does not replace a narrow Azure RBAC role assignment for a VM, subscription or storage account.

A team often mixes the two because both screens use the word access. Suppose a user cannot open the Azure portal after a new device policy. An Owner assignment does not satisfy a device-compliance requirement. Review sign-in details and the policy evaluation before adjusting resource roles. Conversely, a user who signs in successfully after MFA may still lack the Azure role required to modify a resource. Solve the failure at the layer that actually rejected the request.

Security defaults provide a baseline of identity protections for tenants that do not need granular Conditional Access policies. The two approaches are not simply stacked: review Microsoft's current guidance before replacing security defaults with Conditional Access in a real tenant. Conditional Access generally requires Microsoft Entra ID P1 licensing for affected users, with risk-based features requiring P2. Verify licensing, policy prerequisites, emergency-access design and report-only evaluation before enabling a rule that might lock out administrators.

MFA is an authentication safeguard, not evidence that a user should have broad resource authority. A sound design combines strong sign-in controls with appropriately scoped authorization. In a design review, ask whether a proposed change controls who can sign in, what condition they must meet, what resource action they can take, or how access is audited. This classification prevents a security team from trying to solve all four problems with one product feature.

Microsoft Learn: Microsoft Entra Conditional Access · Microsoft Entra security defaults · Microsoft Entra governance licensing · Azure RBAC overview

Privileged Identity Management makes high privilege time-bound

Microsoft Entra Privileged Identity Management, or PIM, can make supported privileged roles eligible rather than permanently active. An eligible user activates a role when the task is needed, subject to configured controls such as justification, MFA or approval, and the activation expires. This reduces standing privilege while preserving an operational path for approved administration. It does not turn an ordinary Reader role into a privileged one, and it does not repair an incorrect scope or missing action in a role definition.

Separate three moments in an incident: eligibility, activation and effective authorization. A person may be eligible for a role yet still be unable to perform the action because the role has not been activated. They may activate it successfully but still target a resource outside the assignment scope. They may have the correct scope but hit a data-plane operation that the role does not include. Checking these moments in order is safer than making the role permanently active whenever a ticket arrives.

PIM's exact features and eligible-license requirements need verification for the tenant and use case; Microsoft lists Entra ID P2 or Entra ID Governance options for privileged identity management. A training example should not imply that every tenant can turn on PIM for free. Before adopting it, identify emergency-access accounts, activation policy owners, review cadence and who receives alerts. A poorly planned activation workflow can leave an organization unable to operate during an outage.

For AZ-104 preparation, distinguish the concept from a memorized click path. If a scenario asks for occasional privileged access with an approval step, PIM may be relevant. If it asks for a team to read one container every day, first choose the right ordinary role and scope. Temporary elevation is not a reason to ignore least privilege in the underlying role selection.

Microsoft Learn: Privileged Identity Management · Microsoft Entra governance licensing · Azure RBAC scope

Role conditions and deny assignments solve different problems

Azure role assignment conditions, sometimes discussed as Azure ABAC, can refine certain supported role assignments using attributes. The feature does not make every Azure action conditionally assignable, so read the currently supported services, roles and expressions before proposing it. A condition narrows what a particular assignment permits; it is not a generic explicit deny that overrides every other grant. If another applicable assignment grants the same operation without the condition, that other assignment can still matter.

Deny assignments are different. An applicable deny assignment can block an Azure resource action even when a role assignment grants it. Microsoft notes that, for generally available scenarios, Azure creates and manages these assignments, for example to protect managed resources. An ordinary administrator should not present customer-created deny assignments as a routine substitute for carefully scoped RBAC. A list of permissions must be interpreted alongside applicable denials and resource controls.

Consider a storage team that wants a reader to see only certain blobs. Before adding a condition, confirm that the relevant data role and attribute type are supported, check for other inherited grants, and test both allowed and disallowed objects. If a user is blocked from deleting a protected resource despite an Owner grant, inspect Azure-managed deny assignments and deployment protections rather than assuming the role assignment was lost. The two cases look similar in a portal error but have very different remedies.

Azure Policy and resource locks are further distinct controls. Policy evaluates or enforces resource compliance rules; a lock can help prevent deletion or modification. Neither should be described as a role definition. The comparison matters in both architecture and exam scenarios because the right answer depends on what must be controlled: who can perform an action, whether a resource meets a rule, or whether a protected resource can be changed.

Microsoft Learn: Azure role assignment conditions · Azure deny assignments · Azure role definitions

Walkthrough 1: help desk can manage users but cannot operate a VM

Imagine a support engineer who can update user accounts in the Microsoft Entra admin center. A ticket then asks them to restart a production VM. They open the VM in the Azure portal and receive an authorization error. The first temptation is to increase their directory role. That would address the wrong control plane. Their identity is valid and their directory role is doing its intended job; the missing permission concerns an Azure resource operation.

A safer response begins with the ticket owner verifying that VM operation is within the engineer's job. Record the target VM's resource ID, the operation requested and the current Azure role assignments for the engineer and their groups. Look for assignments inherited from the resource group or subscription. If there is no suitable grant, select a role containing the required VM operations and assign it at the smallest scope that covers the task. A role such as Owner at the whole subscription would make the error disappear but also expand unrelated capabilities.

After approval, test the exact task and a task outside the expected boundary. If the user can restart the target but cannot modify an unrelated workload, the scope behaves as designed. If access still fails, inspect role propagation, a deny assignment, resource locks, a missing dependent operation or the identity actually signed into the portal. Document what was changed and who approved it. The fictitious diagnostic text below is a teaching representation, not a real Azure log or ITCertPath client incident.

The lesson is that Entra roles and Azure RBAC roles are not competing names for one permission set. Identity administration and resource operation are independent duties. The same engineer can hold both when authorized, but each assignment should explain a concrete need and be reviewed on its own. For an exam, the clue is the object being changed: a VM is an Azure resource; a user account is a directory object.

Approval-first lab

  1. In an approved sandbox, identify a VM resource ID and the principal that should operate it.
  2. Write the intended action and smallest valid scope before looking at role names.
  3. Compare a suitable VM role with Contributor and Owner; explain the unnecessary powers of the broader choices.

Microsoft Learn: Azure roles versus Microsoft Entra roles · Azure built-in roles · Azure RBAC scope

Walkthrough 2: App Service authenticates but cannot read private blobs

A web app uses a system-assigned managed identity to fetch an image from a private blob container. The team enables the identity and sees that token acquisition succeeds, but the storage request returns 403. The evidence separates the layers: the app obtained an Entra token, so the identity path worked; the target did not authorize the data operation. Immediately creating an account key or broadening a subscription role would add risk without clarifying the cause.

First verify which managed identity the deployed app used. A staging slot, separate web app or user-assigned identity could have a different principal object ID from the one the team tested locally. Then record the storage account, container and operation. If the app reads blobs, compare the current role assignments with a data role designed for blob read access. Generic Reader on a storage account can show its configuration without granting blob content read. Choose the narrowest supported scope and confirm whether networking, firewall or private endpoint policy is also relevant.

Next test a known permitted blob and a blob outside the intended boundary. Keep test data synthetic. If the authorized read works and the out-of-scope read fails, the team has evidence that the identity and scope match the requirement. If both fail, inspect service logs and the token's intended audience without logging the token itself. If both succeed, check for inherited or group-based assignments that give broader access than expected.

This example teaches an important production discipline: replacing a secret with managed identity is only half of the change. The old key may have carried broad rights, while the new identity begins with no useful downstream permission until one is intentionally assigned. Plan the migration as two reviews—authentication architecture and target authorization—and verify both before disabling the old path under an approved change procedure.

Storage diagnosis worksheet

  1. Record the workload identity object ID and the target container's resource ID without copying secrets.
  2. Classify the failed operation as management-plane or data-plane.
  3. Explain why Reader on the account and Storage Blob Data Reader for blob content are not interchangeable.

Microsoft Learn: Managed identities for Azure resources · Azure role definitions · Azure RBAC scope

Walkthrough 3: an auditor needs evidence, not subscription ownership

An auditor asks to inspect configuration and activity for one Azure application. The application occupies a resource group inside a shared subscription. Granting Owner at subscription scope would let the auditor change unrelated resources and delegate access; it is much broader than a read-only evidence request. Start by clarifying whether the audit requires resource properties, Azure Activity Log events, resource data such as blob contents, or directory sign-in records. Each is a different evidence source and may require a different authority.

For read-only configuration, an Azure RBAC Reader assignment at the application resource group is a more defensible starting point. Confirm that the necessary logs are available and retained; a role cannot recover a log that was never collected or has aged out. If the auditor must read private application data, obtain explicit data-owner approval and consider a separate data-plane role limited to the relevant storage scope. If they need Microsoft Entra sign-in information, review directory-specific log access rather than silently broadening Azure resource roles.

Time-bound access and a written completion date are useful even for Reader. Record who approved the grant, which resources are in scope, what evidence will be exported and how access will be removed. Do not email raw tokens or unrestricted exports as a workaround. If the audit expands to another workload, revisit scope instead of assuming the original assignment should simply be moved to subscription level.

In an AZ-104 scenario, ask what the auditor must actually see. The phrase 'view all resources in a resource group' points toward a resource-scoped Reader-style answer. The phrase 'read blob contents' introduces data actions. The phrase 'review user sign-ins' points to Entra monitoring. The exam becomes easier when you classify the object and operation before selecting from similarly named roles.

Microsoft Learn: Azure built-in roles · Azure RBAC scope · Azure Activity Log · Microsoft Entra audit logs

Walkthrough 4: a narrower grant does not cancel a broader inherited grant

A new administrator sees that a developer is assigned Reader on a production resource group. The administrator assumes the developer cannot change resources there. However, the developer is also a member of a platform group with Contributor at the parent subscription. The subscription assignment is inherited, so the developer can still perform many resource-management actions in that production group. The local Reader assignment did not subtract the inherited Contributor grant.

To investigate, list applicable assignments at the resource, resource group, subscription and management-group levels. Check direct grants and group memberships, including nested groups when used. Distinguish an active PIM assignment from an eligible one and inspect any relevant deny assignment. Do not rely solely on one IAM tab or on the role most recently added. Effective access is the result of all applicable decisions, not the last row an administrator remembers editing.

The durable fix is to remove or narrow the unnecessary broad grant after an authorized review, or move the workload into an appropriate administrative boundary. Adding another Reader assignment does nothing to reduce Contributor. A hurried attempt to create a custom role with NotActions as a deny mechanism can fail for the same reason: NotActions modify that role definition, not permissions granted by another role. Test access after the change and record expected allowed and disallowed operations.

This is a valuable real-world and exam lesson. Questions that emphasize inherited scope, nested group membership or apparently conflicting roles are asking you to evaluate the whole access path. A least-privilege design is not a pile of restrictions over broad historical grants; it is a small set of justified assignments whose combined effect has been tested.

Microsoft Learn: Azure RBAC scope · Azure RBAC overview · Azure role definitions · Privileged Identity Management

Troubleshoot a denied request without weakening security

Begin with evidence. Record the time, caller, target resource, intended operation and exact error without exposing credentials or personal data. Identify whether the attempt failed at sign-in, token acquisition, Azure Resource Manager authorization or a service data-plane check. A sign-in failure belongs in Entra sign-in details and applicable Conditional Access results. A successful sign-in followed by an ARM authorization error points toward Azure role assignments, scope and possible denial. A storage 403 after token acquisition may involve data roles or network restrictions.

Next verify the principal. People can have multiple accounts or switch tenants; applications can have distinct service principals in different tenants; user-assigned and system-assigned managed identities have different object IDs. Make sure the role was granted to the identity that actually sent the request. Check group membership and whether the role assignment has propagated. Then inspect parent scopes. An inherited role can explain unexpected success, while an assignment on the wrong sibling resource group explains an expected action being denied.

Read the role definition rather than relying on its title. Does the requested action appear under Actions or DataActions? Is an apparent restriction only a NotAction within one role while another role grants the same operation? Is an Azure-managed deny assignment overriding the grant? Does Azure Policy or a lock impose a different kind of block? A good ticket records which hypothesis was checked and what observation ruled it in or out.

Finish with a minimal corrective change and a regression check. Ask the access owner to approve the exact principal, role and scope. Test one allowed action and one action that should remain denied; record the result without publishing tokens or real customer resource IDs. If the request is outside the person's job, the correct outcome may be to leave it denied and route the task to an authorized operator. Successful troubleshooting is not the same as making every red error disappear.

  • Authentication failed: inspect the sign-in and Conditional Access decision before changing resource roles.
  • Token succeeded, ARM action denied: inspect principal, role definition, scope, inherited grants and deny assignments.
  • Data read denied: separate data-plane roles and service networking from management-plane visibility.
  • Unexpected access succeeded: look for inherited or group grants rather than adding another Reader assignment.

Microsoft Learn: Azure RBAC overview · Azure RBAC scope · Azure role definitions · Azure deny assignments · Microsoft Entra Conditional Access

Where to look for access and change evidence

Monitoring is often confused with granting. An Azure role assignment says what a principal may do; an audit record helps explain what happened. For a failed employee sign-in, start with Microsoft Entra sign-in logs and the Conditional Access result. For directory changes, such as a role membership update, investigate Entra audit logs. For Azure resource-management changes, inspect Azure Activity Log events. A storage blob read is a service data-plane operation and may require resource diagnostic logs configured for that service. None of these logs is a universal transcript of all cloud activity.

A useful incident timeline joins evidence by time, principal ID, tenant, resource ID and correlation or request identifiers. It should show the attempted operation, the authentication result, the applicable authorization decision and any policy or networking decision. Do not infer that an event never occurred solely because it is absent from a log that was not enabled or whose retention period has expired. Plan collection and retention before an audit requirement arrives; verify settings with the organization's privacy and security policy.

For study purposes, map each question to its evidence plane. 'User could not sign in' invites Entra sign-in investigation. 'Who deleted this virtual machine?' points to Azure resource activity. 'Who opened a private blob?' requires service-level data logging if it was configured. This operational habit prevents a common AZ-104 mistake: assuming a Reader role or a single portal page gives complete answers about identity, resource changes and application data.

Microsoft Learn: Microsoft Entra audit logs · Azure Activity Log · Microsoft Entra Conditional Access

Design a least-privilege access review

Least privilege is a repeatable design process, not a slogan. Begin with the person's or workload's task, list the exact operations, identify the resources involved and separate temporary from continuing need. Then select an appropriate role and the narrowest practical scope. Check whether the principal already receives an inherited or group-based grant before adding another assignment. A new narrow grant does not reduce older broad access; the combined permission set is what matters.

Ask for an owner and expiry or review date for each privileged assignment. An emergency subscription-wide grant should be treated differently from a read-only resource-group assignment. Where licensing and operations support PIM, eligible activation can replace continuously active privilege for suitable roles. That does not eliminate the need for approval, monitoring, appropriate authentication or separation of duties. Break-glass accounts require their own documented controls and testing; do not simply apply normal Conditional Access rules without considering recovery.

For application identities, inventory which Azure resources and downstream services they access. Avoid sharing one user-assigned managed identity among unrelated workloads merely because it is convenient: shared identity can blur accountability and broaden the consequences of a compromise. Conversely, user-assigned identity can be appropriate when a workload deliberately needs an identity whose lifecycle is independent of one host. The review should record why the chosen identity type, scope and roles fit the architecture.

  • Define task and target before choosing a role.
  • Check existing direct and inherited grants.
  • Approve a principal, role, scope and review date together.
  • Test both intended access and intended denial.
  • Review or remove access when the task ends.

Microsoft Learn: Azure RBAC overview · Azure RBAC scope · Managed identities for Azure resources · Privileged Identity Management

Use this model for the AZ-104 identity and governance domain

The official AZ-104 study guide is the source of truth for the skills measured when you schedule the exam. Use it to build a checklist, then practice configuring and explaining the result of each access decision. The exam tests administration decisions, not the ability to recite role names without context. For identity and governance, be ready to distinguish Entra users and groups from Azure resources, explain RBAC assignments at different scopes and recognize how governance controls affect an administrator's choices.

A practical first lab is to create a disposable resource group in a permitted learning subscription, place a non-sensitive resource inside it and compare Reader with Contributor for a test principal. Before assigning anything, write down predicted outcomes for view, modify and access-delegation actions. After each test, inspect the effective assignments and remove the test grant. Do not use a production subscription or elevate a real colleague merely to study. If a lab environment lacks a second user, diagram the decision and use Microsoft's guided exercises instead of bypassing governance.

A second lab separates control and data planes. Use a private, synthetic storage container and a test workload identity. Predict whether a management-plane Reader grant allows listing account settings and whether it allows reading a blob. Then examine the appropriate storage data role and retest only within your authorized lab. The learning objective is to explain the 403, not to force success with a broad role or account key. Record the scope of each assignment and note how a role at a parent scope would change the result.

A third exercise asks you to sketch the complete access path for a virtual machine application: managed identity issuance, token acquisition, an Azure RBAC assignment if the target is an Azure resource, and a downstream service's authorization decision. Change one layer at a time. In a written explanation, state why authenticating with Entra ID does not automatically permit every ARM or data action. Review the official skills outline again near the exam date because objectives and product terminology can change.

Microsoft Learn: Official AZ-104 study guide · Azure RBAC overview · Managed identities for Azure resources · Azure role definitions

A focused four-week practice plan

Week one is for the vocabulary and control planes. Draw the Entra versus Azure RBAC boundary, compare a directory role with an Azure resource role and map five everyday requests to identity, authentication or authorization. Read the official overview pages, but spend as much time explaining an example aloud as reading. A learner who can describe why a successful portal login is followed by an authorization error has the essential foundation.

Week two is for scope and role definitions. Draw a management group, subscription, resource group and resource hierarchy; place a grant on each level and predict which child resources inherit it. Compare Owner, Contributor and Reader, then add a data-plane example. Inspect Actions, NotActions, DataActions and NotDataActions in role definitions. Write a short explanation of why NotActions is not a universal explicit deny. Revisit any answer where you chose a role by its title rather than its operations.

Week three is for workloads and protective controls. Compare system-assigned and user-assigned managed identities using a realistic deployment lifecycle. Trace a service-to-service request from token acquisition to target authorization. Build a decision table for security defaults, Conditional Access and PIM that includes licensing and operational constraints. Include a deliberate sign-in-failure scenario and a resource-permission-failure scenario so you learn to use different logs for different problems.

Week four is for integrated scenarios and review. Attempt a timed set of original practice questions, then spend more time on wrong-answer analysis than on the raw score. For each missed item, record the principal, operation, resource, scope and evidence you would check. Retest the same concept with a changed scope or identity type. Use the official AZ-104 objectives to spot gaps and keep independent practice tests distinct from Microsoft-issued exam content. Readiness is demonstrated by explaining your decision and its limits, not by memorizing one mock bank.

Microsoft Learn: Official AZ-104 study guide · Azure RBAC scope · Azure role definitions · Microsoft Entra Conditional Access

Mistakes to avoid in a real tenant and on the exam

A frequent error is treating a broad identity title as universal cloud authority. Global Administrator is powerful in the Entra directory, but does not automatically become Azure Owner on every subscription. Microsoft documents a deliberate elevation procedure for a Global Administrator to obtain User Access Administrator at root scope for recovery; this is an exceptional action with significant consequences, not the default permission model. Another error is assuming Contributor can delegate access. Contributor manages many resources but lacks RBAC role-assignment authority by default.

A second cluster of mistakes comes from overlooking the data plane. Reader can inspect many resource properties but does not automatically read blob content. A managed identity can obtain a token yet still receive 403 from the target. Assigning Owner at subscription scope to cure a container read error is therefore both imprecise and risky. Similarly, Azure RBAC role conditions can constrain supported assignments but should not be described as a general user-configurable deny rule; Azure-managed deny assignments are a separate mechanism.

Microsoft Learn: Azure roles versus Microsoft Entra roles · Elevate access to manage Azure subscriptions · Azure built-in roles · Azure role definitions · Azure role assignment conditions · Azure deny assignments · Official AZ-104 study guide

Turn this model into a certification plan

Use the official Microsoft objectives for exam scope. ITCertPath offers independent learning and practice paths; contact us to discuss your training or voucher inquiry without assuming a price, batch or provider affiliation.

Frequently asked questions

Is Microsoft Entra ID the same as Azure RBAC?

No. Microsoft Entra ID manages identities and authentication, and its directory roles govern directory tasks. Azure RBAC authorizes Azure resource operations through assignments of a principal, role and scope. A successful sign-in does not itself grant resource permissions.

Does Global Administrator automatically have Azure Owner access?

No. Global Administrator is a Microsoft Entra directory role, not an automatic Azure subscription Owner role. Microsoft documents a deliberate elevate-access recovery procedure that can grant User Access Administrator at root scope, but that is an explicit privileged action.

Can Azure Contributor assign RBAC roles?

Not by default. Contributor can manage many Azure resources but does not include the authority to assign Azure RBAC roles. Use an approved role with access-delegation permissions when that task is actually required.

Does Reader allow reading files in Azure Blob Storage?

No. Reader generally provides management-plane visibility of resources. Reading blob content requires an applicable data-plane permission, such as an appropriately scoped storage blob data role, as well as any applicable network access.

What is inherited Azure RBAC scope?

An assignment at a management group, subscription or resource group can apply to descendant scopes. A narrower Reader assignment does not remove a broader Contributor grant inherited from a parent or received through a group.

Does a managed identity automatically access other Azure services?

No. A managed identity provides an identity and a way to obtain tokens without an application-owned secret. The target service must still authorize the requested operation, often through a suitable Azure RBAC data or management role.

Are Azure RBAC role conditions the same as deny assignments?

No. Conditions can constrain supported role assignments; they are not a general-purpose explicit deny system. Azure deny assignments are a separate mechanism managed by Azure services and can override grants.

Do Conditional Access and PIM require licenses?

Capabilities and license requirements differ. Conditional Access generally requires Microsoft Entra ID P1, while risk-based features require P2. PIM eligible activation is associated with P2 or Microsoft Entra ID Governance. Verify the current Microsoft licensing terms for your tenant and use case.

Where should I investigate an Azure access denied error?

First identify whether sign-in, token acquisition, Azure Resource Manager authorization or a service data-plane operation failed. Inspect the actual principal, operation and target scope, then check applicable assignments, inherited grants, role actions, deny assignments and relevant logs before changing access.

Is this an official Microsoft training or exam page?

No. This is independent ITCertPath study guidance. Use Microsoft Learn and the current official AZ-104 study guide for authoritative product and exam-objective information.

Official Microsoft sources and review note

This independent guide was reviewed on 10 November 2026 against Microsoft Learn. Product behavior, exam objectives and licensing can change; check the official pages before making a production access change or booking an exam.