ca-policy-investigation

Correlate Conditional Access policy changes with sign-in failure error codes.

2|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/msandbu/sentinelday --skill ca-policy-investigation-msandbu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ca-policy-investigation
Source: https://github.com/msandbu/sentinelday/tree/main/.github/skills/ca-policy-investigation
Command: npx skills add https://github.com/msandbu/sentinelday --skill ca-policy-investigation-msandbu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you investigate why users are blocked from accessing resources due to Conditional Access (CA) policies, by correlating sign-in failures with any recent policy modifications.

Core Features & Use Cases

  • Correlate Sign-in Failures: Links specific error codes (e.g., 53000, 50074) to CA policy changes.
  • Analyze Policy State Transitions: Detects if policies were enabled, disabled, or set to report-only.
  • Identify Unauthorized Changes: Pinpoints if a user bypassed security controls by modifying policies themselves.
  • Use Case: A user reports being unable to access a critical application. This skill helps determine if their access was blocked by a legitimate policy, or if a policy was recently altered (potentially by the user) to circumvent security.

Quick Start

Investigate Conditional Access policy changes for user '[email protected]' around the time of a sign-in failure.

Frequently Asked Questions about ca-policy-investigation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I investigate Conditional Access policy changes correlated with sign-in failures?

Investigate Conditional Access policy changes by correlating user actions with audit logs and sign-in data within Microsoft Sentinel to determine if a policy modification caused access blocks.

Why does a user get blocked by error codes 53000, 50074, or 530032 in Azure AD?

Users receive Azure AD error codes 53000, 50074, or 530032 when Conditional Access policies block their access. This skill correlates these specific sign-in failures with recent policy state transitions.

How can I detect if someone disabled a Conditional Access policy to bypass security controls?

Detect security control bypasses by analyzing Conditional Access policy state transitions from enabled to disabled or report-only, then correlating those specific audit log modifications with user sign-in failures.

Can I use Microsoft Sentinel AuditLogs and SigninLogs to identify unauthorized CA policy modifications?

Yes, you can use Microsoft Sentinel AuditLogs and SigninLogs to identify unauthorized Conditional Access policy modifications by tracking policy state transitions and correlating them with user privilege abuse.

What is the best way to analyze Conditional Access policy state transitions in Microsoft Sentinel?

Analyze Conditional Access policy state transitions in Microsoft Sentinel by querying AuditLogs for policy changes and linking them to SigninLogs to pinpoint enabled, disabled, or report-only states causing blocks.