Agent skill

Entra Id Protection

by vinayaklatthe in vinayaklatthe/microsoft-security-skills

Guidance for Microsoft Entra ID Protection — risk-based identity security that detects user and sign-in risk and automates remediation.

MITAuto-check passedBackend & APIs

Install Entra Id Protection

skills CLI
$ npx skills add vinayaklatthe/microsoft-security-skills --skill entra-id-protection -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install vinayaklatthe/microsoft-security-skills entra-id-protection --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/vinayaklatthe/microsoft-security-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/entra-id-protection .claude/skills/entra-id-protection && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
entra-id-protection
GitHub stars
175
Token cost
~1.6k tokens
SKILL.md length
675 words
Files
1
Skills in repo
50
Repo updated
First seen
Licence
MIT

At a glance

Guidance for Microsoft Entra ID Protection — risk-based identity security that detects user and sign-in risk and automates remediation.

  • Works in 6 steps: Confirm prerequisites — Entra ID P2… → Use risk-based Conditional Access, not… → Tier 1 - High risk only — First policy… → …
  • On-prem AD attack detection (use defender-for-identity)
  • SKILL.md covers When to use, Map the risk signal to the…, Approach and Guardrails, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Entra Id Protection is an agent skill from vinayaklatthe/microsoft-security-skills. Guidance for Microsoft Entra ID Protection — risk-based identity security that detects user and sign-in risk and automates remediation. Covers risk detections, risk-based Conditional Access, self-remediation via MFA / secure password change, risky-user investigation, and streaming risk to Sentinel. WHEN: Entra ID Protection, identity risk policy, risky users, risky sign-ins, user risk policy, sign-in risk policy, risk-based Conditional Access, leaked credentials, anonymous IP detection, atypical travel, automate…

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Backend & APIs, covering Authentication. It works with Microsoft Entra ID and Microsoft Azure. The repository describes itself as: Curated Microsoft Security skills for AI agents - Defender, Sentinel, Entra, Purview, Intune, Security Copilot. The licence is MIT.

When your agent uses it

  • On-prem AD attack detection (use defender-for-identity)
  • CA policy authoring without risk signals (use conditional-access-mfa)
  • PIM activation (use azure-pim)

Example prompts

  • “/entra-id-protection”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Confirm prerequisites — Entra ID P2 licensing, MFA + SSPR registration enforced for the
  2. Use risk-based Conditional Access, not legacy built-in risk policies — Author CA
  3. Tier 1 - High risk only — First policy set: High sign-in risk → require MFA; High user
  4. Tier 2 - Medium expansion — After 30 days of clean Tier 1 metrics, expand to Medium
  5. Investigate the queue — Triage Risky users, Risky sign-ins, Risk detections
  6. Stream to Sentinel — Diagnostic settings → send RiskyUsers, UserRiskEvents,

What it can do on your machine

Read from SKILL.md and the folder at commit 15f16df. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • learn.microsoft.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Entra Id Protection loads about 1.6k tokens when it runs. Until then it costs about 225 tokens; SKILL.md has 675 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~225
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from vinayaklatthe/microsoft-security-skills at commit 15f16df, republished under its MIT licence (© vinayaklatthe). 675 words, ~1,619 tokens.

