Finance entitlement approval
Confirm why Jordan needs membership in the assigned reader group and how long access is authorized.
Work a focused version of Northstar’s Expense Portal incident. Investigate sign-ins, provisioning and approvals, restore two separate causes, and verify six access outcomes. For the full cross-domain final challenge, continue to Lab 015 on JoeLearns Labs.
Investigate the initial evidence before making changes.
Browser-session progress only · Not an exam-readiness predictionStart with the symptoms. Examine each source to distinguish the triggering policy change from other identity and application failures. The records are intentionally incomplete until you open the source.
Jordan from Operations reports that Expense Portal worked earlier this morning. Casey in Finance also sees a device-compliance block; Jamie in Marketing has never been assigned. Support was about to recommend disabling Conditional Access for the whole tenant.
Select a log source on the left to inspect Northstar's incident evidence. Begin with the sign-in records.
Choose the policy-level cause, the directory-to-application cause and who initiated the policy change. Both causes must be correct. This is an assessment of observed evidence, not guesswork from a single error code.
Two changes are required. An application assignment requires governance approval; a Conditional Access policy change requires approved temporary PIM elevation. A convenient shortcut may resolve one symptom while failing the wider security check.
Confirm why Jordan needs membership in the assigned reader group and how long access is authorized.
Use the least privileged eligible role needed to update a tenant-wide CA policy.
These changes affect the same model tested below. Mistargeting or overprivileging access has observable consequences.
After modifying CA, deactivate the temporary role. A completed change cannot leave privileged access active.
Review the initial incident before performing changes.
Run all six checks against the current state. The acceptance matrix includes legitimate access, a prohibited operation, an excluded identity, Finance device protection, emergency recovery and privilege deactivation.
Every inspection, approval, configuration change and validation is recorded in this fictional session. A real change requires independent production evidence and an approved rollback plan.