AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

entra-app-registration

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.

Original source
microsoft
License
MIT
Pinned revision
3f5b461b2314e01c400564051e92469114c5b68f

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read microsoft--entra-app-registration at revision 3f5b461b2314e01c400564051e92469114c5b68f, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 16

references/sdk/azure-identity-ts.md

Authentication — TypeScript SDK Quick Reference

Condensed from azure-identity-ts. Full patterns (sovereign clouds, device code flow, custom credentials, bearer token provider) in the azure-identity-ts plugin skill if installed.

Install

npm install @azure/identity

Quick Start

Auth: DefaultAzureCredential is for local development. See auth-best-practices.md for production patterns.

import { DefaultAzureCredential } from "@azure/identity";
const credential = new DefaultAzureCredential();

Best Practices

  • Use DefaultAzureCredential for local development only (CLI, PowerShell, VS Code). In production, use ManagedIdentityCredential — see auth-best-practices.md
  • Never hardcode credentials — use environment variables or managed identity
  • Prefer managed identity — no secrets to manage in production
  • Scope credentials appropriately — use user-assigned identity for multi-tenant scenarios
  • Handle token refresh — Azure SDK handles this automatically
  • Use ChainedTokenCredential for custom fallback scenarios