From azure-agent-skills
Guides Azure Dev Box image design, troubleshooting, security, RBAC/SSO, limits, and VS Code dev tunnel workflows. Use for Dev Box deployment and configuration tasks.
How this skill is triggered — by the user, by Claude, or both
Slash command
/azure-agent-skills:azure-dev-boxThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill provides expert guidance for Azure Dev Box. Covers troubleshooting, best practices, decision making, limits & quotas, security, configuration, integrations & coding patterns, and deployment. It combines local quick-reference content with remote documentation fetching capabilities.
This skill provides expert guidance for Azure Dev Box. Covers troubleshooting, best practices, decision making, limits & quotas, security, configuration, integrations & coding patterns, and deployment. It combines local quick-reference content with remote documentation fetching capabilities.
IMPORTANT for Agent: Use the Category Index below to locate relevant sections. For categories with line ranges (e.g.,
L35-L120), useread_filewith the specified lines. For categories with file links (e.g.,[security.md](security.md)), useread_fileon the linked reference file
IMPORTANT for Agent: If
metadata.generated_atis more than 3 months old, suggest the user pull the latest version from the repository. Ifmcp_microsoftdocstools are not available, suggest the user install it: Installation Guide
This skill requires network access to fetch documentation content:
mcp_microsoftdocs:microsoft_docs_fetch with query string from=learn-agent-skill. Returns Markdown.fetch_webpage with query string from=learn-agent-skill&accept=text/markdown. Returns Markdown.| Category | Lines | Description |
|---|---|---|
| Troubleshooting | L36-L46 | Diagnosing and fixing Dev Box issues: connectivity/RDC problems, custom image validation errors, stale/inaccessible boxes, and using Azure Monitor logs for troubleshooting. |
| Best Practices | L47-L52 | Guidance on building efficient Dev Box images, including structuring image definitions and pre-warming Visual Studio caches to speed up developer environments. |
| Decision Making | L53-L58 | Guidance on planning Dev Box deployments (networking, images, capacity) and deciding or preparing to move from Dev Box to Windows 365, including design and transition considerations. |
| Limits & Quotas | L59-L64 | Managing Dev Box capacity: requesting quota/core limit increases and configuring per-user Dev Box limits to control usage and costs. |
| Security | L65-L76 | Securing Dev Box access and sessions: RBAC roles, guest access, SSO, API auth, Key Vault/service principals, Intune Conditional Access and Endpoint Privilege Management. |
| Configuration | L77-L104 | Configuring Dev Box infrastructure: networks, images, catalogs, policies, schedules (stop/hibernate/auto-delete), monitoring, and ARM/template-based provisioning and management. |
| Integrations & Coding Patterns | L105-L109 | Using VS Code dev tunnels to securely connect to Azure Dev Box, including setup, authentication, and remote development workflow configuration. |
| Deployment | L110-L113 | Planning and rolling out Dev Box environments, including architecture and configuration, plus guidance for moving Dev Box pools and individual boxes between Azure regions. |
| Topic | URL |
|---|---|
| Resolve common Microsoft Dev Box issues and questions | https://learn.microsoft.com/en-us/azure/dev-box/dev-box-faq |
| Step-by-step guide to Dev Box connectivity issues | https://learn.microsoft.com/en-us/azure/dev-box/how-to-resolve-dev-box-connectivity-issues |
| Troubleshoot Dev Box custom image validation failures | https://learn.microsoft.com/en-us/azure/dev-box/how-to-troubleshoot-custom-image-validation |
| Fix stale or inaccessible Dev Boxes in Task view | https://learn.microsoft.com/en-us/azure/dev-box/how-to-troubleshoot-dev-box-task-view |
| Troubleshoot known Dev Box connectivity problems | https://learn.microsoft.com/en-us/azure/dev-box/how-to-troubleshoot-remote-desktop-connectivity |
| Use Troubleshoot and Repair for Dev Box RDC issues | https://learn.microsoft.com/en-us/azure/dev-box/how-to-troubleshoot-repair-dev-box |
| Monitor Dev Box with Azure Monitor diagnostic logs | https://learn.microsoft.com/en-us/azure/dev-box/monitor-dev-box |
| Topic | URL |
|---|---|
| Best practices for authoring Dev Box image definitions | https://learn.microsoft.com/en-us/azure/dev-box/concept-authoring-troubleshooting-guide-team-customizations |
| Pre-generate Visual Studio caches in Dev Box images | https://learn.microsoft.com/en-us/azure/dev-box/how-to-generate-visual-studio-caches |
| Topic | URL |
|---|---|
| Plan and design a Microsoft Dev Box deployment | https://learn.microsoft.com/en-us/azure/dev-box/concept-dev-box-deployment-guide |
| Plan transition from Dev Box to Windows 365 | https://learn.microsoft.com/en-us/azure/dev-box/dev-box-roadmap |
| Topic | URL |
|---|---|
| Request Dev Box quota and core limit increases | https://learn.microsoft.com/en-us/azure/dev-box/how-to-request-quota-increase |
| Set per-user Dev Box limits to control costs | https://learn.microsoft.com/en-us/azure/dev-box/tutorial-dev-box-limits |
| Topic | URL |
|---|---|
| Connect to Dev Box from VS Code using dev tunnels | https://learn.microsoft.com/en-us/azure/dev-box/how-to-set-up-dev-tunnels |
| Topic | URL |
|---|---|
| Move Dev Box pools and boxes between regions | https://learn.microsoft.com/en-us/azure/dev-box/how-to-move-dev-box-pool-region |
npx claudepluginhub microsoftdocs/agent-skills --plugin azure-agent-skillsProvides expert guidance for Azure DevTest Labs: troubleshooting, best practices, architecture & design patterns, limits, security, configuration, and deployment. Activates when managing DevTest Labs VMs, images, artifacts, ARM/CLI automation, RBAC/Key Vault, or hub-spoke lab setups.
Generates Azure deployment infrastructure (Bicep/Terraform), azure.yaml, and Dockerfiles. Use for creating or modernizing apps to deploy on Azure.
Routes Azure tasks to the right specialist agent from a catalog. Classifies tasks into domains (architecture, containers, database, etc.) and dispatches single agents or parallel teams. Does not answer Azure questions itself.