Skip to content

Commit b1ae67b

Browse files
author
Grant Harris
committed
update agent instructions
1 parent 8a56791 commit b1ae67b

1 file changed

Lines changed: 3 additions & 2 deletions

File tree

docs/agent365-guided-setup/a365-setup-instructions.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -89,7 +89,7 @@ Once the user provides the ID, replace `<CLIENT_APP_ID>` in the command below an
8989
az ad app show --id <CLIENT_APP_ID> --query "{appId:appId, displayName:displayName, requiredResourceAccess:requiredResourceAccess}" -o json && az ad app permission list-grants --id <CLIENT_APP_ID> --query "[].{resourceDisplayName:resourceDisplayName, scope:scope}" -o table
9090
```
9191

92-
From the output of the command above, verify these 5 permissions appear with admin consent. If any are missing or consent is not granted, see "What to do if validation fails" below.
92+
From the output of the command above, verify these 6 permissions appear with admin consent. If any are missing or consent is not granted, see "What to do if validation fails" below.
9393

9494
Required **delegated** Microsoft Graph permissions (all must have **admin consent granted**):
9595

@@ -100,14 +100,15 @@ Required **delegated** Microsoft Graph permissions (all must have **admin consen
100100
| `Application.ReadWrite.All` | Create and manage Azure AD applications |
101101
| `DelegatedPermissionGrant.ReadWrite.All` | Grant delegated permissions |
102102
| `Directory.Read.All` | Read directory data |
103+
| `User.ReadWrite.All` | Create agent users, set usage location, and assign licenses |
103104

104105
If the app does not exist, permissions are missing, or admin consent has not been granted, see "What to do if validation fails" below.
105106

106107
**If validation fails** (app not found, permissions missing, or no admin consent):
107108

108109
1. STOP — do not proceed to run any `a365` CLI commands.
109110
2. Inform the user the custom client app registration is missing or incomplete.
110-
3. Direct the user to the official setup guide: register the app, configure as a Public client with redirect URI `http://localhost:8400`, add all five permissions above, and have a Global Admin grant admin consent.
111+
3. Direct the user to the official setup guide: register the app, configure as a Public client with redirect URI `http://localhost:8400`, add all six permissions above, and have a Global Admin grant admin consent.
111112
4. Wait for the user to confirm the app is properly configured, then re-run the same validation command above.
112113

113114
Save the `clientAppId` value — it will be used automatically in Step 3 (do NOT ask the user for it again).

0 commit comments

Comments
 (0)