docs: Azure CLI commands for the Entra app registrations - #19
Merged
Conversation
Step 1f scripts the whole confidential-app setup (register, api:// audience URI, gateway.access scope, groups claim, service principal, client secret) via az + one Graph PATCH, with the env-var mapping and a lookup-based recipe for the optional Graph application permissions. Step 6 gains the public User-Connect app equivalent, resolving delegated permission ids by name instead of hardcoded GUIDs. Commands verified live against a real tenant while wiring mcp.defency.net (2026-07-25). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The Entra guide walked through the portal only. This adds the Azure CLI equivalents, verified live while wiring a real deployment:
az ad app createwith the/auth/callbackredirect, one GraphPATCHsettingapi://<client-id>, thegateway.accessscope and the groups claim, service principal, client secret (with a note to pipe it into platform config rather than echo it), plus env-var mapping and the optional Graph application permissions via id lookup.--is-fallback-public-client true(= "Allow public client flows"), delegated permission ids resolved by name (oauth2PermissionScopes[?value=='…']) instead of hardcoded GUIDs, admin consent.Docs-only.
🤖 Generated with Claude Code