Agent skill

Entra Id Governance

by vinayaklatthe in vinayaklatthe/microsoft-security-skills

Guidance for Microsoft Entra ID Governance — automating identity lifecycle and access with entitlement management (access packages), access reviews, lifecycle workflows for joiner-mover-leaver…

MITAuto-check passedSecurity

Install Entra Id Governance

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

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

GitHub CLI
$ gh skill install vinayaklatthe/microsoft-security-skills entra-id-governance --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-governance .claude/skills/entra-id-governance && 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-governance
GitHub stars
175
Token cost
~2k tokens
SKILL.md length
828 words
Files
1
Skills in repo
50
Repo updated
First seen
Licence
MIT

At a glance

Guidance for Microsoft Entra ID Governance — automating identity lifecycle and access with entitlement management (access packages), access reviews, lifecycle workflows for joiner-mover-leaver…

  • Works in 6 steps: Define the catalogue — Access packages… → Build access packages with policies —… → Configure access reviews safely — Set… → …
  • Risk-based detection (use entra-id-protection)
  • SKILL.md covers When to use, Pick the right governance…, Approach and Guardrails, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Entra Id Governance is an agent skill from vinayaklatthe/microsoft-security-skills. Guidance for Microsoft Entra ID Governance — automating identity lifecycle and access with entitlement management (access packages), access reviews, lifecycle workflows for joiner-mover-leaver, separation of duties, and guest access governance. Covers when to use access packages vs direct group assignment, reviewer choice and fallback actions, and integration with PIM for privileged access. WHEN: Entra ID Governance, entitlement management, access packages, access reviews, lifecycle workflows, joiner mover…

Its SKILL.md is about 2k 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 Security, covering Access reviews and audit trails. 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

  • Risk-based detection (use entra-id-protection)
  • CA policy authoring (use conditional-access-mfa)
  • PIM activation (use azure-pim)

Example prompts

  • “/entra-id-governance”

