entra-app-registration — Claude Code skill: setup and installation
This skill guides app registration in Microsoft Entra ID, OAuth 2.0 configuration, and MSAL integration. Use it for user sign-in or service-to-service authentication.
npx skills add microsoft/skills --skill entra-app-registration -a claude-codeWhat entra-app-registration does
The skill walks through choosing an app type, setting redirect URIs, and granting access to Microsoft APIs or your own APIs. It covers web apps, SPAs, mobile apps, and background services, with patterns for user sign-in and service-to-service authentication.
Its reference material includes Azure CLI commands, a Bicep example, OAuth flow guidance, and a console app example. MSAL is the recommended library, with options listed for .NET, JavaScript, and Python. A client secret is displayed only once when created, so save it securely at that point rather than placing it in source code. The guidance also covers certificates and federated identity credentials.
What it helps with
- register an application in Microsoft Entra ID
- set redirect URIs for an app type
- grant Microsoft Graph or custom API permissions
- add user sign-in with MSAL
- configure service authentication without user interaction
Example prompts for the agent
- Help me register a web app in Microsoft Entra ID and add MSAL sign-in.
- Set up redirect URIs and Microsoft Graph permissions for my SPA.
- Outline service authentication with the Client Credentials flow.
How to install entra-app-registration
1Skills CLI (Vercel)
npx skills add microsoft/skills --skill entra-app-registration -a claude-code2Manually: put the files in place
~/.claude/skills/entra-app-registration/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/entra-app-registration/
Manually: put the files in place
.agents/skills/entra-app-registration/SKILL.mdFor all projects use ~/.agents/skills/
Manually: put the files in place
.cursor/skills/entra-app-registration/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install microsoft/skills entra-app-registration2Manually: put the files in place
.github/skills/entra-app-registration/SKILL.mdPlatform CLI
gemini skills install https://github.com/microsoft/skills --path .github/plugins/azure-skills/skills/entra-app-registrationManually: put the files in place
.devin/skills/entra-app-registration/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about entra-app-registration
How do I install entra-app-registration in Claude Code?
Run npx skills add microsoft/skills --skill entra-app-registration -a claude-code. The skill file is at ~/.claude/skills/entra-app-registration/SKILL.md.
What does entra-app-registration do?
It guides app registration, OAuth 2.0 setup, and API permissions in Microsoft Entra ID. It also covers MSAL integration patterns.
Which MSAL libraries does the skill cover?
It lists Microsoft.Identity.Client for .NET, @azure/msal-browser and @azure/msal-node for JavaScript and TypeScript, and msal for Python.
Source text
SKILL.md · MIT
--- name: entra-app-registration description: "Guides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration. USE FOR: create app registration, register Azure AD app, configure OAuth, set up authentication, add API permissions, generate service principal, MSAL example, console app auth, Entra ID setup, Azure AD authentication. DO NOT USE FOR: Key Vault secrets (use azure-keyvault-expiration-audit), general Azure resource security guidance." license: MIT metadata: author: Microsoft version: "1.2.1" --- ## Overview Microsoft Entra ID (formerly Azure Active Directory) is Microsoft's cloud-based identity and access management service. App registrations allow applications to authenticate users and access Azure resources securely. ### Key Concepts | Concept | Description | |---------|-------------| | **App Registration** | Configuration that allows an app to use Microsoft identity platform | | **Application (Client) ID** | Unique identifier for your application | | **Tenant ID** | Unique identifier for your Azure AD tenant/directory | | **Client Secret** | Password for the application (confidential clients only) | | **Redirect URI** | URL where authentication responses are sent | | **API Permissions** | Access scopes your app requests | | **Service Principal** | Identity created in your tenant when you register an app | ### Application Types | Type | Use Case | |------|----------| | **Web Application** | Server-side apps, APIs | | **Single Page App (SPA)** | JavaScript/React/Angular apps | | **Mobile/Native App** | Desktop, mobile apps | | **Daemon/Service** | Background services, APIs | ## Core Workflow ### Step 1: Register the Application Create an app registration in the Azure portal or using Azure CLI. **Portal Method:** 1. Navigate to Azure Portal → Microsoft Entra ID → App registrations 2. Click "New registration" 3. Provide name, supported account types, and redirect URI 4. Click "Register" **CLI Method:** See [references/cli-commands.md](references/cli-commands.md) **IaC Method:** See [references/BICEP-EXAMPLE.bicep](references/BICEP-EXAMPLE.bicep) It's highly recommended to use the IaC to manage Entra app registration if you already use IaC in your project, need a scalable solution for managing lots of app registrations or need fine-grained audit history of the configuration changes. ### Step 2: Configure Authentication Set up authentication settings based on your application type. - **Web Apps**: Add redirect URIs, enable ID tokens if needed - **SPAs**: Add redirect URIs, enable implicit grant flow if necessary - **Mobile/Desktop**: Use `http://localhost` or custom URI scheme - **Services**: No redirect URI needed for client credentials flow ### Step 3: Configure API Permissions Grant your application permission to access Microsoft APIs or your own APIs. **Common Microsoft Graph Permissions:** - `User.Read` - Read user profile - `User.ReadWrite.All` - Read and write all users - `Directory.Read.All` - Read directory data - `Mail.Send` - Send mail as a user **Details:** See [references/api-permissions.md](references/api-permissions.md) ### Step 4: Create Client Credentials (if needed) For confidential client applications (web apps, services), create a client secret, certificate or federated identity credential. **Client Secret:** - Navigate to "Certificates & secrets" - Create new client secret - Copy the value immediately (only shown once) - Store securely (Key Vault recommended) **Certificate:** For production environments, use certificates instead of secrets for enhanced security. Upload certificate via "Certificates & secrets" section. **Federated Identity Credential:** For dynamically authenticating the confidential client to Entra platform. ### Step 5: Implement OAuth Flow Integrate the OAuth flow into your application code. **See:** - [references/oauth-flows.md](references/oauth-flows.md) - OAuth 2.0 flow details - [references/console-app-example.md](references/console-app-example.md) - Console app implementation ## Common Patterns ### Pattern 1: First-Time App Registration Walk user through their first app registration step-by-step. **Required Information:** - Application name - Application type (web, SPA, mobile, service) - Redirect URIs (if applicable) - Required permissions **Script:** See [references/first-app-registration.md](references/first-app-registration.md) ### Pattern 2: Console Application with User Authentication Create a .NET/Python/Node.js console app that authenticates users. **Required Information:** - Programming language (C#, Python, JavaScript, etc.) - Authentication library (MSAL recommended) - Required permissions **Example:** See [references/console-app-example.md](references/console-app-example.md) ### Pattern 3: Service-to-Service Authentication Set up daemon/service authentication without user interaction. **Required Information:** - Service/app name - Target API/resource - Whether to use secret or certificate **Implementation:** Use Client Credentials flow (see [references/oauth-flows.md#client-credentials-flow](references/oauth-flows.md#client-credentials-flow)) ## MCP Tools and CLI ### Azure CLI Commands | Command | Purpose | |---------|---------| | `az ad app create` | Create new app registration | | `az ad app list` | List app registrations | | `az ad app show` | Show app details | | `az ad app permission add` | Add API permission | | `az ad app credential reset` | Generate new client secret | | `az ad sp create` | Create service principal | **Complete reference:** See [references/cli-commands.md](references/cli-commands.md) ### Microsoft Authentication Library (MSAL) MSAL is the recommended library for integrating Microsoft identity platform. **Supported Languages:** - .NET/C# - `Microsoft.Identity.Client` - JavaScript/TypeScript - `@azure/msal-browser`, `@azure/msal-node` - Python - `msal` **Examples:** See [references/console-app-example.md](references/console-app-example.md) ## Security Best Practices | Practice | Recommendation | |----------|---------------| | **Never hardcode secrets** | Use environment variables, Azure Key Vault, or managed identity | | **Rotate secrets regularly** | Set expiration, automate rotation | | **Use certificates over secrets** | More secure for production | | **Least privilege permissions** | Request only required API permissions | | **Enable MFA** | Require multi-factor authentication for users | | **Use managed identity** | For Azure-hosted apps, avoid secrets entirely | | **Validate tokens** | Always validate issuer, audience, expiration | | **Use HTTPS only** | All redirect URIs must use HTTPS (except localhost) | | **Monitor sign-ins** | Use Entra ID sign-in logs for anomaly detection | ## SDK Quick References - **Azure Identity**: [Python](references/sdk/azure-identity-py.md) | [.NET](references/sdk/azure-identity-dotnet.md) | [TypeScript](references/sdk/azure-identity-ts.md) | [Java](references/sdk/azure-identity-java.md) | [Rust](references/sdk/azure-identity-rust.md) - **Key Vault (secrets)**: [Python](references/sdk/azure-keyvault-py.md) | [TypeScript](references/sdk/azure-keyvault-secrets-ts.md) - **Auth Events**: [.NET](references/sdk/microsoft-azure-webjobs-extensions-authentication-events-dotnet.md) ## References - [OAuth Flows](references/oauth-flows.md) - Detailed OAuth 2.0 flow explanations - [CLI Commands](references/cli-commands.md) - Azure CLI reference for app registrations - [Console App Example](references/console-app-example.md) - Complete working examples - [First App Registration](references/first-app-registration.md) - Step-by-step guide for beginners - [API Permissions](references/api-permissions.md) - Understanding and configuring permissions - [Troubleshooting](references/troubleshooting.md) - Common issues and solutions ## External Resources - [Microsoft Identity Platform Documentation](https://learn.microsoft.com/entra/identity-platform/) - [OAuth 2.0 and OpenID Connect protocols](https://learn.microsoft.com/entra/identity-platform/v2-protocols) - [MSAL Documentation](https://learn.microsoft.com/entra/msal/) - [Microsoft Graph API](https://learn.microsoft.com/graph/)
© Microsoft · MIT · microsoft/skills