Agent Wealth HubFree public resources
中文 EN العربية

Back to catalog / Security

Entra app registration: configure OAuth and least privilege by app type

Define redirects, audience, API scopes, and credential lifecycle when establishing app identity.

Skills

Confirm whether the app is web, SPA, native/mobile, or daemon and select supported account types; verify redirect URI and OAuth flow. Create registration through portal, CLI, or IaC, requesting only necessary API scopes. Explain each permission’s read/write scope and whether admin consent is required. Before creating a service principal or granting access, present tenant, app ID, scopes, and impact and obtain approval. For confidential clients, prefer certificates or federated identity in production; store any secret only in a secure manager such as Key Vault, never repository/log/chat. Test sign-in, token audience, and permission-denial paths before deployment.

Permissions

Prerequisites

Permissions

Limitations

Verify app type and least API scopes. Do not grant privileged access without confirmation. Prefer certificates/federation in production; store secrets only in Key Vault.

Pinned upstream source

https://github.com/microsoft/skills/blob/fc164ba1d7a0c10377dbcc1c9ac07253b9329fdb/.github/plugins/azure-skills/skills/entra-app-registration/SKILL.md

Repository
microsoft/skills
File path
.github/plugins/azure-skills/skills/entra-app-registration/SKILL.md
Pinned commit
fc164ba1d7a0c10377dbcc1c9ac07253b9329fdb
Source checked
2026-10-14 · Reviewed against the pinned upstream source

Repository metrics

These values describe the upstream repository, not popularity or likes for an individual skill or playbook.

Stars
Not collected
Forks
Not collected
Observed at
Not collected

No metrics snapshot is available yet.

License: MIT

Compatible tools

Entra App registrations · Azure CLI · MSAL client libraries

View skill directory

Main topic

Make Agent behavior safer and easier to verify

Related resources