Skip to main content
Agent skill

Azure

Inspect or change Microsoft Azure resources from the sandbox via the Azure Resource Manager (ARM) REST API or the az CLI. Includes a script to load a short-lived ARM access token for an Nuphos-bound Azure subscription.

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Azure when an AI agent needs a reusable SKILL.md workflow for this job: Inspect or change Microsoft Azure resources from the sandbox via the Azure Resource Manager (ARM) REST API or the az CLI. Includes a script to load a short-lived ARM access token for an Nuphos-bound Azure subscription.

When not to use it

Skip Azure when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/azure
# Save SKILL.md to ~/.claude/skills/azure/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/azure/SKILL.md. For a shared project, commit the folder at .claude/skills/azure/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Azure skill for this task: Use Azure when this documented workflow matches the task. Confirm any required inputs or files before making changes.

What supports this recommendation?

70/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
77/100
Practical detail
68/100
Source evidence
63/100
Source signals
70/100
Model compatibility evidence
  • claudeuntested

    No model-specific signal or recorded compatibility test was found.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# Microsoft Azure (ARM)

## Session isolation

Keep CLI credentials and settings inside the current session's `HOME` (`NUPHOS_SESSION_HOME`) and respect the supplied CLI config environment variables. Do not copy another session's or the runtime owner's credentials. Without `NUPHOS_SESSION_HOME`, CLI defaults may use shared runtime configuration; be aware of the affected scope.

Changing runtime-global settings is possible, but strongly discouraged unless the user understands the impact on other sessions and explicitly requests it. Explain the shared scope first; do not unset session isolation variables, write to the runtime owner's home, use a shared OS credential store, or modify shared shell startup files as routine setup. This is configuration isolation, not an OS security boundary.

Use this skill when the user wants to inspect or change Azure resources. Authenticate before any ARM/`az` call with the short-lived token Nuphos mints for a bound subscription.

## When to skip this skill

For anything Nuphos already exposes via its own API — listing AKS clusters, fetching kubeconfigs — call the Nuphos backend route directly instead of hitting ARM yourself. Same data, no setup, smaller blast radius:

- List AKS clusters in a bound subscription → `GET /teams/:teamId/azure-accounts/:accountId/clusters` - Run kubectl against an AKS cluster → its context is `azure/<account>/<cluster>` in the kubeconfig the kubectl skill sets up. Entra-ID (AAD) integrated clusters are the one exception — they need `kubelogin`, which the sandbox doesn't ship, so they are not included.

Use this skill when the user asks for something Nuphos does not expose (e.g. resource groups, storage accounts, VMs, networking, role assignments).

## Setup

```bash # Load a short-lived ARM access token for an Nuphos-bound subscription, then # source it so $AZURE_ACCESS_TOKEN + $AZURE_SUBSCRIPTION_ID are available. # The token expires (workload-identity federation) — re-run to refresh. source <(bash skills/azure/scripts/setup-credentials.sh <teamId> <accountId>) ```

Nuphos uses OIDC workload identity federation here (like AWS/Tencent): the customer creates an Entra ID app registration with a federated credential trusting the Nuphos issuer and grants it an RBAC role on a subscription. Nuphos exchanges a per-team token for a short-lived ARM access token — no client secret is stored. `setup-credentials.sh` calls `GET /teams/:teamId/azure-accounts/:accountId/credentials` on the Nuphos backend with the user's `NUPHOS_TOKEN` and prints `export` lines for the token + subscription id. The token carries exactly the app's RBAC permissions and expires (~1h), so re-run to refresh.

## Calling ARM

The token is a standard `management.azure.com` bearer. The sandbox runtime pre-installs `az`; prefer `az rest` for ARM requests and use raw `curl` when you need exact control over headers or response handling:

```bash # Which subscription/tenant is this token for? curl -sS -H @<(printf 'Authorization: Bearer %s\n' "$AZURE_ACCESS_TOKEN") \ "https://management.azure.com/subscriptions/$AZURE_SUBSCRIPTION_ID?api-version=2022-12-01"

# List resource groups curl -sS -H @<(printf 'Authorization: Bearer %s\n' "$AZURE_ACCESS_TOKEN") \ "https://management.azure.com/subscriptions/$AZURE_SUBSCRIPTION_ID/resourcegroups?api-version=2021-04-01"

# List AKS clusters (prefer the Nuphos route above unless you need raw ARM) curl -sS -H @<(printf 'Authorization: Bearer %s\n' "$AZURE_ACCESS_TOKEN") \ "https://management.azure.com/subscriptions/$AZURE_SUBSCRIPTION_ID/providers/Microsoft.ContainerService/managedClusters?api-version=2024-05-01" ```

```bash az rest --method get \ --url "https://management.azure.com/subscriptions/$AZURE_SUBSCRIPTION_ID/resourcegroups?api-version=2021-04-01" \ --headers "Authorization=Bearer $AZURE_ACCESS_TOKEN" ```

Always confirm which subscription you are about to operate on, and tell the user before doing anything mutating.

## When you hit HTTP 401 / 403

If `setup-credentials.sh` returns HTTP 403, the current member account does not have access to that Azure binding (or it wasn't shared with them). Do not try to request access from inside the sandbox. Ask the user or a team admin to add the member account to the binding's Access allow list.

If an ARM call returns `AuthorizationFailed`, the app's RBAC role is missing a permission — report exactly which action/scope failed so the user can widen the role assignment. Do not attempt to escalate from inside the sandbox.

Intended uses

  • Use Azure when this documented workflow matches the task.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.