Workflow steps

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

  1. Define the catalogue — Access packages live in a catalogue. Catalogues map to a
  2. Build access packages with policies — Each package has resources (groups, apps,
  3. Configure access reviews safely — Set reviewer (manager > self > specific user),
  4. Lifecycle workflows for JML — Build three core flows: Pre-hire (T-7 days),
  5. Separation of duties on access packages — Mark incompatible packages (e.g. "Accounts
  6. Guest governance — All B2B guests via access packages with expiration. Run a quarterly

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 Governance loads about 2k tokens when it runs. Until then it costs about 210 tokens; SKILL.md has 828 words of instructions outside code blocks.

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

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). 828 words, ~1,963 tokens.

Download SKILL.mdSave it as .claude/skills/entra-id-governance/SKILL.md (or your agent's skills folder).
name
entra-id-governance
description
Guidance for Microsoft Entra ID Governance — automating identity lifecycle and access with entitlement management (access packages), access reviews, lifecycle workflows for joiner-mover-leaver, separation of duties, and guest access governance. Covers when to use access packages vs direct group assignment, reviewer choice and fallback actions, and integration with PIM for privileged access. WHEN: Entra ID Governance, entitlement management, access packages, access reviews, lifecycle workflows, joiner mover leaver, JML, certify access, separation of duties, govern guest access, B2B guest expiration, identity lifecycle automation, sponsor approval, recertify access. DO NOT USE for risk-based detection (use entra-id-protection), CA policy authoring (use conditional-access-mfa), or PIM activation (use azure-pim).
license
MIT
metadata.author
Microsoft
metadata.version
0.1.0

Microsoft Entra ID Governance

Entra ID Governance ensures the right identities have the right access to the right resources at the right time. It automates identity lifecycle (JML) and access governance for employees, partners, and guests. Requires the Entra ID Governance SKU (P2 + Governance add-on, or M365 E5 + Governance).

When to use

Automating access requests/approvals, recurring access certification, and joiner-mover-leaver provisioning. Use this skill to choose between access packages and direct group assignment, configure access reviews safely, and run lifecycle workflows.

Do not use this skill for risk detection (entra-id-protection), Conditional Access (conditional-access-mfa), or PIM activation (azure-pim).

Pick the right governance mechanism

If the goal is...UseNotes
Self-service access request with approvalEntitlement management - access packageIncludes guests; sponsor or manager approval
Time-bound access for a projectAccess package with expirationAuto-revokes; safer than group
Govern an existing privileged groupPIM for Groups (separate skill)Just-in-time, not lifecycle
Recertify membership of a sensitive groupAccess review on the groupManager or self-attestation
Recertify access to an appAccess review on app assignmentsCatches stale SaaS access
Auto-provision new joinersLifecycle workflow - joinerPre-hire setup, welcome email
Auto-revoke leaver accessLifecycle workflow - leaverDisable, group removal, license drop
Move to new department auto-adjust accessLifecycle workflow - mover + dynamic groupsAttribute-driven
Catch toxic role combos (e.g. AP + AR)Separation of duties on access packageHard-block incompatible packages

Rule of thumb: if humans request the access, use an access package. If the system grants the access from HR attributes, use lifecycle workflows + dynamic groups. Direct group assignment is the legacy default and rarely correct in 2026.

Approach

  1. Define the catalogue — Access packages live in a catalogue. Catalogues map to a business owner (HR, Finance, Engineering platform team). Catalogue owners are accountable; IT facilitates. Verify: each catalogue has a named non-IT owner.

  2. Build access packages with policies — Each package has resources (groups, apps, SharePoint sites), eligible requesters (internal users, specific connected orgs, all external), and an assignment policy (approval, expiration, attribute requirements). Verify: every package has expiration set; no perpetual access.

  3. Configure access reviews safely — Set reviewer (manager > self > specific user), recurrence (quarterly Tier 0, bi-annually Tier 1, annually Tier 2). Critical: choose "no response" action carefully - auto-remove on no response is safer for low-risk resources but dangerous if the reviewer is on leave. Verify: reviewer escalation enabled; "no response" defaults documented per review.

  4. Lifecycle workflows for JML — Build three core flows: Pre-hire (T-7 days), Joiner (start date), Leaver (last day). Use HR attributes as triggers (employeeType, employeeHireDate, accountEnabled). Verify: leaver flow disables account, removes from all groups, revokes sessions, within 1 hour of HR attribute change.

  5. Separation of duties on access packages — Mark incompatible packages (e.g. "Accounts Payable" + "Vendor Master Data Editor"). System blocks the second request with audit log.

  6. Guest governance — All B2B guests via access packages with expiration. Run a quarterly review of guests with no recent activity (use signInActivity filter). Remove inactive guests automatically. Verify: guests created outside an access package = 0 in monthly report.

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

Guardrails

  • Prioritise leaver/deprovisioning automation - orphaned access is a common breach root cause. Leaver workflow within 1 hour of HR change, hard, not negotiable.
  • Set review reviewers and fallback actions carefully so "no response" doesn't auto-approve. Default to "no response = remove" with reviewer escalation.
  • Access packages for guests, always. B2B invitations outside packages bypass expiration and reviews.
  • Separation of duties only works if both packages are governed. If one role assignment is direct (not via package), SoD won't see it.
  • Lifecycle workflows are triggered by attributes. If HR doesn't push reliable attribute data, workflows won't fire. Validate the HR sync before relying on automation.
  • Don't put PIM-eligible roles in access packages. Use PIM for Groups so activation is separate from assignment.

Common anti-patterns

  • "Provision via Active Directory groups, deprovision via ticket" - Asymmetric, leaks access. Both sides need to be automated.
  • "Access reviews once a year" - 12 months of drift. Quarterly for sensitive resources.
  • "Reviewer = the resource owner" - Owner has bias to approve. Manager of the user is better; self-review only for low-risk.
  • "Guest invitations from any user" - Untracked guests sprawl. Restrict invitations to access package requests + a small invitations team.
  • "Lifecycle workflow runs on Day 1" - Joiner needs access ready before Day 1. Pre-hire flow at T-7 days.
  • "Direct group assignment is faster than building a package" - Faster once, slower forever after (no review, no expiration, no audit).

Example prompts

  • Build an access package for guest contractors with sponsor approval and 90-day expiration.
  • Set up lifecycle workflows for pre-hire, joiner, and leaver using HR attributes.
  • Configure quarterly access reviews on our privileged group with manager review.
  • Enforce separation of duties between "Accounts Payable" and "Vendor Master" access packages.
  • Audit and remove inactive guests with no sign-in in 90 days.
  • Move from direct group assignment to access packages for self-service.

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-governance of vinayaklatthe/microsoft-security-skills.

Open the folder on GitHubat commit 15f16df

Compare with similar skills

Entra Id Governance 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 Governance compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Entra Id Governance this skillvinayaklatthe/microsoft-security-skills175—~2kAutomated safety check: PassMIT
Implementing Azure Ad Privileged Identity Managementmukul975/Anthropic-Cybersecurity-Skills34k—~2.6kAutomated safety check: PassApache-2.0
Detecting Azure Service Principal Abusemukul975/Anthropic-Cybersecurity-Skills34k—~2.1kAutomated safety check: PassApache-2.0
Implementing Identity Verification For Zero Trustmukul975/Anthropic-Cybersecurity-Skills34k—~2.4kAutomated safety check: PassApache-2.0
Detecting Azure Lateral Movementmukul975/Anthropic-Cybersecurity-Skills34k—~808Automated safety check: PassApache-2.0
Attacking Entra Idtrilwu/secskills157—~4.3kAutomated safety check: PassMIT

Similar skills

  • Implementing Azure Ad Privileged Identity Management

    mukul975/Anthropic-Cybersecurity-Skills

    Configure Microsoft Entra Privileged Identity Management (PIM) to convert standing privileged assignments into eligible, time-bound roles requiring justification, MFA, and approval, covering Entra…

    34k GitHub stars~2.6k tokensUpdated 1 mo ago
    SecurityAuto-check passed
  • Detecting Azure Service Principal Abuse

    mukul975/Anthropic-Cybersecurity-Skills

    Detect Azure service principal abuse in Microsoft Entra ID using KQL detection queries (Sentinel/Splunk) against Azure AD Audit and Sign-in Logs, covering added credentials, privileged role…

    34k GitHub stars~2.1k tokensUpdated 1 mo ago
    SecurityAuto-check passed
  • Implementing Identity Verification For Zero Trust

    mukul975/Anthropic-Cybersecurity-Skills

    Implements continuous, risk-adaptive identity verification for zero trust using phishing-resistant MFA (FIDO2/WebAuthn), risk-based conditional access, and identity governance aligned with NIST SP…

    34k GitHub stars~2.4k tokensUpdated 1 mo ago
    SecurityAuto-check passed
  • Detecting Azure Lateral Movement

    mukul975/Anthropic-Cybersecurity-Skills

    Detect lateral movement in Azure AD/Entra ID environments using Microsoft Graph API audit logs, Azure Sentinel KQL hunting queries, and sign-in anomaly correlation to identify privilege escalation…

    34k GitHub stars~808 tokensUpdated 1 mo ago
    SecurityAuto-check passed
  • Attacking Entra Id

    trilwu/secskills

    Attack and enumerate Azure AD / Entra ID tenants — initial recon with AADInternals and ROADtools, password spraying, token theft (PRT, CAE, refresh tokens), application and service principal abuse…

    157 GitHub stars~4.3k tokensUpdated 1 mo ago
    SecurityAuto-check passed
  • 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

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 Governance

What does Entra Id Governance do?

Guidance for Microsoft Entra ID Governance — automating identity lifecycle and access with entitlement management (access packages), access reviews, lifecycle workflows for joiner-mover-leaver…. Entra Id Governance is an agent skill from vinayaklatthe/microsoft-security-skills. Guidance for Microsoft Entra ID Governance — automating identity lifecycle and access with entitlement management (access packages), access reviews, lifecycle workflows for joiner-mover-leaver, separation of duties, and guest access governance.

When should I use Entra Id Governance?

Entra Id Governance fits situations like: risk-based detection (use entra-id-protection); CA policy authoring (use conditional-access-mfa); PIM activation (use azure-pim).

How do I install Entra Id Governance in Claude Code?

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

How do I install Entra Id Governance in Codex?

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

Can I use Entra Id Governance 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-governance -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-governance, .gemini/skills/entra-id-governance, .github/skills/entra-id-governance and .opencode/skills/entra-id-governance in your project.

What does Entra Id Governance need to run?

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

Does Entra Id Governance 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 Governance 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 Governance use?

Entra Id Governance 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 Governance use?

About 2k tokens (SKILL.md is roughly 7.9k 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 Governance?

Skills that share tags, products or a category with Entra Id Governance: Implementing Azure Ad Privileged Identity Management (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Detecting Azure Service Principal Abuse (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Implementing Identity Verification For Zero Trust (mukul975/Anthropic-Cybersecurity-Skills, 34k stars) and Detecting Azure Lateral Movement (mukul975/Anthropic-Cybersecurity-Skills, 34k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Entra Id Governance?

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.