Skip to content
Skills Library
Security · Review & audit

conditional-access-review

/conditional-access-review

Review Microsoft Entra Conditional Access for gaps — MFA coverage for all users and apps, phishing-resistant MFA for admins, legacy authentication blocking, device compliance, token protection, risk-based policies, exclusions and report-only policies — using policy exports and sign-in log evidence. Use when assessing Entra ID security, troubleshooting why a sign-in wasn't challenged, or after an account takeover.

Repository
Claude-Blue ↗
Licence
MIT
Last repository change
01.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
4
Deprecation

No signals detected. Repository changed on 01.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Review Microsoft Entra Conditional Access for gaps — MFA coverage for all users and apps, phishing-resistant MFA for admins, legacy authentication blocking, device compliance, token protection, risk-based policies, exclusions and report-only policies — using policy exports and sign-in log evidence. Use when assessing Entra ID security, troubleshooting why a sign-in wasn't challenged, or after an account takeover.

Original author description

Review Microsoft Entra Conditional Access for gaps — MFA coverage for all users and apps, phishing-resistant MFA for admins, legacy authentication blocking, device compliance, token protection, risk-based policies, exclusions and report-only policies — using policy exports and sign-in log evidence. Use when assessing Entra ID security, troubleshooting why a sign-in wasn't challenged, or after an account takeover.

How it works

  1. Export policies
  2. Baseline policy set (Microsoft guidance)
  3. Gap analysis with sign-in evidence
  4. Common weaknesses
  5. Output
  6. Related skills
  7. References
Original SKILL.md headings · 53 lines, 300 words
SKILL.md preview
---
name: conditional-access-review
description: Review Microsoft Entra Conditional Access for gaps — MFA coverage for all users and apps, phishing-resistant MFA for admins, legacy authentication blocking, device compliance, token protection, risk-based policies, exclusions and report-only policies — using policy exports and sign-in log evidence. Use when assessing Entra ID security, troubleshooting why a sign-in wasn't challenged, or after an account takeover.
license: MIT
metadata:
  category: azure-security
  version: "2.0.0"
  verification: documented
---

# Conditional Access Review

## Export policies

```powershell
Connect-MgGraph -Scopes "Policy.Read.All"
Get-MgIdentityConditionalAccessPolicy -All | ConvertTo-Json -Depth 10 > ca-policies.json
```
Tools: Microsoft's CA templates / "What If", Maester (Pester-based Entra tests: `Invoke-Maester`), CISA ScubaGear for M365 baselines (`Invoke-SCuBA`).

## Baseline policy set (Microsoft guidance)

1. Require MFA for **all users, all resources** (exclude only break-glass accounts).
2. Require **phishing-resistant MFA** (FIDO2, Windows Hello for Business, certificate-based) for privileged roles (authentication strength).
3. **Block legacy authentication** (client apps: Exchange ActiveSync, other clients).
4. Require MFA for Azure management (Windows Azure Service Management API / Microsoft Admin Portals).
5. Require compliant or hybrid-joined device for sensitive apps or for admins.
6. Sign-in risk / user risk policies (Entra ID P2): require MFA / password change.
7. Block or restrict device code flow and authentication transfer where not needed.
8. Token protection (session binding) for supported apps where licensed.

## Gap analysis with sign-in evidence

```kusto
SigninLogs
| where TimeGenerated > ago(30d) and ResultType == "0"
| where AuthenticationRequirement == "singleFactorAuthentication"
| summarize count(), apps=make_set(AppDisplayName, 20) by UserPrincipalName, ClientAppUsed
| order by count_ desc
```
Shows real single-factor successes — each is a gap or an intended exclusion. Also check `ConditionalAccessStatus == "notApplied"`.

## Common weaknesses

- Exclusions for groups that grow (e.g., "MFA exclusions" with dozens of users), service accounts used interactively, trusted named locations covering whole ISP ranges, policies left in **report-only**, guest users excluded, "All cloud apps" missing for some policies, device platform conditions bypassable with unknown platforms.
- Break-glass accounts without alerting on use.

## Output

`Policy | State | Users/apps scope | Exclusions (count, justification) | Gap | Evidence (sign-ins) | Recommendation`

## Related skills

`entra-signin-investigation`, `authentication-policy-review`, `azure-rbac-review`, `token-theft-investigation`

## References

- Conditional Access policy templates: https://learn.microsoft.com/en-us/entra/identity/conditional-access/concept-conditional-access-policy-common
- Authentication strengths: https://learn.microsoft.com/en-us/entra/identity/authentication/concept-authentication-strengths
- Maester: https://maester.dev/
- CISA ScubaGear: https://github.com/cisagov/ScubaGear

Versions

RepositoryScoreLicence
This page · kaandgnsh/Claude-Blue100MIT
openadminos/greybeard100MIT

Database snapshot: 13.11.2026 · package version c9a41e05a28d (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90implementing-conditional-access-policies-azure-ad
    Configures Microsoft Entra ID (Azure AD) Conditional Access policies for zero trust access control, covering signal-based policy design, device compliance requirements, risk-based authentication, named locations, and session controls aligned to NIST SP 1800-35. Use when…
  • 100entra-signin-rca
    Analyze Microsoft Entra ID (Azure AD) Interactive and Non-Interactive Sign-In JSON/CSV logs to pinpoint why a user, service principal, or device failed authentication or was blocked by overlapping Conditional Access (CA) policies. Use when troubleshooting AADSTS error codes, MFA…
  • 100entra-signin-investigation
    Investigate Microsoft Entra ID sign-ins — interactive and non-interactive logs, ResultType error codes, Conditional Access results, authentication details (MFA method), device and location, token-replay and AiTM indicators, risky sign-ins (Identity Protection) — with KQL and…
  • 100azure-entra-id-specialist
    Use this skill for Microsoft Entra ID specialist work, especially Conditional Access, authentication methods, MFA and SSPR registration, identity protection, workload identities, app registrations, external identities, agent identities, break-glass posture, and tenant identity control reviews.
  • 95implementing-passwordless-auth-with-microsoft-entra
    Implements passwordless authentication using Microsoft Entra ID with FIDO2 security keys, Windows Hello for Business, Microsoft Authenticator passkeys, and certificate-based authentication to eliminate password-based attacks. Use when deploying passwordless sign-in, configuring…
  • 90authentication-policy-review
    Review authentication policy and MFA posture across IdPs — MFA coverage and method strength (phishing-resistant vs. SMS/push), legacy protocol exposure, password policy (NIST SP 800-63B), session lifetimes, self-service recovery and help-desk reset procedures, break-glass…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.