Skip to main content
command CX Codex official · Anthropic

update-user-attrs — Claude Code command: setup and install

The update-user-attrs Claude Code command sets per-user configuration through Microsoft Entra ID extension attributes. It updates one user or processes a CSV file.

Apache-2.0 ★ 41,441 updated 2026-09-21

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add anthropics/financial-services
/plugin install claude-for-msft-365-install@claude-for-financial-services
Open on GitHub

What update-user-attrs does

The command writes per-user settings to Microsoft Entra ID extension attributes through Microsoft Graph. Supported keys include gateway_token, gateway_url, gcp_project_id, gcp_region, aws_role_arn, and aws_region; each value has a 256-character limit. Only the eight keys registered on Anthropic’s app work this way.

For a single user, it calls az rest with a PATCH request. Bulk updates use CSV with Bash on macOS/Linux or PowerShell on Windows. A single-user secret is exposed in shell history and the chat transcript, so the documented CSV route avoids entering values in chat. Azure CLI, an az login session, and Microsoft Graph permission User.ReadWrite.All are required.

The manifest needs entra_sso=1; otherwise, the add-in does not acquire an Entra token to read the attributes. Token claim caching can delay updated values by up to an hour. Fully quitting and reopening the Office app requests a fresh token.

What it helps with

  • set a user’s GCP region or project ID
  • route teams to separate gateways or Bedrock roles
  • apply user attributes from a CSV file
  • check an attribute value through Microsoft Graph

Example prompts for the agent

  • Set europe-west4 as the region for [email protected] with update-user-attrs.
  • Update gateway_token for the users in users.csv without putting secrets in chat.
  • Check the gcp_project_id attribute for [email protected].

How to install update-user-attrs

1Plugin marketplace

/plugin marketplace add anthropics/financial-services
/plugin install claude-for-msft-365-install@claude-for-financial-services

2Manually: put the files in place

.claude/commands/update-user-attrs.md

Call it with /update-user-attrs. For all projects use ~/.claude/commands/

Questions about update-user-attrs

How do I install update-user-attrs in Claude Code?

Run /plugin marketplace add anthropics/financial-services, then /plugin install claude-for-msft-365-install@claude-for-financial-services. The command is also available at .claude/commands/update-user-attrs.md.

What does update-user-attrs do?

It sets per-user Microsoft Entra ID configuration through extension attributes and Microsoft Graph. It can update one user or process a CSV file.

What does update-user-attrs need to run?

It needs Azure CLI with an active az login session, Microsoft Graph permission User.ReadWrite.All, and entra_sso=1 in the manifest. Bulk updates also need a CSV file and Bash on macOS/Linux or PowerShell on Windows.

Source text

update-user-attrs.md · Apache-2.0
---
description: Set per-user config (tokens, region overrides) via Azure AD extension attributes
---

# Per-user config via extension attributes

The eight attributes below are already registered on Anthropic's app
(`c2995f31-…`) — you don't create schema, you just write values. You write
`extension_c2995f3111e74882b7a7ef9def0a0266_<key>` on the user with Graph; the
add-in reads it back as the `extn.<key>` claim in the user's ID token.

**Requires `entra_sso=1` in the manifest.** Without it the add-in never
acquires an Entra token, so these attributes are never read — they silently do
nothing.

**Only these eight keys work this way on Anthropic's app** — it issues `extn.*`
claims for no other attribute, so a value under any other attribute name never
reaches the add-in. Attrs override manifest params, and a [bootstrap](bootstrap.md)
response overrides both. All values are 256 chars max.

| Key | Per-user use case |
|---|---|
| `gateway_token` | Per-user API key (rotation) |
| `gateway_url` | Route different teams to different gateways |
| `gcp_project_id` | Different teams on different GCP projects |
| `gcp_region` | Data-residency override |
| `google_client_id` `google_client_secret` | Different OAuth client per team (uncommon) |
| `aws_role_arn` `aws_region` | Different Bedrock roles by team |

On Anthropic's app, anything else that varies per user — `azure_api_key`,
`disabled_features`, `available_models`, `inference_headers`,
`gateway_api_format`, the `otlp_*` telemetry keys — goes in a
[bootstrap endpoint](bootstrap.md) response, and `bootstrap_url` itself goes in
the manifest, one value for everyone; the endpoint tells users apart by the
Entra token it validates.

**Bring-your-own Entra app (`graph_client_id`):** the token comes from *your*
app, so the `extension_c2995f31…_<key>` attributes do nothing there. Either use
a bootstrap endpoint, or, for each key you need, register a directory extension
on your app named exactly as the config key, add it as an ID-token optional
claim (it reaches the add-in as `extn.<key>`), and swap your app's ID (no
hyphens) into the `extension_…_<key>` commands below. Any config key works this
way except `entra_sso`, `graph_client_id`, `graph_cloud`, `entra_scope`,
`gateway_auth_source` and `allow_1p`, which the add-in reads from the manifest
only. The 256-character limit still applies, so a longer value, such as most
`access_policies` arrays, goes in the manifest or a bootstrap response.

## One user

Substitute `<key>` with the attribute name from the table. For non-secret keys
(regions, project IDs) this is the normal path. For secrets (`gateway_token`,
`google_client_secret`) the value lands in shell history and this conversation's
transcript — use the bulk CSV path below if that's a problem.

