AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides a structured approach to configuring Microsoft Entra ID (formerly Azure AD) for secure application authentication. It covers the end-to-end lifecycle of app registration, including setting up OAuth 2.0 flows, configuring API permissions, and implementing authentication in code using the Microsoft Authentication Library (MSAL). It emphasizes secure practices, such as using managed identities and avoiding hardcoded secrets, while providing references for CLI-based automation and Infrastructure-as-Code (IaC) templates.
What it does
- Guides the creation and configuration of Microsoft Entra ID app registrations.
- Explains how to implement OAuth 2.0 authentication flows for various application types.
- Details the configuration of API permissions for Microsoft Graph and custom APIs.
- Provides best practices for secure credential management, including certificates and managed identities.
- Offers CLI commands and code-based examples for MSAL integration.
- Outlines patterns for service-to-service and user-interactive authentication.
When to use it
- When you need to register a new application in Microsoft Entra ID.
- When setting up authentication for web, mobile, or daemon applications.
- When you need to grant your application access to Microsoft Graph or other protected APIs.
- When implementing secure service-to-service communication using client credentials.
- When migrating from legacy authentication methods to modern OAuth 2.0 flows.
Advantages
- Centralizes configuration steps for Entra ID app registrations.
- Promotes security best practices like least privilege and secret rotation.
- Supports both manual portal configuration and automated CLI/IaC workflows.
- Provides clear guidance on choosing the right authentication library and flow.
Usage examples
- “How do I register a new web application in Microsoft Entra ID?”
- The agent provides a step-by-step guide for the Azure Portal or CLI, including setting redirect URIs and account types.
- “What are the steps to add Microsoft Graph permissions to my app?”
- The agent explains how to navigate to API permissions in the portal and select the appropriate delegated or application permissions.
- “How do I implement a client credentials flow for a background service?”
- The agent outlines the process of creating a client secret or certificate and using the MSAL library to authenticate the service.
- “What is the best way to handle authentication in production?”
- The agent recommends using managed identities or client certificates instead of secrets, with code examples for different environments.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/microsoft/entra-app-registration/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip entra-app-registration.zip -d .agents/skills
Documentation by Microsoft
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:
Navigate to Azure Portal → Microsoft Entra ID → App registrations
Click "New registration"
Provide name, supported account types, and redirect URI
Click "Register"
CLI Method: See references/cli-commands.md IaC Method: See 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://localhostor custom URI schemeServices: 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 profileUser.ReadWrite.All- Read and write all usersDirectory.Read.All- Read directory dataMail.Send- Send mail as a user
Details: See 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 - OAuth 2.0 flow details
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
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
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)
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
Microsoft Authentication Library (MSAL)
MSAL is the recommended library for integrating Microsoft identity platform.
Supported Languages:
.NET/C# -
Microsoft.Identity.ClientJavaScript/TypeScript -
@azure/msal-browser,@azure/msal-nodePython -
msal
Examples: See 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 | .NET | TypeScript | Java | Rust
Key Vault (secrets): Python | TypeScript
Auth Events: .NET
References
OAuth Flows - Detailed OAuth 2.0 flow explanations
CLI Commands - Azure CLI reference for app registrations
Console App Example - Complete working examples
First App Registration - Step-by-step guide for beginners
API Permissions - Understanding and configuring permissions
Troubleshooting - Common issues and solutions
External Resources
Files
- ATTRIBUTION.mdAdded by AutoGineer998 B
- LICENSELicence file added by AutoGineer1.1 KiB
- SKILL.md8.0 KiB
- references/BICEP-EXAMPLE.bicep5.2 KiB
- references/api-permissions.md10.0 KiB
- references/auth-best-practices.md6.1 KiB
- references/cli-commands.md8.6 KiB
- references/console-app-example.md10.7 KiB
- references/first-app-registration.md7.2 KiB
- references/oauth-flows.md9.3 KiB
- references/sdk/azure-identity-dotnet.md940 B
- references/sdk/azure-identity-java.md1.2 KiB
- references/sdk/azure-identity-py.md1.1 KiB
- references/sdk/azure-identity-rust.md805 B
- references/sdk/azure-identity-ts.md1.1 KiB
- references/sdk/azure-keyvault-py.md1.1 KiB
- references/sdk/azure-keyvault-secrets-ts.md1.0 KiB
- references/sdk/microsoft-azure-webjobs-extensions-authentication-events-dotnet.md1.5 KiB
- references/troubleshooting.md7.4 KiB
references/cli-commands.md
Azure CLI Commands for App Registration
This document provides a comprehensive reference for managing Microsoft Entra app registrations using Azure CLI.
Prerequisites
# Ensure Azure CLI is installed
az version
# Login to Azure
az login
# Set default subscription (optional)
az account set --subscription "Your Subscription Name"App Registration Management
Create App Registration
Basic app registration:
az ad app create --display-name "MyApplication"Web application with redirect URI:
az ad app create \
--display-name "MyWebApp" \
--web-redirect-uris "https://myapp.com/callback" \
--sign-in-audience "AzureADMyOrg"Single Page Application (SPA):
az ad app create \
--display-name "MySpaApp" \
--spa-redirect-uris "http://localhost:3000" \
--sign-in-audience "AzureADMyOrg"Public client (Desktop/Mobile app):
az ad app create \
--display-name "MyDesktopApp" \
--public-client-redirect-uris "http://localhost" \
--sign-in-audience "AzureADMyOrg"Multi-tenant application:
az ad app create \
--display-name "MyMultiTenantApp" \
--web-redirect-uris "https://myapp.com/callback" \
--sign-in-audience "AzureADMultipleOrgs"Sign-in Audience Options
| Value | Description |
|---|---|
AzureADMyOrg | Single tenant (default) |
AzureADMultipleOrgs | Multi-tenant (any Azure AD) |
AzureADandPersonalMicrosoftAccount | Multi-tenant + personal Microsoft accounts |
PersonalMicrosoftAccount | Personal Microsoft accounts only |
List and Query Apps
List all app registrations
az ad app list --output tableList apps with custom query
# Filter by display name
az ad app list --display-name "MyApp" --output table
# Get specific fields
az ad app list --query "[].{Name:displayName, AppId:appId}" --output tableGet app details
# By display name
az ad app show --id $(az ad app list --display-name "MyApp" --query "[0].appId" -o tsv)
# By application ID
az ad app show --id "YOUR_APPLICATION_ID"Get Application (Client) ID
APP_ID=$(az ad app list --display-name "MyApp" --query "[0].appId" -o tsv)
echo "Application ID: $APP_ID"Get Object ID
OBJECT_ID=$(az ad app list --display-name "MyApp" --query "[0].id" -o tsv)
echo "Object ID: $OBJECT_ID"Update App Registration
Add redirect URIs
Web app:
az ad app update --id $APP_ID \
--web-redirect-uris "https://myapp.com/callback" "https://myapp.com/auth"SPA:
az ad app update --id $APP_ID \
--spa-redirect-uris "http://localhost:3000" "http://localhost:5000"Public client:
az ad app update --id $APP_ID \
--public-client-redirect-uris "http://localhost" "myapp://auth"Client Credentials (Secrets & Certificates)
Create client secret
# Create secret with default expiration
az ad app credential reset --id $APP_ID
# Create secret with custom expiration
az ad app credential reset --id $APP_ID --years 1
# Create secret with specific end date
az ad app credential reset --id $APP_ID --end-date "2025-12-31"Save the output:
{
"appId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
"password": "your-secret-value-SAVE-THIS",
"tenant": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
}⚠️ Important: Resetting Client credential will delete all existing credentials. ⚠️ Important: The secret value is only shown once. Store it securely (e.g., Azure Key Vault).
List client credentials
# List all credentials (secrets and certificates)
az ad app credential list --id $APP_IDDelete client secret
# Get key ID from credential list
az ad app credential list --id $APP_ID --query "[].{KeyId:keyId, Type:type}" -o table
# Delete specific credential
az ad app credential delete --id $APP_ID --key-id "KEY_ID_HERE"Upload certificate
# Upload certificate from file
az ad app credential reset --id $APP_ID --cert "@path/to/cert.pem"API Permissions
Add API permissions
Microsoft Graph User.Read:
GRAPH_RESOURCE_ID="00000003-0000-0000-c000-000000000000" # Microsoft Graph
USER_READ_ID="e1fe6dd8-ba31-4d61-89e7-88639da4683d" # User.Read permission
az ad app permission add --id $APP_ID \
--api $GRAPH_RESOURCE_ID \
--api-permissions "$USER_READ_ID=Scope"Microsoft Graph Mail.Read (delegated):
MAIL_READ_ID="570282fd-fa5c-430d-a7fd-fc8dc98a9dca" # Mail.Read permission
az ad app permission add --id $APP_ID \
--api $GRAPH_RESOURCE_ID \
--api-permissions "$MAIL_READ_ID=Scope"Microsoft Graph User.Read.All (application):
USER_READ_ALL_ID="df021288-bdef-4463-88db-98f22de89214" # User.Read.All application permission
az ad app permission add --id $APP_ID \
--api $GRAPH_RESOURCE_ID \
--api-permissions "$USER_READ_ALL_ID=Role"Note: Use Scope for delegated permissions, Role for application permissions.
Common Permission IDs
Microsoft Graph (00000003-0000-0000-c000-000000000000):
| Permission | ID | Type |
|---|---|---|
| User.Read | e1fe6dd8-ba31-4d61-89e7-88639da4683d | Delegated |
| User.ReadWrite | b4e74841-8e56-480b-be8b-910348b18b4c | Delegated |
| Mail.Read | 570282fd-fa5c-430d-a7fd-fc8dc98a9dca | Delegated |
| Mail.Send | e383f46e-2787-4529-855e-0e479a3ffac0 | Delegated |
| Calendars.Read | 465a38f9-76ea-45b9-9f34-9e8b0d4b0b42 | Delegated |
| User.Read.All | df021288-bdef-4463-88db-98f22de89214 | Application |
| Directory.Read.All | 7ab1d382-f21e-4acd-a863-ba3e13f7da61 | Application |
Grant admin consent
# Grant admin consent for all permissions
az ad app permission admin-consent --id $APP_IDNote: Admin consent is required for application permissions and some delegated permissions.
List permissions
az ad app permission list --id $APP_IDDelete permission
# Remove specific permission
az ad app permission delete --id $APP_ID \
--api $GRAPH_RESOURCE_ID \
--permission-id $USER_READ_IDService Principal Management
Create service principal
# Create service principal for the app
az ad sp create --id $APP_IDList service principals
az ad sp list --display-name "MyApp"Get service principal details
az ad sp show --id $APP_IDDelete service principal
az ad sp delete --id $APP_IDApp Roles and Claims
Get app roles
az ad app show --id $APP_ID --query "appRoles"Get optional claims
az ad app show --id $APP_ID --query "optionalClaims"Owners
List app owners
az ad app owner list --id $APP_IDAdd owner
# Add user as owner
USER_OBJECT_ID=$(az ad user show --id "[email protected]" --query "id" -o tsv)
az ad app owner add --id $APP_ID --owner-object-id $USER_OBJECT_IDRemove owner
az ad app owner remove --id $APP_ID --owner-object-id $USER_OBJECT_IDDelete App Registration
# Delete app registration (and associated service principal)
az ad app delete --id $APP_IDTenant and Identity Information
Get tenant ID
az account show --query tenantId -o tsvGet current user information
az ad signed-in-user showGet user by email
az ad user show --id "[email protected]"Get user object ID
az ad user show --id "[email protected]" --query "id" -o tsvList all users
az ad user list --output tableScripting Examples
Complete app setup script
#!/bin/bash
# Variables
APP_NAME="MyApplication"
REDIRECT_URI="http://localhost:3000"
echo "Creating app registration..."
APP_ID=$(az ad app create \
--display-name "$APP_NAME" \
--spa-redirect-uris "$REDIRECT_URI" \
--query "appId" -o tsv)
echo "App created with ID: $APP_ID"
echo "Adding Microsoft Graph permissions..."
GRAPH_RESOURCE_ID="00000003-0000-0000-c000-000000000000"
USER_READ_ID="e1fe6dd8-ba31-4d61-89e7-88639da4683d"
az ad app permission add --id $APP_ID \
--api $GRAPH_RESOURCE_ID \
--api-permissions "$USER_READ_ID=Scope"
echo "Granting admin consent..."
az ad app permission admin-consent --id $APP_ID
echo "Creating service principal..."
az ad sp create --id $APP_ID
TENANT_ID=$(az account show --query tenantId -o tsv)
echo ""
echo "App registration complete!"
echo "Application (Client) ID: $APP_ID"
echo "Tenant ID: $TENANT_ID"
echo "Redirect URI: $REDIRECT_URI"Cleanup script
#!/bin/bash
# Delete all apps matching pattern
az ad app list --display-name "Test*" --query "[].appId" -o tsv | while read APP_ID; do
echo "Deleting app: $APP_ID"
az ad app delete --id $APP_ID
doneRequirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs Node.js
Security
What our scanner noticed· Low risk
- Instructions that use the network
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- Microsoft
- Publisher
- Microsoft (Official)
- Source
- microsoft/skills · .github/plugins/azure-skills/skills/entra-app-registration · commit 0696600
- Licence
- MIT License (redistribution allowed)
- LICENSE (added by AutoGineer from .github/plugins/azure-skills/LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
- Also distributed in
- microsoft/azure-skills
AutoGineer is not affiliated with or endorsed by Microsoft.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download entra-app-registration.zip