entra app registration

Skill

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: Azure RBAC or role assignments (use azure-rbac), Key Vault secrets (use azure-keyvault-expiration-audit), general Azure resource security guidance.

Files17
  • @skills/entra-app-registration/SKILL.md
  • @skills/entra-app-registration/references/BICEP-EXAMPLE.bicep
  • @skills/entra-app-registration/references/api-permissions.md
  • @skills/entra-app-registration/references/auth-best-practices.md
  • @skills/entra-app-registration/references/cli-commands.md
  • @skills/entra-app-registration/references/console-app-example.md
  • @skills/entra-app-registration/references/first-app-registration.md
  • @skills/entra-app-registration/references/oauth-flows.md
  • @skills/entra-app-registration/references/sdk/azure-identity-dotnet.md
  • @skills/entra-app-registration/references/sdk/azure-identity-java.md
  • @skills/entra-app-registration/references/sdk/azure-identity-py.md
  • @skills/entra-app-registration/references/sdk/azure-identity-rust.md
  • @skills/entra-app-registration/references/sdk/azure-identity-ts.md
  • @skills/entra-app-registration/references/sdk/azure-keyvault-py.md
  • @skills/entra-app-registration/references/sdk/azure-keyvault-secrets-ts.md
  • @skills/entra-app-registration/references/sdk/microsoft-azure-webjobs-extensions-authentication-events-dotnet.md
  • @skills/entra-app-registration/references/troubleshooting.md

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

ConceptDescription
App RegistrationConfiguration that allows an app to use Microsoft identity platform
Application (Client) IDUnique identifier for your application
Tenant IDUnique identifier for your Azure AD tenant/directory
Client SecretPassword for the application (confidential clients only)
Redirect URIURL where authentication responses are sent
API PermissionsAccess scopes your app requests
Service PrincipalIdentity created in your tenant when you register an app

Application Types

TypeUse Case
Web ApplicationServer-side apps, APIs
Single Page App (SPA)JavaScript/React/Angular apps
Mobile/Native AppDesktop, mobile apps
Daemon/ServiceBackground 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 [blocked] IaC Method: See references/BICEP-EXAMPLE.bicep [blocked]
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 [blocked]

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 [blocked] - OAuth 2.0 flow details
  • references/console-app-example.md [blocked] - 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 [blocked]

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 [blocked]

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 [blocked])

MCP Tools and CLI

Azure CLI Commands

CommandPurpose
az ad app createCreate new app registration
az ad app listList app registrations
az ad app showShow app details
az ad app permission addAdd API permission
az ad app credential resetGenerate new client secret
az ad sp createCreate service principal
Complete reference: See references/cli-commands.md [blocked]

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 [blocked]

Security Best Practices

PracticeRecommendation
Never hardcode secretsUse environment variables, Azure Key Vault, or managed identity
Rotate secrets regularlySet expiration, automate rotation
Use certificates over secretsMore secure for production
Least privilege permissionsRequest only required API permissions
Enable MFARequire multi-factor authentication for users
Use managed identityFor Azure-hosted apps, avoid secrets entirely
Validate tokensAlways validate issuer, audience, expiration
Use HTTPS onlyAll redirect URIs must use HTTPS (except localhost)
Monitor sign-insUse Entra ID sign-in logs for anomaly detection

SDK Quick References

  • Azure Identity: Python [blocked] | .NET [blocked] | TypeScript [blocked] | Java [blocked] | Rust [blocked]
  • Key Vault (secrets): Python [blocked] | TypeScript [blocked]
  • Auth Events: .NET [blocked]

References

  • OAuth Flows [blocked] - Detailed OAuth 2.0 flow explanations
  • CLI Commands [blocked] - Azure CLI reference for app registrations
  • Console App Example [blocked] - Complete working examples
  • First App Registration [blocked] - Step-by-step guide for beginners
  • API Permissions [blocked] - Understanding and configuring permissions
  • Troubleshooting [blocked] - Common issues and solutions

External Resources

entra-app-registration — Kortix Marketplace | Kortix