There’s been an important development in the GitHub Copilot space that caught my attention, and I wanted to break it down — not just what was announced, but why it matters and how it fits into the bigger picture.
What’s New
Today we’re announcingazure-functions-skillsinpublic preview: a one-command way to give your favorite coding agent (GitHub Copilot CLI, Claude Code, Codex CLI, VS Code) the skills, agent definition, MCP servers, hooks, and instructions it needs to shipsecure-by-default, scale-readyAzure Functions — end-to-end.
AI coding agents now write the first draft of your function, scaffold the infrastructure, and run the deploy command. But ask a general-purpose agent to build for Azure Functions and the output is usually a step behind. It leans on older programming models that have been superseded, and it has no knowledge of newer capabilities: the serverless agents runtime, Flex Consumption defaults, the new Azure MCP template service, the latest binding shapes, this week’s runtime improvements, or Go language support. Worse, the code it produces oftenleaves hardcoded keys, connection strings, and other secrets sitting in your function for you to clean up later, picks patterns that don’t scale (client-per-invocation, blocking I/O on the hot path), and skips identity-based access entirely. The code compiles, but it isn’t secure, isn’t current, and isn’t using what Azure Functions offers today.
azure-functions-skillscloses that gap. The skills steer the agent toward managed identity, Key Vault references, Flex Consumption, and the binding and concurrency patterns that scale — and the built-indoctorcatches the rest before deploy.
Try it now:npx @azure/functions-skills install
What is azure-functions-skills?
azure-functions-skillsis a plugin for AI coding agents. It builds on the broaderazure-skillsplugin for cross-Azure scenarios, and it ships:
Skills.Task-focused playbooks the agent loads on demand (setup,create,deploy,diagnostics,best-practices,health-status,inventory,doctor,feedback).
An agent definition(functions-copilot) that routes user requests to the right skill and proposes the next workflow when one finishes.
MCP server configuration,hooks, andinstruction files(copilot-instructions.md,CLAUDE.md,AGENTS.md). Everything the agent needs to behave consistently across hosts.
Skill catalog
Theazure-functions-agentsskill is included from launch and supports theAzure Functions serverless agents runtimethat just launched at Build 2026.
Theazure-functions-agentsskill is included from launch and supports theAzure Functions serverless agents runtimethat just launched at Build 2026.
The set is intentionally small at launch. It already includesazure-functions-agentsso you can scaffold and deploy on theAzure Functions serverless agents runtimethat just launched at Build 2026. A skill to assistmigrating worker code to Gois next.
Have a skill you’d like to see? Open an issue athttps://github.com/Azure/azure-functions-skills/issues, or just runazure-functions-feedbackmid-session and the skill itself will prepare the issue draft for you.
Key Takeaways
- Today we’re announcingazure-functions-skillsinpublic preview: a one-command way to give your favorite coding agent (GitHub Copilot CLI, Claude Code, Codex CLI, VS Code) the skills, agent definition, MCP servers, hooks, and instructions it needs to shipsecure-by-default, scale-readyAzure Functions — end-to-end.
- AI coding agents now write the first draft of your function, scaffold the infrastructure, and run the deploy command.
- azure-functions-skillscloses that gap.
- In about 5 minutes you’ll have a working Functions project scaffolded with managed identity, a deploy-ready workflow, and adoctorHTML report you can wire into CI.
- Requirements: Node 18+, an Azure subscription, and one of: GitHub Copilot CLI, Claude Code, Codex CLI, or VS Code.
Why This Matters
Developer productivity is one of the highest-ROI applications of AI today. Copilot is proving that AI can augment — not replace — human expertise, making experienced developers more productive and helping newcomers ramp up faster.
This development is particularly significant because it reflects the broader industry shift toward making AI more accessible, enterprise-ready, and integrated into existing workflows. For teams already invested in the Microsoft ecosystem, this is a clear signal of where the platform is heading.
My Take
The technical evolution of Copilot is fascinating from an AI systems perspective. We’ve moved from completion-based assistance (predict the next line) to agent-mode (understand the intent, decompose the problem, execute multi-file changes, run tests, iterate on failures). This is a fundamental architectural shift — from a stateless token predictor to a stateful reasoning agent with tool use. What’s technically impressive is the context management: Copilot now maintains a working memory of your entire codebase, open issues, PR history, and team conventions. The retrieval augmentation layer that grounds suggestions in your specific codebase (not just generic patterns) is what makes the difference between a toy and a production tool. The agentic workflows — where Copilot can plan, execute, verify, and self-correct — represent the state of the art in applied AI agents today.
Business Translation
For the C-Suite: Developer talent is the #1 constraint in digital transformation. Copilot delivers a measurable 25-55% productivity gain (validated by Microsoft/GitHub research across 1M+ developers). In financial terms: a 500-developer organization saves $15-30M annually in equivalent output — without hiring. More importantly, it reduces time-to-market for features, which directly impacts revenue capture. The strategic play isn’t just efficiency — it’s enabling your existing engineering team to tackle projects that were previously impossible given resource constraints.
📖 Read the original article for the full details and official documentation.
Written by Cyril Bou-Harb — Solution Engineer, Cloud & AI at Microsoft. Opinions and analysis are my own and do not represent Microsoft’s official position.