```bash
az rest --method PATCH \
  --uri "https://graph.microsoft.com/v1.0/users/<upn>" \
  --body '{"extension_c2995f3111e74882b7a7ef9def0a0266_<key>":"<value>"}'
```

Success is silent — PATCH returns 204 with an empty body. To verify:

```bash
az rest --method GET --uri "https://graph.microsoft.com/v1.0/users/<upn>?\$select=extension_c2995f3111e74882b7a7ef9def0a0266_<key>"
```

Graph reads are immediately consistent with the write — no lag. To dump every
extension attr on a user (without knowing exact key names), use `/beta/`:

```bash
az rest --method GET --uri "https://graph.microsoft.com/beta/users/<upn>" | jq 'to_entries | map(select(.key | startswith("extension"))) | from_entries'
```

## Bulk (CSV, values never enter this chat)

Have the admin prepare `users.csv`. First column is UPN; remaining column
headers are the attribute keys. Empty cells skip that attr for that user.

```
upn,gateway_token,gcp_region
[email protected],sk-live-aaa,
[email protected],sk-live-bbb,europe-west4
[email protected],,europe-west4
```

**macOS/Linux** — write this to `apply.sh` next to their CSV (the `read -a` array syntax is
bash-only; a bare paste into zsh breaks). They review it, then run
`bash apply.sh`. You only see ✓/✗ — don't `cat` either file.

```bash
#!/bin/bash
EXT=extension_c2995f3111e74882b7a7ef9def0a0266_
{
  IFS=, read -ra keys
  while IFS=, read -ra vals; do
    upn="${vals[0]}"
    for i in "${!keys[@]}"; do
      [ "$i" -eq 0 ] || [ -z "${vals[$i]}" ] && continue
      az rest --method PATCH --uri "https://graph.microsoft.com/v1.0/users/$upn" \
        --body "{\"${EXT}${keys[$i]}\":\"${vals[$i]}\"}" \
        && echo "✓ $upn ${keys[$i]}" || echo "✗ $upn ${keys[$i]}"
    done
  done
} < users.csv
```

**Windows** — write this to `apply.ps1` next to their CSV. `Import-Csv` reads
the header as the schema directly; they run `.\apply.ps1` in PowerShell.

```powershell
$EXT = 'extension_c2995f3111e74882b7a7ef9def0a0266_'
Import-Csv users.csv | ForEach-Object {
  $upn = $_.upn
  $_.PSObject.Properties | Where-Object { $_.Name -ne 'upn' -and $_.Value } | ForEach-Object {
    $body = @{ "$EXT$($_.Name)" = $_.Value } | ConvertTo-Json -Compress
    az rest --method PATCH --uri "https://graph.microsoft.com/v1.0/users/$upn" --body $body
    if ($?) { "OK $upn $($_.Name)" } else { "FAIL $upn $($_.Name)" }
  }
}
```

Report the ✓ and ✗ counts. 404 means the UPN is wrong; 403
means `az login` lacks `User.ReadWrite.All` — they need to re-consent or use
an admin account.

## Propagation delay

Graph writes succeed immediately, but the add-in reads these via the user's
ID token at NAA sign-in — and Azure's STS caches token claims. Expect **up to
an hour** before the new value appears for a given user. If they open the
add-in right after the PATCH and it behaves as if unconfigured, that's the
cache, not a failure. Tell them to wait and retry; quitting the Office app
fully (not just closing the taskpane) forces a fresh NAA token on next launch.

© Anthropic · Apache-2.0 · anthropics/financial-services

Similar slash commands

All slash commands for Cloud: AWS, Azure, GCP →

From the same set116

The whole set →
market-researcher The market-researcher Claude Code subagent researches an industry or investment theme, covering competitors, peer multiples and a shortlist of ideas. It runs on requests for a sector or thematic primer, not updates on a single company. CX Codex ★ 41,441repo stars kyc-screener kyc-screener — a subagent for Claude Code, Codex, and Cursor that automates client onboarding document analysis. It runs KYC/AML rule checks, screens against sanctions and PEP lists, and flags gaps for compliance review. CX Codex ★ 41,441repo stars gl-reconciler gl-reconciler — a subagent for Claude Code matches the general ledger against subledgers for a trade date. It runs daily or at month-end, then prepares exceptions for sign-off. CX Codex ★ 41,441repo stars earnings-reviewer earnings-reviewer — a subagent for Claude Code automating end-to-end earnings event processing. It analyzes call transcripts and filings to update financial models and draft post-earnings notes. CX Codex ★ 41,441repo stars setup A setup command for Claude Code that guides administrators through connecting the Claude Office add-in to their cloud infrastructure. CX Codex +1 ★ 41,441repo stars manifest This Claude Code command builds an add-in XML manifest with cloud settings. Outlook uses a separate template and needs Microsoft Graph admin consent before deployment. CX Codex +1 ★ 41,441repo stars export-data The export-data command for Claude Code copies chat history, skills, and settings before a machine is rebuilt. CX Codex +1 ★ 41,441repo stars entra-app This Claude Code command explains how to register a Microsoft Entra app in your own tenant. It covers sign-in setup for Outlook, gateways, Foundry, and sovereign clouds. CX Codex +1 ★ 41,441repo stars

Project sponsors

Companies that keep this analytics open