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
azd version         # Azure Developer CLI, required for Azure Skills deployment workflows
func --version      # Azure Functions Core Tools ≥ 4.x
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)

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.

After Setup

After the environment check completes and you have reported the results, update the local Azure Functions Skills setup state when a state command is available:

1. If the startup context provided an exact npx @azure/functions-skills state setup-complete ... command, run that exact command.
2. Otherwise, when running from a workspace that has .azure-functions-skills/state.local.json, run:

npx @azure/functions-skills state setup-complete --dir .

If the command is unavailable because the CLI is not installed, the npm package has not been updated yet, or the user reached the skill without using the CLI, update .azure-functions-skills/state.local.json directly when that file exists:

1. Preserve every existing field except the setup status timestamps.
2. Set setupSkill to include at least:

   {
     "status": "completed",
     "completedAt": "<current ISO-8601 time>",
     "completedBy": "<active agent if known, otherwise null>"
   }
   

3. Update workspace.updatedAt to the same current ISO-8601 time.

Do this only after the setup check has finished and the user has received the checklist results. If neither the command nor direct file update is possible, state that setup state could not be updated and continue with the next-step guidance.

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-agents to build an AI-powered agent app on Azure Functions (scheduled agents, chat agents, connector-triggered agents, background AI workflows)

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-agents for AI agent apps — 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.