deploy-agent-aca-dev Skill
AI-led deployment of the local-LLM sample agent (Ollama + Microsoft Entra Agent ID sidecar) to Azure Container Apps. Use when the user wants to deploy sidecar/dev to ACA, run the agent on Azure without AWS/GCP, host Ollama on Container Apps, promote the docker-compose local-dev stack from ClientSecret to SignedAssertio Published by microsoft in entra-agentid-samples.
What is deploy-agent-aca-dev Skill?
AI-led deployment of the local-LLM sample agent (Ollama + Microsoft Entra Agent ID sidecar) to Azure Container Apps. Use when the user wants to deploy sidecar/dev to ACA, run the agent on Azure without AWS/GCP, host Ollama on Container Apps, promote the docker-compose local-dev stack from ClientSecret to SignedAssertio Published by microsoft in entra-agentid-samples. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Deployment
- Deployment use cases
Technical details
- Install or run with Copy skill directory
When to use deploy-agent-aca-dev Skill
- Use it for deployment.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/entra-agentid-samples
- Skill file: .claude/skills/deploy-agent-aca-dev/SKILL.md
What it does
AI-led deployment of the local-LLM sample agent (Ollama + Microsoft Entra Agent ID sidecar) to Azure Container Apps. Use when the user wants to deploy sidecar/dev to ACA, run the agent on Azure without AWS/GCP, host Ollama on Container Apps, promote the docker-compose local-dev stack from ClientSecret to SignedAssertio
Skill instructions
Deploy Local-LLM Agent to Azure Container Apps (AI-Led) End-to-end, secretless deployment of sidecar/dev (Ollama + Entra Agent ID sidecar) to Azure Container Apps. One federation chain (MI → Entra Blueprint), no second cloud. Canonical tutorial: sidecar/dev/deploy-local-llm-agent-sidecar-container-apps.md. This skill is the automated, fast-path counterpart. When to Use - User says: "deploy dev to ACA", "deploy the local LLM agent to Azure", "Ollama on Container Apps", "ship sidecar/dev to Azure" - User wants a self-contained demo in a tenant where AWS/GCP aren't options (airgapped, regulated, customer-owned) - User hits AADSTS65001 on OBO sign-in — see references/post-deploy-manual-steps.md - User hits AADSTS50011: redirect URI mismatch — same reference - User hits Ollama out of memory or ImagePullBackOff — see references/ollama-on-aca.md - User asks "can I run this without Bedrock / Vertex?" Do NOT Use When - AWS Bedrock deployment — use deploy-agent-aca-aws - GCP Vertex AI deployment
Explore related resources
Frequently asked questions
What is deploy-agent-aca-dev?
deploy-agent-aca-dev is a open-source AI agent skill with Copy skill directory. AI-led deployment of the local-LLM sample agent (Ollama + Microsoft Entra Agent ID sidecar) to Azure Container Apps.
Who is deploy-agent-aca-dev best for?
deploy-agent-aca-dev is best for reusing agent instructions, scripts, and references, deployment workflows.
How do I install deploy-agent-aca-dev?
Install or run deploy-agent-aca-dev using Copy skill directory. Check deploy-agent-aca-dev for the latest setup command.
Is deploy-agent-aca-dev actively maintained?
deploy-agent-aca-dev may need a closer maintenance check before production use.
Auto-fetched from GitHub.
