Azure Functions CLI 4.15.2

Host Version

• Host Runtime Version: 4.1053.200
• In-Proc CLI:
  • CLI Version: 4.8.0
  • Host Runtime Version: 4.52.100 (includes 4.852.100, 4.652.100)

Changes

• Add Dockerfile generation (func init --docker / --docker-only) for .NET 11 isolated projects using the chiseled mcr.microsoft.com/azure-functions/dotnet-isolated:4-dotnet-isolated11.0-chiseled base image. (#5599)
• Require explicit confirmation before func bundles download --force recursively deletes an existing extension bundle directory. (#5666)

Azure Functions CLI 4.15.1

Host Version

• Host Runtime Version: 4.1053.200
• In-Proc CLI:
  • CLI Version: 4.8.0
  • Host Runtime Version: 4.52.100 (includes 4.852.100, 4.652.100)

Changes

Azure Functions CLI 4.15.0

Host Version

• Host Runtime Version: 4.1053.200
• In-Proc CLI:
  • CLI Version: 4.8.0
  • Host Runtime Version: 4.52.100 (includes 4.852.100, 4.652.100)

Changes

• Add explicit .NET 11 C# isolated initialization with updated templates. The default remains .NET 10; .NET 11 F# scaffolding and Docker support are not yet available.
• Support worker-indexed .NET isolated build and publish outputs in func pack, including --no-build, without requiring a separate functions.metadata file.
• Fixed Python native dependency builds to inherit authenticated pip indexes in Docker containers (#5574)
• Make host.json optional across func publish, and pack (#5488)
• Fixed func kubernetes deploy failing with Invalid property identifier character: { for dotnet-isolated projects with more than one function. The print-functions.sh script previously used a sed command that only captured the last function name and produced malformed JSON; replaced with awk to correctly key each function object by its name field. (#3585)

Azure Functions CLI 4.14.0

Host Version

• Host Runtime Version: 4.1052.200
• In-Proc CLI:
  • CLI Version: 4.7.0
  • Host Runtime Version: 4.51.100 (includes 4.851.100, 4.651.100)

Changes

• Added durable-functions dependency to package.json when creating Node.js durable function templates (#5495)
• Changed func start to bind to the IPv4 loopback address (127.0.0.1) by default instead of 0.0.0.0, and added an opt-in --address flag (and Host.LocalHttpAddress setting in local.settings.json) to override the bind address (#5484)
  • Potential breaking change: the host now binds to 127.0.0.1 by default, so it is only reachable from the local machine. Setups that relied on binding to 0.0.0.0 — for example reaching the host from outside a Docker container via a published port — will no longer connect. Workaround: start the host with func start --address 0.0.0.0 (or set "LocalHttpAddress": "0.0.0.0" under Host in local.settings.json) to restore the previous behavior.

Azure Functions CLI 4.13.0

Host Version

• Host Runtime Version: 4.1051.300
• In-Proc CLI:
  • CLI Version: 4.7.0
  • Host Runtime Version: 4.51.100 (includes 4.851.100, 4.651.100)

Changes

• Removed warning log for remote build with Python 3.14 Flex apps, as remote build is now supported (#5375)
• Fixed npm postinstall silently swallowing extraction errors (#5281)
• Added lazy first-use install for npm RFC #868 compatibility (#5291)
• Added warning when key vault references fail to resolve (#5373)
• Replaced deprecated url.parse in npm installer (#5371)
• Enhanced func CLI static gitignore and streamlined Azurite entries (#5084)
• Bumped dotnet templates version to 4.0.5590 (#5271)
• Bumped https-proxy-agent dependency (#5335)
• Updated target framework to .NET 10 (#4850)
• Fix Flex Health Check to use defaultHostName instead of enabledHostNames (#5462)
• Added durable-functions dependency to package.json when creating Node.js durable function templates (#5495)
• Changed func start to bind to the IPv4 loopback address (127.0.0.1) by default instead of 0.0.0.0, and added an opt-in --address flag (and Host.LocalHttpAddress setting in local.settings.json) to override the bind address (#5484)
  • Potential breaking change: the host now binds to 127.0.0.1 by default, so it is only reachable from the local machine. Setups that relied on binding to 0.0.0.0 — for example reaching the host from outside a Docker container via a published port — will no longer connect. Workaround: start the host with func start --address 0.0.0.0 (or set "LocalHttpAddress": "0.0.0.0" under Host in local.settings.json) to restore the previous behavior.

Azure Functions CLI 4.12.1

Host Version

• Host Runtime Version: 4.1048.200
• In-Proc CLI:
  • CLI Version: 4.6.0
  • Host Runtime Version: 4.49.100 (includes 4.849.100, 4.649.100)

Changes

• No changes to core CLI, in-proc CLI updated to 4.6.0 with host version 4.49.100

Azure Functions CLI

What's changed since preview.1

• Fix func run failing to resolve installed prerelease worker workloads against built-in profile ranges (e.g. node [3.13.0] now accepts 3.13.0-preview.1). (#5286)

New to v5?

This is a preview of the v5 CLI rebuild. See the v5.0.0-preview.1 release notes for the full overview, or jump in below.

⚠️ Preview. Not production-ready, not at v4 feature parity.

Install

PowerShell (Windows, macOS, Linux):

iex "& { $(irm https://aka.ms/func-cli/install.ps1) } -Prerelease"

Bash (macOS, Linux):

curl -sSL https://aka.ms/func-cli/install.sh | bash -s -- --prerelease

You maybe need to run with -Force (pwsh) | --force (bash) if you are upgrading.

Getting started

The CLI ships with just the core commands. Before you can create or run a Functions app, you need to install the workloads for your stack. The easiest way to do that is func setup.

1. Set up your machine

Run func setup on its own to get an interactive multi-select prompt for the stacks you want:

func setup

Prefer non-interactive? Pass the stack directly with --features:

func setup --features dotnet     # .NET
func setup --features node       # Node.js
func setup --features python     # Python
func setup --features go         # Go

2. Create a project

func quickstart                  # complete sample app
# or
func init                        # initalize an empty project

Add individual Function templates via

func new

3. Run it locally

func run

Feedback

File issues at https://github.com/Azure/azure-functions-core-tools/issues and tag with v5.

Azure Functions CLI

⚠️ Preview release. This is the first public preview of the Azure Functions CLI. It is not production-ready and is not at feature parity with Core Tools (v4). Expect breaking changes before GA. For stable workflows, keep using Core Tools.

This release is a ground-up rebuild designed around a small core func binary plus on-demand workloads (host, language stacks, templates, extension bundle).

What's new in v5

• New architecture. Small core binary built on System.CommandLine, Spectre.Console, and .NET 10. The Functions host, language stacks, templates, and the extension bundle ship as separate workloads installed on demand.
• Per-stack workloads. Install only what you need: dotnet, node, python, or go (more coming soon).
• Decoupled host. The Functions host is no longer baked into the CLI. It's a workload of its own, so you can install, update, or pin host versions independently of the CLI version, and run multiple host versions side by side.
• Profiles. Pin the host (and other workload versions) to match a specific Azure Functions environment, so your local install lines up with what Azure is running.
• Interactive func run dashboard. When attached to a TTY, func run (alias func start) renders a live dashboard: a sticky header showing the host status and list
• Rebranded. The product is now Azure Functions CLI. The legacy "Core Tools" name is being phased out in v5.

Install

Because this is a preview, you must opt in to prereleases when installing.

PowerShell (Windows, macOS, Linux):

iex "& { $(irm https://aka.ms/func-cli/install.ps1) } -Prerelease"

Bash (macOS, Linux):

curl -sSL https://aka.ms/func-cli/install.sh | bash -s -- --prerelease

You maybe need to run with -Force (pwsh) | --force (bash) if you are upgrading.

Both scripts auto-detect your OS and architecture, download this release from GitHub, and install to ~/.azure-functions. The install directory is added to your PATH automatically (run source ~/.bashrc or open a new shell on Linux/macOS to pick it up).

Getting started

The CLI ships with just the core commands. Before you can create or run a Functions app, you need to install the workloads for your stack. The easiest way to do that is func setup.

1. Set up your machine

Run func setup on its own to get an interactive multi-select prompt for the stacks you want:

func setup

Prefer non-interactive? Pass the stack directly with --features:

func setup --features dotnet     # .NET
func setup --features node       # Node.js
func setup --features python     # Python
func setup --features go         # Go

Or set up multiple stacks at once (comma-separated or repeated):

func setup --features node,python

Either way, func setup installs the Functions host, the worker for each selected stack, templates, and the extension bundle.

2. Create a project

Two scaffolding entry points, depending on what you want:

• func quickstart: scaffolds a complete, ready-to-run sample app (trigger code, host config, optional IaC) from a curated catalog. Best when you want a working starting point.
• func init + func new: build a project from scratch. func init creates an empty project; func new is the template engine for adding individual functions by trigger (HTTP, Timer, Blob, Queue, Cosmos DB, Durable, etc.).

func quickstart                  # complete sample app
# or
func init                        # initalize an empty project

Add individual Function templates via

func new

3. Run it locally

func run

Feedback

File issues at https://github.com/Azure/azure-functions-core-tools/issues and tag with v5.

Azure Functions CLI 4.12.0

Host Version

• Host Runtime Version: 4.1048.200
• In-Proc CLI:
  • CLI Version: 4.5.0
  • Host Runtime Version: 4.48.100 (includes 4.848.100, 4.648.100)

Changes

• Fix HttpsProxyAgent is not a constructor error in install.js when installing behind a proxy (https-proxy-agent v9 requires a named import).
• Remove azure-functions-core-tools from the devDependencies of generated function app templates (package-js.json, package-js-v4.json, package-ts.json, package-ts-v4.json). Users get the CLI from their system install; pulling it in again via npm install doubled disk usage and made every project's install fragile to Core Tools postinstall regressions.

Preview Feature

• Add preview Go language support to func init, func start, func pack, and func publish (#4875, #4892, #4943). Behaviour, build/publish flags, and deployment layout may change before GA.

Azure Functions CLI 4.11.0

Host Version

• Host Runtime Version: 4.1048.200
• In-Proc CLI:
  • CLI Version: 4.5.0
  • Host Runtime Version: 4.48.100 (includes 4.848.100, 4.648.100)

Changes

• Fix func pack throwing cryptic Unsupported runtime: None when local.settings.json is absent and FUNCTIONS_WORKER_RUNTIME is not set (#4829)
• Mark Node.js 24 as GA in stacks.json (add Flex Consumption SKU) (#4867)
• Surface SSL/TLS certificate errors clearly when SSL inspection proxies intercept connections (#4857)
• Fix func kubernetes deploy race condition where kubectl rollout status ran before the Deployment was registered (#4919)
• Fix func kubernetes delete to honor --no-docker instead of failing on registry auth (#4919)
• Add McpPromptTrigger template for dotnet-isolated func new (#4891)
• Fix func azure storage fetch-connection-string failing with "Cannot find storage account" due to ARM eventual consistency (#4884)
• Remove gozip binaries from the CLI (#4959)