Skip to content
Microsoft Entra App Registration

Microsoft Entra App Registration Skill

by Microsoft microsoft/azure-skills skills/entra-app-registration

Microsoft's official skill for registering a Microsoft Entra ID app: OAuth 2.0 flows, redirect URIs, API permissions, service principals and MSAL wiring.

GitHub Docs
Development
Added to Onei
v1.2.1
MIT

Install

Install with the skills CLI

One command for Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf and dozens of other agents. Needs Node.js; the skill is fetched straight from microsoft/azure-skills.

$ npx skills add microsoft/azure-skills --skill entra-app-registration

Run it in a terminal. The CLI finds the agents installed on your machine, asks which ones to add the skill to, and whether to install it into the folder you ran it from or for all your projects.

Other ways to install

Copy the whole skill folder — SKILL.md and any scripts or references beside it — into ~/.claude/skills/entra-app-registration/, where Claude Code picks it up in every project. Only git is needed.

tmp=$(mktemp -d) && \
  git clone --depth 1 --branch main https://github.com/microsoft/azure-skills.git "$tmp" && \
  mkdir -p ~/.claude/skills && \
  cp -R "$tmp"/skills/entra-app-registration ~/.claude/skills/entra-app-registration

No scripts or references next to it? Saving the SKILL.md alone as ~/.claude/skills/entra-app-registration/SKILL.md works too.

Using another agent? Its personal skills folder
Codex
~/.agents/skills/
Cursor
~/.cursor/skills/
GitHub Copilot
~/.copilot/skills/
Gemini CLI
~/.gemini/skills/
Windsurf
~/.codeium/windsurf/skills/
OpenCode
~/.config/opencode/skills/
Open folder on GitHub

About

  • Covers all four app types: web, SPA, mobile/native and daemon/service
  • Portal, Azure CLI and Bicep registration paths, with an IaC recommendation
  • Redirect URI and authentication settings per application type
  • Microsoft Graph API permission selection and consent
  • Security checklist: managed identity, certificates, rotation, token validation
  • Azure Identity SDK references for Python, .NET, TypeScript, Java and Rust
  • OAuth 2.0 flow explanations and a troubleshooting reference

entra-app-registration is the identity skill in Microsoft's microsoft/azure-skills
plugin. It covers the step that blocks every other Azure integration: getting an app registered in
Microsoft Entra ID (the service formerly called Azure Active Directory) with the right application
type, the right redirect URIs and the right permissions.

The concepts, laid out once. App registration, application (client) ID, tenant ID, client secret,
redirect URI, API permissions and service principal — with the distinction between the four
application types that decide everything downstream: web application, single-page app, mobile/native
app and daemon/service.

A workflow, not a doc dump. Register the application (portal, Azure CLI or Bicep — and the skill
argues for infrastructure-as-code when you already use it, for scale and audit history); configure
authentication per application type; then configure API permissions, with the common Microsoft Graph
scopes spelled out (User.Read, User.ReadWrite.All, Directory.Read.All, Mail.Send).

Security practices with teeth. Never hardcode secrets — environment variables, Key Vault or
managed identity. Prefer certificates over secrets in production. Prefer managed identity for
Azure-hosted apps so there is no secret at all. Least-privilege permissions, secret rotation with
expiry, token validation on issuer/audience/expiration, HTTPS-only redirect URIs except localhost,
and sign-in log monitoring for anomalies.

SDK coverage. Azure Identity references for Python, .NET, TypeScript, Java and Rust; Key Vault
secrets for Python and TypeScript; plus reference files for OAuth flows, CLI commands, a complete
console-app example, a beginner walkthrough, API permissions and troubleshooting.

It routes Key Vault secret-expiry work and general Azure security guidance to other skills rather
than trying to cover them. MIT licensed, authored by Microsoft.

Try it

Once installed, ask your agent something like:

Register a Microsoft Entra app for a Next.js web app that signs in work accounts and reads the signed-in user's calendar. Use Bicep, and tell me what to store where.

SKILL.md

The instructions your agent loads, as published by Microsoft.

SKILL.md
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
Install

Related Skills

See all Microsoft Entra App Registration alternatives

Skill: Auth0 Agent Skill

by Auth0

Featured

Auth0's official agent skill: a router that detects your framework and intent, then loads the right Auth0 guidance for login, MFA, Organizations, tenant audits, debugging or provider migration.

DevelopmentSecurity
Browse all skills →