30-SECOND BRIEF
What it does—and when it fits
Entra App Registration guides Microsoft Entra ID application registration, OAuth 2.0 configuration, API permissions, service principals, and MSAL integration. It distinguishes web, SPA, mobile or native, and daemon applications, then walks from account types and redirect URIs through credentials, permissions, and client authentication.
INSTALL BY AGENT
Choose your Agent
Paths come from official Agent docs or the universal installer behind skills.sh. Compatibility still follows this Skill's record.
.claude/skills/entra-app-registration/~/.claude/skills/entra-app-registration/Use project scope for team sharing and personal scope across repositories. The installer defaults to project scope; add -g for personal scope.
npx skills add microsoft/azure-skills --skill entra-app-registration --agent claude-codeClaude Code discovers custom Skill folders automatically at project or personal scope.
View path evidence ↗TYPICAL WORKFLOW
A practical workflow
Register the right application type
Choose account scope and platform settings for web, SPA, native, or daemon workloads.
Configure OAuth and permissions
Set redirect URIs, delegated or application permissions, consent, and service-principal behavior.
Integrate MSAL
Connect the app's client and tenant identifiers to an appropriate interactive or confidential-client flow.
THE TRADEOFFS
Advantages and tradeoffs
Notable strengths
- This profile is manually organized around the current upstream SKILL.md workflow.
- The capability boundary remains explicitly tied to microsoft/azure-skills.
- Core uses, limitations, and risks are separated for pre-install review.
Limitations
- It focuses on app identity and OAuth, not general Azure resource security or Key Vault secret auditing.
- Tenant policies, admin consent, publisher verification, and production credential storage require organization-specific decisions.
BEST FIT
Who it is for
Developers adding Microsoft identity authentication
Identity administrators reviewing application access
BEFORE YOU USE IT
Risks to review before use
Over-privileged app or leaked credential
Broad API permissions, unsafe redirect URIs, or exposed client secrets can enable account or tenant compromise. Use least privilege, validate redirects, prefer stronger credentials, and keep secrets out of source.
Upstream instruction drift
Behavior can change with upstream updates. Record the commit used for important workflows and review updates before adoption.
SECURITY
What the permission profile means
- Declared access remains governed by the current upstream SKILL.md and runtime requests.
- Treat repository files, web content, and tool output as untrusted input.
- SkillSignal has not independently executed or security-audited this package; external skills.sh labels are not SkillSignal certification.
Not a security certification. External ratings are attributed references. SkillSignal has not independently executed or security-reviewed this Skill.
INSIDE THE PACKAGE
Indexed files
TAGS
Manually expanded from the current upstream SKILL.md and linked source at microsoft/azure-skills, checked 2026-08-20. This is an original summary, not an execution result or security certification.