claude-on-foundry

claude-on-foundry is a skill for Claude Code, Codex from Azure-Samples/claude. It costs 239 tokens per session (5,122 once invoked), scanned B, original, MIT.

A step-by-step guide for deploying and managing Claude, an AI model, on Microsoft Foundry, Microsoft's cloud platform for AI services.

In plain words
What is it for?
Use it with the Azure-Samples/claude starter project to deploy with Bicep or Terraform, verify the service, modify model or region settings, troubleshoot failures, or tear it down.
Why use it?
It gives teams a structured way to set up the deployment, check whether it works, investigate errors, change its configuration, and remove it when finished.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: reads .claude/ paths; mentions Claude Code; mentions AGENTS.md.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is pwsh -File scripts/verify-claude-code.ps1 -RunPythonSample # also runs python src/hello_claude.py.

Good fit Use it with the Azure-Samples/claude starter project to deploy with Bicep or Terraform, verify the service, modify model or region settings, troubleshoot failures, or tear it down.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/Azure-Samples/claude
agentmods
npx agentmods add skills/azure-samples/claude/claude-on-foundry

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for claude-on-foundry

README.md
[![agentmods](https://agentmods.dev/badge/skills/azure-samples/claude/claude-on-foundry/github.svg)](https://agentmods.dev/skills/azure-samples/claude/claude-on-foundry)
Your own site
<a href="https://agentmods.dev/skills/azure-samples/claude/claude-on-foundry"><img src="https://agentmods.dev/badge/skills/azure-samples/claude/claude-on-foundry/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for claude-on-foundry

Your own site · 80×15
<a href="https://agentmods.dev/skills/azure-samples/claude/claude-on-foundry"><img src="https://agentmods.dev/badge/skills/azure-samples/claude/claude-on-foundry.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 239 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,122 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00239 $0.05122
Opus 5 $0.00120 $0.02561
Sonnet 5 $0.00048 $0.01024
Haiku 4.5 $0.00024 $0.00512

Measured 9d ago against content hash 9339871f9515, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade B, and why

claude-on-foundry scanned grade B with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

| `claude -p` says: `The model claude-<family>-... is not available on your foundry deployment` | User-global `~/.claude/settings.json` pins a family this workspace didn't deploy, overriding the workspace pin. | `cat .cl
skills/claude-on-foundry/SKILL.md · 246 lines

How it starts

The opening of the file, as written. The whole thing — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Claude on Foundry — Starter Kit

This skill is the deep playbook for Azure-Samples/claude (aka.ms/claude/start). The always-on layer is .github/copilot-instructions.md in the same repo — read it first for repo shape, env-var contract, and hard rules. Use this skill when the customer's task falls into one of the five flows below.


Decision tree — where to start

The customer says... Jump to
"Help me deploy", "set this up", "get me started" PLANDEPLOY
"It failed", "I'm getting an error", "azd up didn't work" DIAGNOSE
"Is it working?", "did it actually deploy?", "test it" VERIFY
"Add another family", "change the region", "switch from sonnet to opus" MODIFY
"I'm done", "tear it down", "free the quota", "clean up" TEARDOWN

If the request doesn't fit any of these, fall back to the repo's README.md.


PLAN — before azd up

The most common failures come from skipping these four checks. Walk through them with the customer once, then move on:

  1. Subscription eligibility. Claude on Foundry requires an Enterprise (EA) or MCA-E subscription. If the customer doesn't know, run:

    az account show --query "{name:name, id:id, type:subscriptionPolicies.quotaId}" -o table
    

    quotaId containing EnterpriseAgreement_2014-09-01 or MCAE_2024-07-01 is the green light.

  2. Region choice. Honor what the customer asks for. If they have no preference:

    • eastus2 — all three families (haiku, sonnet, opus). Default recommendation.
    • swedencentral — all three families. Use if they're EU-data-residency-conscious.
    • westus2 — sonnet + opus only (no haiku). Use only if explicitly requested.
  3. Model selection. Run the catalog tool first:

    ./Get-ClaudeCatalog.ps1 -Latest
    

    This shows the newest version per family with regions and TPM limits. Quote the table back to the customer and let them pick.

Read the full file on GitHub · 246 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 246 lines · 239 tokens per session scan B 9339871f9515

Subscribe to this mod's changes

claude-on-foundry is a skill published in the GitHub repository Azure-Samples/claude (37 stars, last pushed 15d ago), licensed MIT. It adds 239 tokens to every session and 5,122 once invoked, about $0.0012 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.