Aspire
microsoft/aspire.dev
Orchestrates Aspire distributed applications using the Aspire CLI for running, debugging, and managing distributed apps.
Provides deployment commands and troubleshooting for Azure Container Apps.
The automated check flagged lines worth reading first. See the safety section below.
$ npx skills add microsoft-foundry/foundry-agent-webapp --skill deploying-to-azure -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install microsoft-foundry/foundry-agent-webapp deploying-to-azure --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/microsoft-foundry/foundry-agent-webapp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/deploying-to-azure .claude/skills/deploying-to-azure && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "deploying-to-azure" agent skill from https://github.com/microsoft-foundry/foundry-agent-webapp/tree/main/.github/skills/deploying-to-azure into .claude/skills/deploying-to-azure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploying-to-azure", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/microsoft-foundry/foundry-agent-webapp/tree/main/.github/skills/deploying-to-azureType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add microsoft-foundry/foundry-agent-webapp --skill deploying-to-azure -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install microsoft-foundry/foundry-agent-webapp deploying-to-azure --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft-foundry/foundry-agent-webapp.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/deploying-to-azure .agents/skills/deploying-to-azure && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "deploying-to-azure" agent skill from https://github.com/microsoft-foundry/foundry-agent-webapp/tree/main/.github/skills/deploying-to-azure into .agents/skills/deploying-to-azure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploying-to-azure", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add microsoft-foundry/foundry-agent-webapp --skill deploying-to-azure -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install microsoft-foundry/foundry-agent-webapp deploying-to-azure --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft-foundry/foundry-agent-webapp.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/deploying-to-azure .cursor/skills/deploying-to-azure && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "deploying-to-azure" agent skill from https://github.com/microsoft-foundry/foundry-agent-webapp/tree/main/.github/skills/deploying-to-azure into .cursor/skills/deploying-to-azure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploying-to-azure", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/microsoft-foundry/foundry-agent-webapp.git --path .github/skills/deploying-to-azure--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add microsoft-foundry/foundry-agent-webapp --skill deploying-to-azure -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install microsoft-foundry/foundry-agent-webapp deploying-to-azure --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft-foundry/foundry-agent-webapp.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/deploying-to-azure .gemini/skills/deploying-to-azure && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "deploying-to-azure" agent skill from https://github.com/microsoft-foundry/foundry-agent-webapp/tree/main/.github/skills/deploying-to-azure into .gemini/skills/deploying-to-azure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploying-to-azure", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install microsoft-foundry/foundry-agent-webapp deploying-to-azureInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add microsoft-foundry/foundry-agent-webapp --skill deploying-to-azure -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/microsoft-foundry/foundry-agent-webapp.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/deploying-to-azure .github/skills/deploying-to-azure && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "deploying-to-azure" agent skill from https://github.com/microsoft-foundry/foundry-agent-webapp/tree/main/.github/skills/deploying-to-azure into .github/skills/deploying-to-azure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploying-to-azure", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add microsoft-foundry/foundry-agent-webapp --skill deploying-to-azure -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install microsoft-foundry/foundry-agent-webapp deploying-to-azure --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft-foundry/foundry-agent-webapp.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/deploying-to-azure .opencode/skills/deploying-to-azure && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "deploying-to-azure" agent skill from https://github.com/microsoft-foundry/foundry-agent-webapp/tree/main/.github/skills/deploying-to-azure into .opencode/skills/deploying-to-azure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploying-to-azure", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
deploying-to-azureProvides deployment commands and troubleshooting for Azure Container Apps.
Deploying To Azure is an agent skill from microsoft-foundry/foundry-agent-webapp. Provides deployment commands and troubleshooting for Azure Container Apps. Use when running azd commands, deploying containers, debugging deployment failures, or updating infrastructure in this repository.
Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering Containers, Deployment and Debugging. It works with Microsoft Azure, Docker and Bicep. The repository describes itself as: GitHub Copilot enabled repo for building and deploying a web application with Entra ID authentication and integrated with Azure AI Foundry Agents. The licence is MIT.
4 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit f6cb362. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
azFrom the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
learn.microsoft.comai.azure.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Deploying To Azure loads about 2.2k tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 650 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found patterns that need a careful read before installing.
- Custom npm registries: Add `.npmrc` to `frontend/` directory_ID not set` | Run `azd up` to generate `.env` files |4. Generates local dev config files (`.env.local` for frontend, `.env` for backend)# Remove local .env files to prevent localhost configRUN rm -f .env.local .env.development .envAutomated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from microsoft-foundry/foundry-agent-webapp at commit f6cb362, republished under its MIT licence (© microsoft-foundry). 650 words, ~2,207 tokens.
.claude/skills/deploying-to-azure/SKILL.md (or your agent's skills folder).Container logs and deployment output can be massive (1000+ lines). Delegate to subagent for:
runSubagent(
prompt: "ANALYSIS task - analyze deployment issue.
**Problem**: [describe the deployment failure]
**Run these commands**:
1. az containerapp logs show --name <app> --resource-group <rg> --tail 200
2. az containerapp show --name <app> --resource-group <rg> --query 'properties.provisioningState'
**Find**:
- Error messages or stack traces
- Resource provisioning failures
- Configuration mismatches
**Return** (max 15 lines):
- Root cause (1-2 sentences)
- Key error lines only (max 5)
- Suggested fix command
Do NOT include full log output.",
description: "Debug: [deployment issue]"
)| Delegate to Subagent | Keep Inline |
|---|---|
| Full log analysis (100+ lines) | Quick status check |
| Multi-resource debugging | Single az command |
| RBAC permission audit | Container image query |
| Startup failure diagnosis | Provisioning state check |
| Command | Purpose | Time |
|---|---|---|
azd up | Full deployment (Entra app + infrastructure + container) | 10-12 min |
azd deploy | Code-only deployment (Docker rebuild + push) | 3-5 min |
azd provision | Re-run infrastructure + AI Foundry discovery | 5-7 min |
azd env set ENTRA_SERVICE_MANAGEMENT_REFERENCE "<guid>"identifierUri on Entra app + updates redirect URIs + assigns RBAC to AI Foundry + generates local dev configImplementation:
infra/entra-app.bicep (Entra app registration via Microsoft Graph Bicep extension)deployment/hooks/preprovision.ps1 (AI Foundry discovery)deployment/hooks/postprovision.ps1 (Entra config + RBAC + local config generation)deployment/hooks/predeploy.ps1 (container build + push)deployment/hooks/modules/Get-AIFoundryAgents.ps1 (agent discovery via REST)Build order: React → .NET → Runtime
deployment/docker/frontend.Dockerfiledeployment/docker/backend.Dockerfile.npmrc to frontend/ directoryAuto-discovery (azd up): Searches subscription for AI Foundry resources → prompts to select if multiple → discovers agents via REST API → configures RBAC.
Change resource: Run azd provision to re-run discovery, or:
azd env set AI_FOUNDRY_RESOURCE_GROUP <rg>
azd provisionGET /api/health every 30s) and startup (GET /api/health every 10s, 5s initial delay) probes configured on the Container AppAcrPull role — no admin credentials or secrets. The MI is created in main-infrastructure.bicep before the Container App, avoiding the chicken-and-egg problem.container-app.bicep)| Issue | Fix |
|---|---|
VITE_ENTRA_SPA_CLIENT_ID not set | Run azd up to generate .env files |
AI_AGENT_ENDPOINT not configured | Run azd provision to re-discover AI Foundry |
| No AI Foundry resources found | Create at https://ai.azure.com |
| Multiple AI Foundry resources | Run azd provision to select different resource |
| Container not updating | Check az containerapp logs show --name $app --resource-group $rg |
| Container fails health check | Verify /api/health endpoint returns 200 — check container logs for startup errors |
# Check current container image
az containerapp show --name $app --resource-group $rg `
--query "properties.template.containers[0].image"
# View container logs
az containerapp logs show --name $app --resource-group $rg --tail 100
# Check RBAC assignments
$principalId = az containerapp show --name $app --resource-group $rg `
--query "identity.principalId" -o tsv
az role assignment list --assignee $principalIdFile: deployment/hooks/preprovision.ps1
What it does:
Get-AIFoundryAgents.ps1Note: Entra app registration is handled by Bicep (infra/entra-app.bicep), not this hook.
File: deployment/hooks/postprovision.ps1
What it does:
identifierUri (api://{clientId}) on Entra app — can't be done in Bicep because it references the auto-generated appId.env.local for frontend, .env for backend)Why RBAC via CLI?: Using Azure CLI for role assignment prevents azd from tracking the external AI Foundry resource group, avoiding accidental deletion on azd down.
File: deployment/hooks/predeploy.ps1
What it does:
SERVICE_WEB_IMAGE_NAME env var for BicepFile: deployment/docker/frontend.Dockerfile (production build)
# Stage 1: Build React Frontend
FROM node:22-alpine AS frontend-builder
ARG ENTRA_SPA_CLIENT_ID
ARG ENTRA_TENANT_ID
WORKDIR /app/frontend
COPY frontend/ ./
RUN npm ci
# Remove local .env files to prevent localhost config
RUN rm -f .env.local .env.development .env
ENV NODE_ENV=production
ENV VITE_ENTRA_SPA_CLIENT_ID=$ENTRA_SPA_CLIENT_ID
ENV VITE_ENTRA_TENANT_ID=$ENTRA_TENANT_ID
RUN npm run build
# Stage 2: Build .NET Backend
FROM mcr.microsoft.com/dotnet/sdk:10.0 AS backend-builder
WORKDIR /app
COPY backend/WebApp.sln ./
COPY backend/WebApp.Api/WebApp.Api.csproj ./backend/WebApp.Api/
COPY backend/WebApp.ServiceDefaults/WebApp.ServiceDefaults.csproj ./backend/WebApp.ServiceDefaults/
RUN dotnet restore backend/WebApp.Api/WebApp.Api.csproj
COPY backend/ ./backend/
RUN dotnet publish backend/WebApp.Api/WebApp.Api.csproj -c Release -o /app/publish
# Stage 3: Runtime - Single container serving API + static files
FROM mcr.microsoft.com/dotnet/aspnet:10.0-alpine
WORKDIR /app
COPY --from=backend-builder /app/publish ./
COPY --from=frontend-builder /app/frontend/dist ./wwwroot
EXPOSE 8080
ENV ASPNETCORE_URLS=http://+:8080
ENV ASPNETCORE_ENVIRONMENT=Production
ENTRYPOINT ["dotnet", "WebApp.Api.dll"]| Topic | URL |
|---|---|
| Azure Container Apps | https://learn.microsoft.com/azure/container-apps/overview |
| Container Apps quickstart | https://learn.microsoft.com/azure/container-apps/quickstart-portal |
| Azure Developer CLI (azd) | https://learn.microsoft.com/azure/developer/azure-developer-cli/overview |
| azd templates | https://learn.microsoft.com/azure/developer/azure-developer-cli/azd-templates |
| Azure AI Foundry overview | https://learn.microsoft.com/azure/ai-foundry/what-is-ai-foundry |
| AI Foundry Agent Service | https://learn.microsoft.com/azure/ai-foundry/agents/overview |
| Managed Identity | https://learn.microsoft.com/entra/identity/managed-identities-azure-resources/overview |
| Cognitive Services RBAC | https://learn.microsoft.com/azure/ai-services/authentication |
© microsoft-foundry, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .github/skills/deploying-to-azure of microsoft-foundry/foundry-agent-webapp.
Open the folder on GitHubat commit f6cb362
Deploying To Azure next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Deploying To Azure this skillmicrosoft-foundry/foundry-agent-webapp | 127 | — | ~2.2k | Automated safety check: Warn | MIT | |
| Aspiremicrosoft/aspire.dev | 196 | 4 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Aspire DeploymentCommunityToolkit/Aspire | 629 | — | ~4.5k | Automated safety check: Notes | MIT | |
| Medusa Cloud Local Buildmedusajs/medusa-agent-skills | 227 | — | ~1k | Automated safety check: Notes | None | |
| Azure Anomaly DetectorMicrosoftDocs/Agent-Skills | 777 | — | ~1.1k | Automated safety check: Pass | CC-BY-4.0 | |
| Azure Preparemicrosoft/GitHub-Copilot-for-Azure | 255 | 1 repos | ~3.2k | Automated safety check: Pass | MIT |
microsoft/aspire.dev
Orchestrates Aspire distributed applications using the Aspire CLI for running, debugging, and managing distributed apps.
CommunityToolkit/Aspire
WORKFLOW SKILL — Deploy Aspire apps from AppHost models to Docker Compose, Kubernetes, Azure, AWS, or preview Radius.
medusajs/medusa-agent-skills
Reproduces a Medusa Cloud build on your machine with mcloud local build, to debug build-failed deployments without pushing or waiting on Cloud.
MicrosoftDocs/Agent-Skills
Expert knowledge for Azure AI Anomaly Detector development including troubleshooting, best practices, limits & quotas, configuration, and deployment.
microsoft/GitHub-Copilot-for-Azure
Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow.
microsoft/GitHub-Copilot-for-Azure
Assess whether source code is ready to deploy to Azure — the check BEFORE infrastructure work.
microsoft-foundry/foundry-agent-webapp
Provides commit message format and workflow for this repository.
microsoft-foundry/foundry-agent-webapp
Provides SSE streaming patterns for the chat API and frontend.
microsoft-foundry/foundry-agent-webapp
Provides structured plan template for feature implementation.
microsoft-foundry/foundry-agent-webapp
Provides research patterns for Foundry Agent Service SDK. An agent skill from microsoft-foundry/foundry-agent-webapp.
microsoft-foundry/foundry-agent-webapp
Synchronize MCP server configuration between VS Code (.vscode/mcp.json) and Copilot CLI (~/.copilot/mcp-config.json).
microsoft-foundry/foundry-agent-webapp
Validate that Copilot CLI can see all repo skills, MCP servers, and custom instructions.
Works with
Categories
Provides deployment commands and troubleshooting for Azure Container Apps. Deploying To Azure is an agent skill from microsoft-foundry/foundry-agent-webapp. Provides deployment commands and troubleshooting for Azure Container Apps.
Deploying To Azure fits situations like: running azd commands; deploying containers; debugging deployment failures; updating infrastructure in this repository.
Run `npx skills add microsoft-foundry/foundry-agent-webapp --skill deploying-to-azure -a claude-code`. Or copy the skill folder (.github/skills/deploying-to-azure in microsoft-foundry/foundry-agent-webapp) into .claude/skills/deploying-to-azure in your project. Claude Code loads it when a task matches its description.
Run `npx skills add microsoft-foundry/foundry-agent-webapp --skill deploying-to-azure -a codex`. Or copy the skill folder (.github/skills/deploying-to-azure in microsoft-foundry/foundry-agent-webapp) into .agents/skills/deploying-to-azure in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add microsoft-foundry/foundry-agent-webapp --skill deploying-to-azure -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/deploying-to-azure, .gemini/skills/deploying-to-azure, .github/skills/deploying-to-azure and .opencode/skills/deploying-to-azure in your project.
Going by SKILL.md and its folder, Deploying To Azure needs the command-line tools its instructions call (az). Our summary lists: Docker.
SKILL.md names 2 domains. As links in the text: learn.microsoft.com and ai.azure.com. This is read from the text; nothing was executed.
Our automated static check of SKILL.md flagged 1 warning(s): mentions a credentials file (ssh keys, cloud or package-manager tokens). Read the flagged lines before installing; the check is not a guarantee either way.
Deploying To Azure is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.2k tokens (SKILL.md is roughly 8.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Deploying To Azure: Aspire (microsoft/aspire.dev, 196 stars), Aspire Deployment (CommunityToolkit/Aspire, 629 stars), Medusa Cloud Local Build (medusajs/medusa-agent-skills, 227 stars) and Azure Anomaly Detector (MicrosoftDocs/Agent-Skills, 777 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
microsoft-foundry (a GitHub organization) maintains it in microsoft-foundry/foundry-agent-webapp, which has 127 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on April 21, 2026.
Source: microsoft-foundry/foundry-agent-webapp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.