Azure Functions Setup

Language: Always respond in the same language the user is using.

azure-functions-setup — Azure Functions Environment Setup

Verify that the developer's environment has all prerequisites for Azure Functions development.

Checks

Run each check and report results:

az --version        # Azure CLI ≥ 2.60 (≥ 2.87.0 for Go deployments)
azd version         # Azure Developer CLI, required for Azure Skills deployment workflows
func --version      # Azure Functions Core Tools ≥ 4.x (≥ 4.12 for Go projects)
node --version      # Node.js 24 or 22 for new Node.js/TypeScript projects
python --version    # Python 3.13 preferred; 3.10-3.13 supported for Python projects
python3 --version   # Use this fallback when python is not on PATH
dotnet --version    # .NET SDK ≥ 8.0 (if .NET project)
go version          # Go 1.24 or later (if Go project; Go support is in preview)

Run the language checks that match the user's project or stated intent. Do not report a missing Go toolchain as a problem for a Python project, and do not report a missing Python interpreter as a problem for a Go project.

Azure Skills Plugin Check

Azure Functions deployment is proxied through the Azure Skills deployment workflow. For deployment scenarios, verify that the Azure Skills plugin is installed and that these skills are available:

• azure-prepare
• azure-validate
• azure-deploy

How to detect availability: Check your current tool/skill list for the above skill names. If they appear in the list of available skills (e.g., in <available_skills> or equivalent plugin registry), they are installed. You do not need to run any commands — the presence of these skills in the agent's tool list is sufficient confirmation.

If the Azure Skills plugin is missing, install it for the active host before using azure-functions-deploy.

Output Format

Present results as a checklist:

Azure Functions Environment Check

  ✅ Azure CLI          <version>
  ✅ Azure Developer CLI <version>
  ✅ Core Tools         <version>
  ✅ Node.js            <version>
  ⚠️  Azure subscription  Not logged in → Run 'az login'
  ⚠️  Azure Skills plugin Missing → install before azure-functions-deploy

Fix Instructions

For each failing check, provide:

1. What's wrong — one-line description
2. How to fix — exact install/fix command for the user's OS and shell
3. Docs link — Microsoft Learn URL

Use the user's operating system when choosing fix commands. Do not give Linux-only installation commands to Windows or macOS users. If the operating system or package manager is unclear, show the OS-specific choices and ask the user to run the one that matches their machine.

For language runtimes, prefer the latest Azure Functions GA-supported version for new installs. Do not recommend preview runtimes unless the user explicitly asks for previews.

Azure Functions runtime 4.x currently supports Node.js 24 and 22 for Node.js/TypeScript apps, and Python 3.10 through 3.13 for Python apps. Python 3.14 can appear in preview; keep Python 3.13 as the default recommendation until the user opts into preview support. Mention hosting caveats when relevant: newer language versions might not be available on Linux Consumption, so Flex Consumption is the safer default for new Linux-hosted apps.

Go prerequisites

Go support on Azure Functions is in public preview. Say so before recommending it for production work.

Go has two version floors that no other language has.

• Core Tools 4.12 or later. The native worker that runs Go ships in 4.12. Earlier 4.x versions reject a Go project with a misleading "unsupported worker runtime" error, so compare the reported func --version against 4.12 rather than only checking for a 4. prefix.
• Azure CLI 2.87.0 or later, needed when creating Azure resources or deploying packages. The general 2.60 floor used elsewhere in this checklist is not sufficient for Go, so a Go environment can otherwise be reported as ready when it is not. Check with az version.

If the installed Core Tools or Azure CLI is present but below the Go floor, report it as a failing check and give the upgrade command for the user's platform.

Go projects also use FUNCTIONS_WORKER_RUNTIME=native in local.settings.json, not go or golang. Mention this when a Go project is detected, because it is the most common local configuration mistake.

Scaffold Go projects with func init <project-name> --worker-runtime go. func new is not supported for Go.

See https://learn.microsoft.com/azure/azure-functions/functions-reference-go for the authoritative prerequisite list.

After Setup

After the environment check completes, report the checklist and recommend the most relevant next skill. No local setup state is created or updated.

When all checks pass, suggest the next step:

✅ Your environment is ready! Next:

• Use azure-functions-create to scaffold a new Azure Functions project (HTTP triggers, timer triggers, queue triggers, etc.)
• Use azure-functions-hosted-skills to build cloud-hosted, event-driven intelligent capabilities with Markdown, Functions triggers, code, tools, HTTP, and MCP

For deployment, confirm the Azure Skills plugin is available before suggesting azure-functions-deploy. azure-functions-deploy delegates to azure-prepare, azure-validate, and azure-deploy.

Next steps

• On success, suggest azure-functions-create for traditional Functions projects, or azure-functions-hosted-skills for Azure Functions Hosted Skills — let the user choose based on their goal.
• On failure, keep the user in azure-functions-setup: explain fixes, then ask them to rerun setup verification.
• If deployment is requested and Azure Skills is missing, keep the user in azure-functions-setup until the Azure Skills plugin is installed or the user explicitly chooses a fallback deployment path.