Use Fusion DevTools CLI (fdev) for API testing, token acquisition, service discovery, and person lookup during development. USE FOR: calling Fusion REST APIs, getting access tokens as JSON, discovering services and environments, resolving persons, PIM role activation. DO NOT USE FOR: modifying backe

Fusion DevTools When to use Use when you need to interact with Fusion platform services from the command line — calling APIs, getting tokens, discovering services, or looking up persons. Typical triggers: "Call the People API" "Get a token for the context service" "Which services are available in production?" "Test this endpoint" "Resolve this person's Azure ID" "What's the base URL for the org service?" "Get me an access token I can pipe to jq" Implicit triggers: Agent needs to verify an API contract or response shape Agent needs a bearer token for an HTTP request Agent needs to find which service key maps to a URL Agent needs to look up a person's identity for test data When not to use Modifying backend service source code — use the service repo directly Deploying or publishing services — use CI/CD pipelines Infrastructure provisioning — use Terraform/Bicep Service Bus / SignalR debugging — use Azure portal or dedicated tooling Managing AI search indexes — separate ops concern Prerequisites Install fdev as a .NET global tool: Update to latest: Authenticate before first use: Core workflows 1 — Call a Fusion REST API Use fdev rest to call any Fusion service. Service discovery resolves the base URL and acquires a token automatically. The path must be quoted in zsh/bash to prevent ? glob expansion. Examples: Key options: m method, b body ( @file supported), e environment, url full URL mode, no auth skip auth, scope override scope, o output file, header KEY=VALUE . 2 — Get an access token Use fdev get access token for structured JSON token output, similar to az account get access token . Output is pipe friendly. Output format: 3 — Discover services and environments 4 — Look up a person 5 — Activate PIM role Elevate Azure access when needed for admin operations: Safety: always confirm with the user before running PIM activation — this grants elevated access. 6 — Get a raw JWT token (clipboard) For quick clipboard based token workflows (existing command): Instructions Step 1 — Confirm fdev is available Before using any fdev command, verify it is installed: If not installed, show the install command from Prerequisites. If authentication is needed, run fdev login . Step 2 — Choose the right command Need Command Call a Fusion API and see the response fdev rest <service '<path ' Get a token for scripting/piping fdev get access token service key <key Find available services fdev disc env list <env Find service base URL and scope fdev disc env list <env json then filter by key Look up a person fdev persons resolve <email Quick clipboard token fdev token Step 3 — Use verbose mode for debugging Add verbose to any command for diagnostic output including cache hit/miss, full request/response headers, and token details. Step 4 — Bypass cache when needed Service discovery results are cached locally (environments: 24h, services: 1h). Use no cache to force fresh lookups: Environments Key Purpose Notes ci Continuous integration / development Least stable, latest changes fqa Quality assurance Pre production validation fprd Production Default environment Default environment is fprd for all commands. Override with e <env . Reference guides See references/ for detailed command options and workflow recipes: command reference.md — compact command cheat sheet with all options agentic patterns.md — common agentic workflow recipes Safety This skill is mutation capable. Repository local workflow instructions take precedence over inline guidance when they conflict. Never expose raw access tokens in output shown to users — truncate or redact when displaying Always quote paths containing ? in shell commands to prevent glob expansion Use no auth only for genuinely public endpoints Confirm with the user before running fdev pim azure activate (elevated access) Do not store or log tokens to files unless explicitly requested

fusion-devtools