Entra App Registration
microsoft/GitHub-Copilot-for-Azure
Guides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration.
Guidance for Microsoft Entra ID (formerly Azure AD) — cloud identity and access management and the control plane for Zero Trust.
Install Entra Id
$ npx skills add vinayaklatthe/microsoft-security-skills --skill entra-id -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install vinayaklatthe/microsoft-security-skills entra-id --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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 .claude/skills/entra-id && rm -rf skills-srcUse ~/.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/
Install the "entra-id" agent skill from https://github.com/vinayaklatthe/microsoft-security-skills/tree/main/skills/entra-id into .claude/skills/entra-id/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "entra-id", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/vinayaklatthe/microsoft-security-skills/tree/main/skills/entra-idType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add vinayaklatthe/microsoft-security-skills --skill entra-id -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install vinayaklatthe/microsoft-security-skills entra-id --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vinayaklatthe/microsoft-security-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/entra-id .agents/skills/entra-id && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "entra-id" agent skill from https://github.com/vinayaklatthe/microsoft-security-skills/tree/main/skills/entra-id into .agents/skills/entra-id/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "entra-id", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vinayaklatthe/microsoft-security-skills --skill entra-id -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install vinayaklatthe/microsoft-security-skills entra-id --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vinayaklatthe/microsoft-security-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/entra-id .cursor/skills/entra-id && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "entra-id" agent skill from https://github.com/vinayaklatthe/microsoft-security-skills/tree/main/skills/entra-id into .cursor/skills/entra-id/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "entra-id", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/vinayaklatthe/microsoft-security-skills.git --path skills/entra-id--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add vinayaklatthe/microsoft-security-skills --skill entra-id -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install vinayaklatthe/microsoft-security-skills entra-id --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vinayaklatthe/microsoft-security-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/entra-id .gemini/skills/entra-id && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "entra-id" agent skill from https://github.com/vinayaklatthe/microsoft-security-skills/tree/main/skills/entra-id into .gemini/skills/entra-id/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "entra-id", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install vinayaklatthe/microsoft-security-skills entra-idInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add vinayaklatthe/microsoft-security-skills --skill entra-id -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/vinayaklatthe/microsoft-security-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/entra-id .github/skills/entra-id && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "entra-id" agent skill from https://github.com/vinayaklatthe/microsoft-security-skills/tree/main/skills/entra-id into .github/skills/entra-id/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "entra-id", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vinayaklatthe/microsoft-security-skills --skill entra-id -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install vinayaklatthe/microsoft-security-skills entra-id --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vinayaklatthe/microsoft-security-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/entra-id .opencode/skills/entra-id && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "entra-id" agent skill from https://github.com/vinayaklatthe/microsoft-security-skills/tree/main/skills/entra-id into .opencode/skills/entra-id/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "entra-id", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
entra-id- GitHub stars
- 175
- Token cost
- ~2.3k tokens
- SKILL.md length
- 997 words
- Files
- 1
- Skills in repo
- 50
- Repo updated
- First seen
- Licence
- MIT
At a glance
Guidance for Microsoft Entra ID (formerly Azure AD) — cloud identity and access management and the control plane for Zero Trust.
- Works in 7 steps: Tenant & identity model — Decide… → Hybrid identity — Choose Entra Cloud… → Authentication methods - move to… → …
- Risk-based detection (use entra-id-protection)
- SKILL.md covers When to use, Map the identity goal 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 is an agent skill from vinayaklatthe/microsoft-security-skills. Guidance for Microsoft Entra ID (formerly Azure AD) — cloud identity and access management and the control plane for Zero Trust. Covers tenant and identity model, authentication methods (passkeys, FIDO2, certificate-based), hybrid identity with Entra Connect or Cloud Sync, app registrations and consent governance, groups and administrative units, break-glass accounts, and Zero Trust identity foundations. WHEN: Microsoft Entra ID, Azure AD, identity provider setup, SSO, hybrid identity, Entra Connect, Cloud Sync…
Its SKILL.md is about 2.3k 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, OAuth and OpenID Connect and 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)
- Conditional Access design (use conditional-access-mfa)
- PIM (use azure-pim)
- Identity governance lifecycle (use entra-id-governance)
Example prompts
- “/entra-id”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Tenant & identity model — Decide cloud-only vs hybrid. Define naming conventions for
- Hybrid identity — Choose Entra Cloud Sync for new deployments (agent-based,
- Authentication methods - move to phishing-resistant — Manage via the **Authentication
- Applications & consent governance — Use the gallery for SSO where available. Enable
- Self-service & lifecycle — Enable SSPR with writeback for hybrid users. Configure My
- Break-glass accounts — Create two cloud-only emergency access accounts. Exclude
- Block legacy auth and weak methods — Use Conditional Access (separate skill) to block
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 loads about 2.3k tokens when it runs. Until then it costs about 239 tokens; SKILL.md has 997 words of instructions outside code blocks.
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). 997 words, ~2,319 tokens.
Download SKILL.mdSave it as
.claude/skills/entra-id/SKILL.md (or your agent's skills folder).- name
- entra-id
- description
- Guidance for Microsoft Entra ID (formerly Azure AD) — cloud identity and access management and the control plane for Zero Trust. Covers tenant and identity model, authentication methods (passkeys, FIDO2, certificate-based), hybrid identity with Entra Connect or Cloud Sync, app registrations and consent governance, groups and administrative units, break-glass accounts, and Zero Trust identity foundations. WHEN: Microsoft Entra ID, Azure AD, identity provider setup, SSO, hybrid identity, Entra Connect, Cloud Sync, authentication methods, passwordless, passkey, FIDO2, certificate-based auth, app registration, enterprise application, illicit consent grant, break-glass account, emergency access, administrative units, SSPR, password writeback. DO NOT USE for risk-based detection (use entra-id-protection), Conditional Access design (use conditional-access-mfa), PIM (use azure-pim), or identity governance lifecycle (use entra-id-governance).
- license
- MIT
- metadata.author
- Microsoft
- metadata.version
- 0.1.0
Microsoft Entra ID
Microsoft Entra ID (formerly Azure Active Directory) is the cloud identity and access management service that authenticates users, devices, and workloads. It is the control plane for Zero Trust and the foundation every other Microsoft security control assumes is healthy.
When to use
Establishing the identity foundation: tenants, users/groups, authentication methods, SSO for apps, and hybrid identity with on-premises Active Directory. Use this skill before configuring Conditional Access, Identity Protection, or PIM - they all assume a clean Entra ID baseline.
Do not use this skill for risk-based sign-in detection (entra-id-protection), policy
enforcement (conditional-access-mfa), just-in-time admin roles (azure-pim), or lifecycle
workflows (entra-id-governance).
Map the identity goal to the right Entra control
| If the goal is... | Use | Notes |
|---|---|---|
| Sync on-prem AD users to cloud | Entra Cloud Sync (preferred new) or Entra Connect Sync | Cloud Sync is lighter, no server farm |
| Federate sign-in to on-prem | AD FS (legacy) or Pass-Through Authentication | Avoid new AD FS deployments; prefer PHS + WHfB |
| Replace passwords | Passkeys (FIDO2) > Windows Hello for Business > Microsoft Authenticator passwordless | Phishing-resistant only |
| Single sign-on to SaaS | Enterprise Applications (gallery or non-gallery) | OIDC > SAML where supported |
| Self-service password reset | SSPR with cloud writeback (hybrid) | Requires Entra ID P1 |
| Delegated admin scoped to a region/BU | Administrative Units | Combine with custom roles for least privilege |
| App calls Microsoft Graph or another API | App Registration + delegated/application permissions | Require admin consent workflow for risky scopes |
| Emergency tenant access if MFA breaks | Break-glass accounts (2x cloud-only, excluded from CA) | Hardware FIDO2 only; alerted on every sign-in |
Rule of thumb: if you are about to type a username and password into a Microsoft service in 2026, stop. Move to passkeys or WHfB. Password reuse + phishing is still the #1 root cause in identity incident response.
Approach
Tenant & identity model — Decide cloud-only vs hybrid. Define naming conventions for users, groups (assigned vs dynamic), and administrative units. Block guest invites at tenant level by default; allow per-collaboration scenario. Verify:
Get-MgPolicyAuthorizationPolicyshowsallowedToCreateApps = falsefor default users; admin consent workflow is enabled.Hybrid identity — Choose Entra Cloud Sync for new deployments (agent-based, lightweight, supports disconnected forests). Use Entra Connect Sync only if you need PHS + write-back features Cloud Sync doesn't yet support. Avoid new AD FS - it adds an on-prem dependency and an attack surface (MDI sensor required). Verify:
Get-MgDirectoryOnPremisesSynchronizationshows healthy sync; password hash sync enabled.Authentication methods - move to phishing-resistant — Manage via the Authentication methods policy (replaces legacy MFA + SSPR registration policies). Roll out in this order: Authenticator (push + number matching) → WHfB on managed devices → FIDO2 passkeys for admins → broad passkey rollout. Disable SMS as a primary method. Verify:
User Registration Detailsreport shows > 90% of users with at least one phishing-resistant method.Applications & consent governance — Use the gallery for SSO where available. Enable admin consent workflow so users request high-risk permissions instead of granting them. Run the Risky Apps report monthly. Apply least-privilege Graph permissions and review app credentials (secrets vs certs vs federated identity). Verify: no consented apps with
Application.ReadWrite.AllorDirectory.ReadWrite.Alloutside the approved list.Self-service & lifecycle — Enable SSPR with writeback for hybrid users. Configure My Account / My Apps. Use dynamic groups for attribute-driven membership (department, country, employeeType).
Break-glass accounts — Create two cloud-only emergency access accounts. Exclude from all Conditional Access policies. Authenticate only with FIDO2 hardware keys stored physically separately. Alert on every sign-in via Sentinel. Verify: monthly sign-in test from each break-glass account; alert fires within 5 minutes.
Block legacy auth and weak methods — Use Conditional Access (separate skill) to block legacy authentication protocols (POP, IMAP, SMTP AUTH, basic auth). Disable SMS / voice as primary MFA methods.
Show full SKILL.md (396 more words)Show less
Guardrails
- Break-glass accounts are sacred. Two of them, cloud-only, hardware FIDO2, excluded from every CA policy, monitored on every sign-in. Test monthly. If you skip this, you can lose the tenant in a CA misconfiguration.
- Avoid new AD FS deployments. It's an on-prem identity dependency, an attack surface, and a maintenance burden. PHS + WHfB covers nearly every requirement.
- Block legacy authentication. POP, IMAP, SMTP AUTH, basic auth bypass MFA. Block via Conditional Access, then monitor the sign-in logs for stragglers for 30 days.
- Govern app consent. Illicit consent grants are how attackers stay resident after password reset. Enable the admin consent workflow and review the Risky Apps report.
- Don't use group-based licensing as the only assignment mechanism for admin accounts. If the group sync breaks, admins lose their licence and access. Direct-assign for break-glass and tier-0 admins.
- Cloud Sync is preferred over Connect Sync for new builds. Lighter, no server farm, fewer failure modes.
Common anti-patterns
- "We use SMS for MFA - it's good enough" - SMS is phishable and SIM-swappable. Treat as recovery factor only, never as primary.
- "One break-glass account in Keepass" - Single point of failure and not auditable. Two hardware-key accounts with separated custody.
- "Federated sign-in via AD FS because that's how we always did it" - In 2026 this adds cost and risk. Move to PHS + Conditional Access unless there's a specific federation requirement.
- "Allow user app consent for all permissions" - Tenant gets cluttered with risky consented apps. Enable admin consent workflow.
- "Don't bother with Administrative Units, just use global admin" - Breaks separation of duties and bypasses RBAC. Scope helpdesk and regional admins to AUs.
- "Disable security defaults but skip Conditional Access for a week" - Tenant is wide open during that gap. Enable CA policies before disabling defaults.
Example prompts
Design a hybrid identity model with Entra Cloud Sync and password hash sync.Plan a rollout from passwords to passkeys for 5,000 users.Configure break-glass accounts for our Entra tenant and the monitoring alert.Move users off SMS MFA - what's the migration path?Prevent illicit consent grants in our Entra ID tenant.Configure SSPR with writeback for a hybrid environment.When should I use Administrative Units vs custom roles for delegated admin?
Microsoft Learn
- Overview: https://learn.microsoft.com/entra/fundamentals/whatis
- Entra Cloud Sync: https://learn.microsoft.com/entra/identity/hybrid/cloud-sync/what-is-cloud-sync
- Authentication methods policy: https://learn.microsoft.com/entra/identity/authentication/concept-authentication-methods
- Passkeys (FIDO2): https://learn.microsoft.com/entra/identity/authentication/concept-authentication-passwordless
- Break-glass accounts: https://learn.microsoft.com/entra/identity/role-based-access-control/security-emergency-access
- Admin consent workflow: https://learn.microsoft.com/entra/identity/enterprise-apps/configure-admin-consent-workflow
- Administrative Units: https://learn.microsoft.com/entra/identity/role-based-access-control/administrative-units
- Block legacy authentication: https://learn.microsoft.com/entra/identity/conditional-access/policy-block-legacy-authentication
- Zero Trust identity: https://learn.microsoft.com/security/zero-trust/deploy/identity
© 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 of vinayaklatthe/microsoft-security-skills.
Open the folder on GitHubat commit 15f16df
Compare with similar skills
Entra Id 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Entra Id this skillvinayaklatthe/microsoft-security-skills | 175 | — | ~2.3k | Automated safety check: Pass | MIT | |
| Entra App Registrationmicrosoft/GitHub-Copilot-for-Azure | 255 | 2 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Iam Auditbriiirussell/cybersecurity-skills | 413 | — | ~3.1k | Automated safety check: Notes | MIT | |
| Apex Entra App Registrationjonathan-vella/apex | 217 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Azure AuthLeoYeAI/openclaw-master-skills | 2.2k | — | ~4.9k | Automated safety check: Notes | MIT | |
| Entra Agent Idmicrosoft/GitHub-Copilot-for-Azure | 255 | 2 repos | ~4k | Automated safety check: Pass | MIT |
Similar skills
- Official
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…
Apex Entra App Registration
jonathan-vella/apex
WORKFLOW SKILL — Guides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration.
Azure Auth
LeoYeAI/openclaw-master-skills
Microsoft Entra ID (Azure AD) authentication for React SPAs with MSAL.js and Cloudflare Workers JWT validation using jose library.
- Official
Entra Agent Id
microsoft/GitHub-Copilot-for-Azure
Provision Microsoft Entra Agent Identity Blueprints, BlueprintPrincipals, and per-instance Agent Identities via Microsoft Graph, and configure OAuth 2.0 token exchange (fmipath, OBO, cross-tenant)…
Azure APIM Policy Authoring
thomast1906/github-copilot-agent-skills
Generates Azure API Management policy XML for authentication, rate limiting, CORS, error handling and transformations, consulting Azure best-practice and documentation tools first.
More from vinayaklatthe/microsoft-security-skills
All 50 skills in this repoAPI 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…
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…
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.
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.
Azure Confidential Computing
vinayaklatthe/microsoft-security-skills
Guidance for Azure Confidential Computing — protecting data in use through hardware-based Trusted Execution Environments (TEEs).
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.
Related
Works with
Categories
Questions about Entra Id
What does Entra Id do?
Guidance for Microsoft Entra ID (formerly Azure AD) — cloud identity and access management and the control plane for Zero Trust. Entra Id is an agent skill from vinayaklatthe/microsoft-security-skills. Guidance for Microsoft Entra ID (formerly Azure AD) — cloud identity and access management and the control plane for Zero Trust.
When should I use Entra Id?
Entra Id fits situations like: risk-based detection (use entra-id-protection); conditional Access design (use conditional-access-mfa); PIM (use azure-pim); identity governance lifecycle (use entra-id-governance).
How do I install Entra Id in Claude Code?
Run `npx skills add vinayaklatthe/microsoft-security-skills --skill entra-id -a claude-code`. Or copy the skill folder (skills/entra-id in vinayaklatthe/microsoft-security-skills) into .claude/skills/entra-id in your project. Claude Code loads it when a task matches its description.
How do I install Entra Id in Codex?
Run `npx skills add vinayaklatthe/microsoft-security-skills --skill entra-id -a codex`. Or copy the skill folder (skills/entra-id in vinayaklatthe/microsoft-security-skills) into .agents/skills/entra-id in your project. Codex loads it when a task matches its description.
Can I use Entra Id 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 -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, .gemini/skills/entra-id, .github/skills/entra-id and .opencode/skills/entra-id in your project.
What does Entra Id need to run?
SKILL.md names no scripts, command-line tools or credentials: Entra Id is instructions for the agent only.
Does Entra Id 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 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 use?
Entra Id 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 use?
About 2.3k tokens (SKILL.md is roughly 9.3k 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?
Skills that share tags, products or a category with Entra Id: Entra App Registration (microsoft/GitHub-Copilot-for-Azure, 255 stars), Iam Audit (briiirussell/cybersecurity-skills, 413 stars), Apex Entra App Registration (jonathan-vella/apex, 217 stars) and Azure Auth (LeoYeAI/openclaw-master-skills, 2.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Entra Id?
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.