Download SKILL.mdSave it as .claude/skills/entra-id-protection/SKILL.md (or your agent's skills folder).
name
entra-id-protection
description
Guidance for Microsoft Entra ID Protection — risk-based identity security that detects user and sign-in risk and automates remediation. Covers risk detections, risk-based Conditional Access, self-remediation via MFA / secure password change, risky-user investigation, and streaming risk to Sentinel. WHEN: Entra ID Protection, identity risk policy, risky users, risky sign-ins, user risk policy, sign-in risk policy, risk-based Conditional Access, leaked credentials, anonymous IP detection, atypical travel, automate identity remediation, alert about leaked credentials, user flagged as risky, force password reset for compromised accounts, block sign-in when identity risk is high, EID P2 risk policy. DO NOT USE for on-prem AD attack detection (use defender-for-identity), CA policy authoring without risk signals (use conditional-access-mfa), or PIM activation (use azure-pim).
license
MIT
metadata.author
Microsoft
metadata.version
0.1.0

Microsoft Entra ID Protection

Microsoft Entra ID Protection uses Microsoft's threat intelligence and ML to detect identity risk (user risk and sign-in risk), automate remediation, and surface a queue of risky users and sign-ins for investigation. Requires Entra ID P2 to enable risk policies.

When to use

Adding risk-based, adaptive protection on top of Entra ID and Conditional Access. Use this skill to choose risk thresholds, decide between self-remediation and SOC investigation, and stream signals to Sentinel.

Do not use this skill for on-prem AD attack detection (defender-for-identity), authoring plain CA policies (conditional-access-mfa), or PIM activation (azure-pim).

Map the risk signal to the response

Risk typeExamplesRecommended response
Sign-in risk (this request)Anonymous IP, atypical travel, malware-linked IP, unfamiliar sign-in propertiesRisk-based CA → require MFA
User risk (this identity)Leaked credentials (TI feeds), Microsoft / partner-reported compromiseRisk-based CA → require secure password change
Both medium+ on same userActive session takeover indicatorsBlock + force secure password change + analyst review

Rule of thumb: start risk policies at High threshold, run for 30 days, then expand to Medium once user registration and remediation flows are proven. Starting at Medium without SSPR + MFA registration causes lockouts.

Approach

  1. Confirm prerequisites — Entra ID P2 licensing, MFA + SSPR registration enforced for the target user scope (registration policy in Authentication methods). Verify: Authentication methods activity report shows > 95% of in-scope users registered for at least one strong method.

  2. Use risk-based Conditional Access, not legacy built-in risk policies — Author CA policies with Sign-in risk and User risk conditions. Legacy "User risk policy" / "Sign-in risk policy" toggles are deprecated in favour of CA. Verify: no legacy risk policies enabled; risk conditions appear in CA What-If results.

  3. Tier 1 - High risk only — First policy set: High sign-in risk → require MFA; High user risk → require secure password change. Exclude break-glass accounts from every risk policy. Verify: report-only for 14 days shows < 5 false positives per 1,000 sign-ins before enforcing.

  4. Tier 2 - Medium expansion — After 30 days of clean Tier 1 metrics, expand to Medium sign-in risk → MFA. Don't extend user risk to Medium without an analyst review queue.

  5. Investigate the queue — Triage Risky users, Risky sign-ins, Risk detections daily. Confirm compromise (forces remediation + trains the model) or dismiss false positives. Never bulk-dismiss without review - dismisses teach the model wrong signal. Verify: weekly risky-user queue < 1% of monthly active users in a healthy tenant.

  6. Stream to Sentinel — Diagnostic settings → send RiskyUsers, UserRiskEvents, RiskyServicePrincipals to a Log Analytics workspace. Correlate with MDI and MDE in Defender XDR incidents.

Show full SKILL.md (254 more words)Show less

Guardrails

  • Break-glass accounts excluded from every risk policy. A leaked-credential detection on the wrong account can lock you out of the tenant.
  • MFA + SSPR registration first. Self-remediation only works when users can complete it. Without registration, risk policies become lockouts.
  • Start at High, expand to Medium. Medium thresholds without tuning generate noise and user friction.
  • Don't dismiss bulk false positives. Dismiss = "this was safe" which trains the model. Use confirm-safe / confirm-compromise deliberately, not as a queue cleanup tool.
  • Workload identity risk is separate. Service principals have their own risk detections
    • cover them with a parallel policy.

Common anti-patterns

  • "Use the legacy User risk / Sign-in risk policy toggles" - Deprecated. Use CA risk conditions which support broader controls and exclusions.
  • "Risk policy on All users at Medium on day one" - Lockout event. Pilot at High first.
  • "Bulk-dismiss the risky user queue weekly to clear noise" - Trains the detector incorrectly and erodes future precision.
  • "Risk events stay in Entra portal" - No SOC correlation. Stream to Sentinel and Defender XDR.

Example prompts

  • Configure risk-based Conditional Access for sign-in risk and user risk in Entra ID Protection.
  • Set up self-remediation - MFA for sign-in risk, secure password change for user risk.
  • Investigate a user flagged as risky and confirm compromise or dismiss safely.
  • Stream Entra ID Protection risk events to Sentinel for SOC correlation.
  • Why are we getting too many medium-risk alerts - how do I tune?

Microsoft Learn

© vinayaklatthe, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/entra-id-protection of vinayaklatthe/microsoft-security-skills.

Open the folder on GitHubat commit 15f16df

Compare with similar skills

Entra Id Protection next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Entra Id Protection compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Entra Id Protection this skillvinayaklatthe/microsoft-security-skills175—~1.6kAutomated safety check: PassMIT
Microsoft Azure Webjobs Extensions Authentication Events Dotnetmicrosoft/skills3.1k5 repos~3.8kAutomated safety check: PassMIT
Entra App Registrationmicrosoft/GitHub-Copilot-for-Azure2552 repos~2.1kAutomated safety check: PassMIT
Troubleshooting Authenticationmicrosoft-foundry/foundry-agent-webapp127—~682Automated safety check: NotesMIT
Iam Auditbriiirussell/cybersecurity-skills413—~3.1kAutomated safety check: NotesMIT
Auditing Azure Active Directory Configurationmukul975/Anthropic-Cybersecurity-Skills34k—~3kAutomated safety check: PassApache-2.0

Similar skills

  • Entra App Registration

    microsoft/GitHub-Copilot-for-Azure

    Official

    Guides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration.

    255 GitHub starsUsed in 2 repos~2.1k tokens
    Backend & APIsAuto-check passed
  • Troubleshooting Authentication

    microsoft-foundry/foundry-agent-webapp

    Provides authentication troubleshooting for MSAL, JWT, and Entra ID.

    127 GitHub stars~682 tokensUpdated 5 mo ago
    Backend & APIsAuto-check: notes
  • Iam Audit

    briiirussell/cybersecurity-skills

    Audit, design, and migrate Identity and Access Management — cloud provider IAM (AWS, GCP, Azure), identity providers (Okta, Entra ID / Azure AD, Auth0, Google Workspace), application authorization…

    413 GitHub stars~3.1k tokensUpdated 4 mo ago
    Backend & APIsAuto-check: notes
  • Auditing Azure Active Directory Configuration

    mukul975/Anthropic-Cybersecurity-Skills

    Auditing Microsoft Entra ID (Azure Active Directory) configuration to identify risky authentication policies, overly permissive role assignments, stale accounts, conditional access gaps, and guest…

    34k GitHub stars~3k tokensUpdated 1 mo ago
    Backend & APIsAuto-check passed
  • Validating Local Setup

    microsoft-foundry/foundry-agent-webapp

    Diagnose and fix incomplete local development setup. An agent skill from microsoft-foundry/foundry-agent-webapp.

    127 GitHub stars~1.2k tokensUpdated 5 mo ago
    Backend & APIsAuto-check: notes

More from vinayaklatthe/microsoft-security-skills

All 50 skills in this repo
  • API Security Design

    vinayaklatthe/microsoft-security-skills

    Guidance for designing secure APIs on Azure - authentication, authorization, gateway controls, input validation, rate limiting, secret management, and runtime threat detection - aligned to OWASP API…

    175 GitHub stars~2.2k tokensUpdated 3 mo ago
    Auto-check passed
  • Azure App Service Security

    vinayaklatthe/microsoft-security-skills

    Guidance for securing Azure App Service web apps and APIs — managed identity, Easy Auth with Microsoft Entra ID, network isolation via private endpoints + VNet integration, HTTPS / TLS hardening…

    175 GitHub stars~1.9k tokensUpdated 3 mo ago
    Auto-check passed
  • Azure Arc

    vinayaklatthe/microsoft-security-skills

    Guidance for Azure Arc — projecting on-premises, multicloud (AWS/GCP), and edge servers, Kubernetes, and data services into Azure Resource Manager for unified governance, security, and management.

    175 GitHub stars~1.9k tokensUpdated 3 mo ago
    Auto-check passed
  • Azure Bastion Jit

    vinayaklatthe/microsoft-security-skills

    Guidance for secure remote VM management in Azure using Azure Bastion combined with Defender for Cloud just-in-time (JIT) VM access.

    175 GitHub stars~2.2k tokensUpdated 3 mo ago
    Auto-check passed
  • Azure Confidential Computing

    vinayaklatthe/microsoft-security-skills

    Guidance for Azure Confidential Computing — protecting data in use through hardware-based Trusted Execution Environments (TEEs).

    175 GitHub stars~2.4k tokensUpdated 3 mo ago
    Auto-check passed
  • Azure Ddos Protection

    vinayaklatthe/microsoft-security-skills

    Guidance for Azure DDoS Protection — Network Protection (per-VNet) and IP Protection (per public IP) tiers built on the same always-on Microsoft platform.

    175 GitHub stars~2k tokensUpdated 3 mo ago
    Auto-check passed

Categories

Questions about Entra Id Protection

What does Entra Id Protection do?

Guidance for Microsoft Entra ID Protection — risk-based identity security that detects user and sign-in risk and automates remediation. Entra Id Protection is an agent skill from vinayaklatthe/microsoft-security-skills. Guidance for Microsoft Entra ID Protection — risk-based identity security that detects user and sign-in risk and automates remediation.

When should I use Entra Id Protection?

Entra Id Protection fits situations like: on-prem AD attack detection (use defender-for-identity); CA policy authoring without risk signals (use conditional-access-mfa); PIM activation (use azure-pim).

How do I install Entra Id Protection in Claude Code?

Run `npx skills add vinayaklatthe/microsoft-security-skills --skill entra-id-protection -a claude-code`. Or copy the skill folder (skills/entra-id-protection in vinayaklatthe/microsoft-security-skills) into .claude/skills/entra-id-protection in your project. Claude Code loads it when a task matches its description.

How do I install Entra Id Protection in Codex?

Run `npx skills add vinayaklatthe/microsoft-security-skills --skill entra-id-protection -a codex`. Or copy the skill folder (skills/entra-id-protection in vinayaklatthe/microsoft-security-skills) into .agents/skills/entra-id-protection in your project. Codex loads it when a task matches its description.

Can I use Entra Id Protection in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vinayaklatthe/microsoft-security-skills --skill entra-id-protection -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/entra-id-protection, .gemini/skills/entra-id-protection, .github/skills/entra-id-protection and .opencode/skills/entra-id-protection in your project.

What does Entra Id Protection need to run?

SKILL.md names no scripts, command-line tools or credentials: Entra Id Protection is instructions for the agent only.

Does Entra Id Protection access the network?

SKILL.md names 1 domain. As links in the text: learn.microsoft.com. This is read from the text; nothing was executed.

Is Entra Id Protection safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Entra Id Protection use?

Entra Id Protection is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Entra Id Protection use?

About 1.6k tokens (SKILL.md is roughly 6.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Entra Id Protection?

Skills that share tags, products or a category with Entra Id Protection: Microsoft Azure Webjobs Extensions Authentication Events Dotnet (microsoft/skills, 3.1k stars), Entra App Registration (microsoft/GitHub-Copilot-for-Azure, 255 stars), Troubleshooting Authentication (microsoft-foundry/foundry-agent-webapp, 127 stars) and Iam Audit (briiirussell/cybersecurity-skills, 413 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Entra Id Protection?

vinayaklatthe (a GitHub user) maintains it in vinayaklatthe/microsoft-security-skills, which has 175 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on June 18, 2026.

Source: vinayaklatthe/microsoft-security-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.