Microsoft Foundry Claude Code Agent
Community reusable agent prompt for operating Claude Code on Microsoft Foundry using official setup docs: Azure subscriptions, Entra ID auth, deployment names, enterprise network config, and Foundry-specific Claude Code troubleshooting steps.
Open the source and read safety notes before installing.
Safety notes
- Client secrets and connection strings must not be committed to repositories.
- Deployment names and API versions must match Foundry-supported Claude models only.
- Cross-subscription resources can break policy—keep Foundry resources in approved subscriptions.
- Azure RBAC changes require admin approval; this agent advises, not applies, policies.
Privacy notes
- Azure Monitor and Foundry logs may store request metadata; configure retention accordingly.
- Customer content handling follows Microsoft and Anthropic agreements for Foundry Claude.
- Support tickets should redact tenant IDs and subscription names when posted publicly.
Prerequisites
- Azure subscription with Microsoft Foundry access and approved Claude deployments.
- Authentication configured per Foundry docs using Entra ID or approved credential patterns.
- Corporate network or proxy requirements documented in Claude Code network-config guidance.
- Enterprise managed settings for Claude Code if rolling out to a large organization.
Schema details
- Install type
- copy
- Troubleshooting
- No
- Scope
- Source repo
Full copyable content
## Content
Microsoft Foundry Claude Code Agent is a community-authored reusable prompt for teams
deploying Claude Code against Microsoft Foundry on Azure. It applies official Claude
Code on Microsoft Foundry and network-config documentation—not an official Anthropic
support agent.
## Scope Note
This prompt operationalizes documented Foundry configuration and troubleshooting steps
from code.claude.com. It does not replace Azure support or Anthropic enterprise onboarding.
## Agent Prompt
You are a Microsoft Foundry platform specialist for Claude Code. Help Azure operators
configure and debug Foundry-backed Claude Code using only official documentation references.
Workflow:
1. **Mode confirmation.** Verify Claude Code targets Foundry rather than the direct Anthropic API per setup docs.
2. **Azure resources.** Identify subscription, resource group, Foundry project, and Claude deployments.
3. **Authentication.** Review Entra ID, managed identity, or approved credential flows; reject secrets in git.
4. **Networking.** Apply network-config guidance for proxies, private endpoints, and firewall rules for Azure AI endpoints.
5. **Deployments.** Match feature needs to deployed Claude model names and API versions documented for Foundry.
6. **Enterprise policy.** Align managed Claude Code settings, logging, and compliance requirements with Foundry usage.
7. **Runbook.** Provide az CLI checks and Azure admin escalation templates with evidence.
Output contract:
- Configuration summary with subscription, deployment, and auth method.
- Error diagnosis with Azure-specific causes and evidence.
- Developer vs Azure admin remediation steps.
- Compliance notes on logging and data handling.
## Features
- Maps Foundry setup docs to repeatable troubleshooting workflows.
- Promotes Azure authentication hygiene without secret sprawl.
- Incorporates enterprise network-config requirements.
- Produces admin-ready escalation templates.
## Use Cases
- Roll out Claude Code to Azure-first engineering organizations.
- Debug 401/403 errors against Foundry Claude deployments from CI.
- Standardize deployment names across business units.
- Prepare platform admin tickets with precise RBAC changes.
## Source Notes
Verified against Claude Code Microsoft Foundry and network-config documentation on
**2026-06-16**:
- Official docs describe configuring Claude Code to call Claude models through Microsoft
Foundry with Azure credentials rather than Anthropic API keys.
- Setup covers Foundry project configuration, deployment selection, and authentication
patterns appropriate to enterprise Azure environments.
- Network-config documentation addresses corporate proxies and TLS requirements that
affect Foundry endpoint reachability from developer machines and CI.
## Duplicate Check
Checked content/guides and content/agents for Foundry Claude Code coverage.
claude-code-on-microsoft-foundry-setup is a one-time setup guide. No agents entry provides
ongoing Foundry platform troubleshooting with Azure auth and network-config runbooks.
## Editorial Disclosure
Submitted as an independent community agent entry by kiannidev, based on public Claude
Code Microsoft Foundry documentation and the public anthropics/claude-code repository.
No paid placement, referral, or affiliate relationship.
## Sources
- Claude Code on Microsoft Foundry - https://code.claude.com/docs/en/microsoft-foundry
- Claude Code network config - https://code.claude.com/docs/en/network-config
- Claude Code repository - https://github.com/anthropics/claude-codeAbout this resource
Content
Microsoft Foundry Claude Code Agent is a community-authored reusable prompt for teams deploying Claude Code against Microsoft Foundry on Azure. It applies official Claude Code on Microsoft Foundry and network-config documentation—not an official Anthropic support agent.
Scope Note
This prompt operationalizes documented Foundry configuration and troubleshooting steps from code.claude.com. It does not replace Azure support or Anthropic enterprise onboarding.
Agent Prompt
You are a Microsoft Foundry platform specialist for Claude Code. Help Azure operators configure and debug Foundry-backed Claude Code using only official documentation references.
Workflow:
- Mode confirmation. Verify Claude Code targets Foundry rather than the direct Anthropic API per setup docs.
- Azure resources. Identify subscription, resource group, Foundry project, and Claude deployments.
- Authentication. Review Entra ID, managed identity, or approved credential flows; reject secrets in git.
- Networking. Apply network-config guidance for proxies, private endpoints, and firewall rules for Azure AI endpoints.
- Deployments. Match feature needs to deployed Claude model names and API versions documented for Foundry.
- Enterprise policy. Align managed Claude Code settings, logging, and compliance requirements with Foundry usage.
- Runbook. Provide az CLI checks and Azure admin escalation templates with evidence.
Output contract:
- Configuration summary with subscription, deployment, and auth method.
- Error diagnosis with Azure-specific causes and evidence.
- Developer vs Azure admin remediation steps.
- Compliance notes on logging and data handling.
Features
- Maps Foundry setup docs to repeatable troubleshooting workflows.
- Promotes Azure authentication hygiene without secret sprawl.
- Incorporates enterprise network-config requirements.
- Produces admin-ready escalation templates.
Use Cases
- Roll out Claude Code to Azure-first engineering organizations.
- Debug 401/403 errors against Foundry Claude deployments from CI.
- Standardize deployment names across business units.
- Prepare platform admin tickets with precise RBAC changes.
Source Notes
Verified against Claude Code Microsoft Foundry and network-config documentation on 2026-06-16:
- Official docs describe configuring Claude Code to call Claude models through Microsoft Foundry with Azure credentials rather than Anthropic API keys.
- Setup covers Foundry project configuration, deployment selection, and authentication patterns appropriate to enterprise Azure environments.
- Network-config documentation addresses corporate proxies and TLS requirements that affect Foundry endpoint reachability from developer machines and CI.
Duplicate Check
Checked content/guides and content/agents for Foundry Claude Code coverage. claude-code-on-microsoft-foundry-setup is a one-time setup guide. No agents entry provides ongoing Foundry platform troubleshooting with Azure auth and network-config runbooks.
Editorial Disclosure
Submitted as an independent community agent entry by kiannidev, based on public Claude Code Microsoft Foundry documentation and the public anthropics/claude-code repository. No paid placement, referral, or affiliate relationship.
Sources
- Claude Code on Microsoft Foundry - https://code.claude.com/docs/en/microsoft-foundry
- Claude Code network config - https://code.claude.com/docs/en/network-config
- Claude Code repository - https://github.com/anthropics/claude-code
Source citations
Add this badge to your README
Show that Microsoft Foundry Claude Code Agent is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/agents/microsoft-foundry-claude-code-agent)How it compares
Microsoft Foundry Claude Code Agent side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | Microsoft Foundry Claude Code Agent Community reusable agent prompt for operating Claude Code on Microsoft Foundry using official setup docs: Azure subscriptions, Entra ID auth, deployment names, enterprise network config, and Foundry-specific Claude Code troubleshooting steps. Open dossier | Bedrock Claude Code Platform Agent Community reusable agent prompt for operating Claude Code on Amazon Bedrock using official setup docs: IAM credential chains, regional model IDs, inference profiles, enterprise network config, quota errors, and Bedrock-specific troubleshooting steps. Open dossier | Vertex AI Claude Code Platform Agent Community reusable agent prompt for operating Claude Code on Google Vertex AI using official setup docs: GCP projects, service accounts, regions, VPC-SC constraints, billing alerts, and Vertex-specific Claude Code troubleshooting steps. Open dossier | Enterprise Network Proxy Debugging Agent Community reusable agent prompt for debugging Claude Code behind corporate HTTP proxies and mTLS using official network-config docs: HTTP_PROXY variables, certificate trust, downloads reachability, and remote MCP URL failures. Open dossier |
|---|---|---|---|---|
| Trust | ||||
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Category | agents | agents | agents | agents |
| Source | source-backed | source-backed | source-backed | source-backed |
| Author | kiannidev | kiannidev | kiannidev | kiannidev |
| Added | 2026-06-16 | 2026-06-16 | 2026-06-16 | 2026-06-16 |
| Platforms | Claude Code | Claude Code | Claude Code | Claude Code |
| Source repo | — | — | — | — |
| Safety notes | ✓Client secrets and connection strings must not be committed to repositories. Deployment names and API versions must match Foundry-supported Claude models only. Cross-subscription resources can break policy—keep Foundry resources in approved subscriptions. Azure RBAC changes require admin approval; this agent advises, not applies, policies. | ✓Long-lived access keys in repositories are forbidden; prefer IAM roles and OIDC for CI. Bedrock model allowlists should match security-approved model IDs only. Cross-region failover can violate data residency—confirm before switching regions. IAM policy changes require cloud admin approval; this agent advises, not applies, policies. | ✓Service account keys in repositories are high risk; prefer workload identity federation. Vertex endpoints and regions must match data residency commitments. Shared service accounts across teams complicate audit—prefer scoped identities. GCP org policy changes require admin approval; this agent advises, not applies, policies. | ✓Do not paste proxy credentials or client private keys into shared chat logs. Disabling TLS verification globally is not an acceptable production fix. Split-tunnel VPN changes affect MCP SaaS endpoints—coordinate with security teams. Debugging commands should use read-only curl or openssl checks before changing production laptops. |
| Privacy notes | ✓Azure Monitor and Foundry logs may store request metadata; configure retention accordingly. Customer content handling follows Microsoft and Anthropic agreements for Foundry Claude. Support tickets should redact tenant IDs and subscription names when posted publicly. | ✓Bedrock invocation logs and CloudTrail events may contain prompt metadata—configure retention. Customer content handling follows AWS Bedrock and Anthropic agreements for your account type. Support bundles should redact account IDs and role ARNs when shared externally. | ✓Cloud Logging may capture request metadata; configure exclusions for sensitive projects. Customer data handling follows Google Cloud and Anthropic terms for Vertex Claude models. Support cases should avoid attaching application default credential JSON files. | ✓Proxy logs may capture Anthropic API paths and internal MCP hostnames. Packet captures for debugging must follow company retention and access policies. Support tickets should redact employee emails and internal gateway URLs when possible. |
| Prerequisites |
|
|
|
|
| Install | — | — | — | — |
| Config | — | — | — | — |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Signals
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.