Why PIM Role Activation Bypasses Approval
A company is implementing Privileged Identity Management (PIM) in Microsoft Entra ID for Azure resources. The security team wants to ensure that all privileged role activations require approval and are logged. They also want to require Azure MFA during activation. However, they notice that some users are able to activate roles without approval. What is the most likely cause?
Quick Answer
The answer is that PIM role activation bypasses approval because the role settings for approval are not configured at the resource scope, and users are activating roles using inherited settings from a management group where no approval requirement exists. In Microsoft Entra ID, PIM for Azure resources allows you to define activation policies at the management group, subscription, or resource group scope. If approval is enforced only at the subscription level but a user activates a role at a resource group that inherits its settings from a management group lacking approval, the activation proceeds without any approval step. This is a classic misconfiguration tested on the AZ-500 exam, where candidates must understand that scope inheritance can override granular security controls. A common trap is assuming that setting approval at a higher scope automatically applies to all child scopes—it does not, unless explicitly configured. Memory tip: “Scope sets the scope of approval—if it’s missing at the leaf, inheritance gives no relief.”
⚠ Common exam trap
Many exam-takers assume PIM role settings are applied globally or uniformly across all scopes, but Azure resource PIM settings are scoped and inherited, so a missing approval configuration at a higher scope (like a management group) can silently bypass approval requirements at lower scopes.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The role settings for approval are not configured at the resource scope, and the users are using inherited settings from a management group
PIM role settings for Azure resources can be configured at the management group, subscription, or resource group scope. If approval is required only at the subscription scope but users activate roles at a resource group scope that inherits from a management group where approval is not configured, the activation will proceed without approval. This is a common misconfiguration where the approval requirement is not applied at the correct scope.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Users have permanent eligible assignments that bypass approval
Why it's wrong here
Permanent eligible assignments still require activation, which can be subject to approval.
- ✗
The audit log is not enabled for PIM
Why it's wrong here
Audit logging does not affect approval requirements; it only logs activities.
- ✗
Users are assigned the role directly instead of through eligibility
Why it's wrong here
Direct assignments provide permanent activation, but they do not bypass approval if the role settings require approval for activation.
- ✓
The role settings for approval are not configured at the resource scope, and the users are using inherited settings from a management group
Why this is correct
Role settings can be configured at different scopes (management group, subscription, resource group). If the approval requirement is not set at the specific scope, inherited settings may not require approval.
Go deeper
Related to this question
About these practice questions
This AZ-500 question is part of Courseiva's 194-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on AZ-500
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Refer to the exhibit. You are configuring a PIM role setting for an Azure AD role. The exhibit shows the activation settings. A user activates the role and provides a justification. An approver from the Security Team does not see any pending requests. What is the most likely reason?
medium- A.The role is permanently assigned
- B.The activation duration is set to 0 days
- C.The user did not provide a justification
- ✓ D.The user is a member of the approver group
Why D: The user who activated the role is a member of the approver group. In Azure AD Privileged Identity Management (PIM), when a user is both the requester and a member of the approver group, the approval request is automatically approved and does not appear as a pending request for other approvers. This self-approval behavior prevents the request from being visible in the pending requests queue.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AZ-500 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-500 exam.