---
next_cursor: eyJzY29yZSI6MCwic2VxIjoxNDU2LCJzaW5jZSI6bnVsbCwidG9vbCI6ImF6ZCIsInYiOjF9
has_more: true
next: https://sincecutoff.com/v1/changes.md?tool=azd&score=0&cursor=eyJzY29yZSI6MCwic2VxIjoxNDU2LCJzaW5jZSI6bnVsbCwidG9vbCI6ImF6ZCIsInYiOjF9
items: 10
---
# sincecutoff.com changes: azd

## azd auto-detects Bicep or Terraform from infra files (azd, 2026-01-15)
Published 2026-10-19
- slug: azd-auto-detects-bicep-or-terraform-from-infra-files-0138d1ccfdec
- score: 0.95

How to use it:

When `infra.provider` is unset, run `azd provision` to provision from the project’s infrastructure files; for automatic Bicep or Terraform detection, use azd v1.23.0 or later. If both file types are present, set `infra.provider` explicitly.

Examples:

```
azd provision
```

```
infra:
  provider: <bicep|terraform>
```

- why_it_matters: Provision a project with Bicep or Terraform files when `infra.provider` is unset in `azure.yaml`.
- sources: <https://github.com/Azure/azure-dev/releases/tag/azure-dev-cli_1.23.0>, <https://github.com/Azure/azure-dev/pull/6461>, <https://learn.microsoft.com/en-us/azure/developer/azure-developer-cli/azd-commands>, <https://learn.microsoft.com/en-us/azure/developer/azure-developer-cli/azd-schema>, <https://github.com/Azure/azure-dev/blob/azure-dev-cli_1.23.0/cli/azd/pkg/project/importer.go>
- gotchas: "Version: 1.23.0"; "infra.provider: Infrastructure provisioning provider; documented values include `bicep` and `terraform`."; "Prerequisite: Use Azure Developer CLI v1.23.0 or later for the release-note-described auto-detection."; "Prerequisite: `azure.yaml` belongs at the project root and configures project infrastructure; the `infra` directory contains infrastructure files."; "Detection scans the infra directory and ignores subdirectories."; "If both Bicep and Terraform file types are present, explicit configuration is required."; "Docs conflict: The current schema docs state that the default provider is Bicep; they do not document the v1.23.0 file-based auto-detection behavior. The v1.23.0 source is the version-specific evidence for that behavior."

## azd uses Podman when Docker is unavailable (azd, 2026-01-15)
Published 2026-10-19
- slug: azd-uses-podman-when-docker-is-unavailable-1c2ff3ed8af7
- score: 0.97

How to use it:

When running azd container functionality, azd checks Docker first and falls back to Podman. Set `AZD_CONTAINER_RUNTIME` to `podman` or `docker` to choose explicitly.

Examples:

```
azd provision
```

```
AZD_CONTAINER_RUNTIME=podman azd provision
```

```
AZD_CONTAINER_RUNTIME=docker azd provision
```

- why_it_matters: Run azd container functionality in a development environment where Podman is installed and Docker is unavailable.
- before: Previously, azd required Docker for container functionality; without Docker, running `azd provision` failed its external-tool check.
- sources: <https://github.com/Azure/azure-dev/releases/tag/azure-dev-cli_1.23.0>, <https://github.com/Azure/azure-dev/pull/6436>, <https://github.com/Azure/azure-dev/blob/azure-dev-cli_1.23.0/cli/azd/pkg/tools/docker/docker.go>, <https://learn.microsoft.com/en-us/azure/developer/azure-developer-cli/reference>
- gotchas: "Version: 1.23.0"; "AZD_CONTAINER_RUNTIME: Selects the container runtime; documented values are `docker` and `podman`."; "azd provision [<layer>] [flags]: Provisions Azure resources for the project; `<layer>` and flags are optional."; "Prerequisite: The selected runtime must be installed and its service running. Minimum versions: Docker 17.09 or Podman 3.0."; "Docker 17.09+ or Podman 3.0+ is required."; "Cross-platform support applies on platforms where Podman is supported."

## azd env remove deletes local environment configuration files (azd, 2026-01-23)
Published 2026-10-19
- slug: azd-env-remove-deletes-local-environment-configuration-files-f25839544558
- score: 0.96

How to use it:

When you need to remove an azd environment, run `azd env remove <environment>` to remove it. Add `--force` to skip the confirmation prompt.

Examples:

```
azd env remove <environment> [--force]
```

- why_it_matters: Remove a local environment configuration from an azd project.
- sources: <https://github.com/Azure/azure-dev/releases/tag/azure-dev-cli_1.23.1>, <https://learn.microsoft.com/en-us/azure/developer/azure-developer-cli/reference>
- gotchas: "Version: 1.23.1"; "<environment> (required): Name of the environment to remove."; "--force: Skips confirmation before removal."

## azd automatically enables no-prompt mode for detected coding agents (azd, 2026-01-30)
Published 2026-10-19
- slug: azd-automatically-enables-no-prompt-mode-for-detected-coding-agents-6f0fc4a27b23
- score: 0.95

How to use it:

When `azd` detects an AI-agent environment, it enables no-prompt mode automatically. Run the `azd` command you need; pass `--no-prompt` to request no-prompt mode explicitly.

Examples:

```
azd <command> [args...]
```

```
azd <command> [args...] --no-prompt
```

- why_it_matters: When running azd from a supported AI coding agent, automate azd commands without interactive prompts.
- sources: <https://github.com/Azure/azure-dev/releases/tag/azure-dev-cli_1.23.3>, <https://github.com/Azure/azure-dev/pull/6633>, <https://learn.microsoft.com/en-us/azure/developer/azure-developer-cli/reference>
- gotchas: "Version: 1.23.3"; "--no-prompt: Runs without prompts, using existing values; fails if a required value or decision cannot be resolved automatically."; "Detection covers 15+ AI agents, including Claude Code, GitHub Copilot, Cursor, Windsurf, Gemini CLI, Amazon Q, and Aider."; "Detection uses environment variables, `AZURE_DEV_USER_AGENT` parsing, and parent process tree walking."; "Cross-platform support is stated for Windows, Linux, and macOS."; "Docs conflict: The current reference documents `AZD_NON_INTERACTIVE=false` to opt out of automatic no-prompt enablement. The card says to use `--no-prompt=false`; the current documentation does not confirm that override syntax."

## azd CLI JSON output supports JMESPath queries (azd, 2026-02-10)
Published 2026-10-19
- slug: azd-cli-json-output-supports-jmespath-queries-82c64db31fb6
- score: 0.96

How to use it:

When an `azd` command emits JSON, pass a JMESPath expression to `--query` to select fields. The release note documents the flag, but I couldn’t find an official `azd` command example at version 1.23.4.

- why_it_matters: Filter JSON output from an azd CLI command to inspect selected fields.
- sources: <https://github.com/Azure/azure-dev/releases/tag/azure-dev-cli_1.23.4>
- gotchas: "Version: 1.23.4"; "--query <JMESPath expression>: The release note says this flag adds JMESPath query support for JSON output; the exact `azd` syntax and behavior are not documented on a usable official `azd` page I found."

## azd Azure Functions flex consumption apps support remoteBuild (azd, 2026-02-13)
Published 2026-10-19
- slug: azd-azure-functions-flex-consumption-apps-support-remotebuild-ffb4f3f11107
- score: 0.94

How to use it:

For an Azure Functions Flex Consumption app, set `remoteBuild: true` on its service in `azure.yaml` to build the deployment package remotely with Oryx.

Examples:

```
services:
  <service-name>:
    project: <project-path>
    language: <language>
    host: function
    remoteBuild: true
```

- why_it_matters: Configure an Azure Functions flex consumption app to use remote builds.
- sources: <https://github.com/Azure/azure-dev/releases/tag/azure-dev-cli_1.23.5>, <https://learn.microsoft.com/en-us/azure/developer/azure-developer-cli/azd-schema>, <https://github.com/Azure/azure-dev/blob/main/schemas/v1.0/azure.yaml.json>
- gotchas: "Version: 1.23.5"; "services.<service-name>.remoteBuild: Boolean; `true` builds the function deployment package remotely using Oryx; `false` deploys the package as-is. If omitted, defaults to true for JavaScript, TypeScript, and Python function apps."; "services.<service-name>.host (required): Set to `function`; `remoteBuild` is only valid for function services."; "services.<service-name>.project (required): Path to the service source directory; function services using source projects require this instead of `image`."; "Prerequisite: Use azd 1.23.5 or later for the option introduced in that release."; "Applies to Azure Functions flex consumption apps."; "Docs conflict: The current schema reference describes `remoteBuild` as a general remote image build option. The release note and function-specific schema describe it for function app package builds; this answer follows the release note’s function-app context."

## azd provision and azd up accept subscription and location flags (azd, 2026-02-21)
Published 2026-10-19
- slug: azd-provision-and-azd-up-accept-subscription-and-location-flags-ea3643dec664
- score: 0.97

How to use it:

When provisioning or deploying a repository with a specific Azure subscription and location, pass both values to `azd provision` or `azd up`; the flags save them to the environment and skip the selection prompts.

Examples:

```
azd provision --subscription <subscription-id> --location <location>
```

```
azd up --subscription <subscription-id> --location <location>
```

- why_it_matters: Provision or deploy a repository using a specific Azure subscription and location.
- before: Run the command and select a subscription and location at the interactive prompts.
- sources: <https://github.com/Azure/azure-dev/releases/tag/azure-dev-cli_1.23.6>, <https://github.com/Azure/azure-dev/pull/6777>, <https://learn.microsoft.com/en-us/azure/developer/azure-developer-cli/reference>
- gotchas: "Version: 1.23.6"; "--subscription <subscription-id>: Azure subscription ID to use for the environment; the value is saved to that environment."; "--location <location>: Azure location to use for the environment; the value is saved to that environment. Alias: `-l`."; "Prerequisite: Use an `azd` version that includes the flags (introduced in 1.23.6)."; "Prerequisite: Authenticate with Azure and have access to the chosen subscription."

## azd detects pnpm and yarn for JavaScript/TypeScript services (azd, 2026-02-28)
Published 2026-10-19
- slug: azd-detects-pnpm-and-yarn-for-javascript-typescript-services-e6b12d5ac394
- score: 0.92

How to use it:

For JavaScript/TypeScript services using pnpm or yarn, run `azd package` or deploy with `azd deploy` to let azd detect the package manager. To override detection, set `services.<service>.config.packageManager` in `azure.yaml`.

Examples:

```
azd package
```

```
azd deploy
```

```
services:
  <service>:
    language: js # or ts
    config:
      packageManager: pnpm # npm | pnpm | yarn
```

- why_it_matters: Build or deploy a JavaScript/TypeScript service that uses pnpm or yarn.
- sources: <https://github.com/Azure/azure-dev/releases/tag/azure-dev-cli_1.23.7>, <https://learn.microsoft.com/en-us/azure/developer/azure-developer-cli/azd-commands>, <https://learn.microsoft.com/en-us/azure/developer/azure-developer-cli/azd-schema>
- gotchas: "Version: 1.23.7"; "services.<service>.config.packageManager: Package manager used for dependency installation; overrides auto-detection from lock files. Allowed values: `npm`, `pnpm`, `yarn`."; "Prerequisite: Applies to JavaScript/TypeScript services (`js` or `ts`)."; "Applies to JavaScript/TypeScript services."

## azd detects pyproject.toml and installs Python projects (azd, 2026-02-28)
Published 2026-10-19
- slug: azd-detects-pyproject-toml-and-installs-python-projects-7ebaa88de27e
- score: 0.93

How to use it:

If the Python project has `pyproject.toml`, azd detects it and uses `pip install .` when restoring the project for build or deployment. When both `pyproject.toml` and `requirements.txt` exist, `pyproject.toml` takes priority.

Examples:

```
pip install .
```

- why_it_matters: Prepare a Python project with modern packaging for azd build or deployment.
- before: Before this change, azd detected Python projects through `requirements.txt` and restored them with `pip install -r requirements.txt`.
- sources: <https://github.com/Azure/azure-dev/releases/tag/azure-dev-cli_1.23.7>, <https://github.com/Azure/azure-dev/pull/6848>
- gotchas: "Version: 1.23.7"; "Prerequisite: Requires azd 1.23.7 or later for this detection and install support."; "Applies to Python projects using modern project packaging."

## azd init --template supports local directories (azd, 2026-02-28)
Published 2026-10-19
- slug: azd-init-template-supports-local-directories-95f6507db0a1
- score: 0.98

How to use it:

When iterating on a template in a local directory, pass its path to `azd init --template` to initialize from it without pushing it to a remote repository.

Examples:

```
azd init --template <local-directory-path>
```

- why_it_matters: Iterate on a template stored in a local directory without pushing it to a remote repository.
- sources: <https://github.com/Azure/azure-dev/releases/tag/azure-dev-cli_1.23.7>, <https://learn.microsoft.com/en-us/azure/developer/azure-developer-cli/reference>, <https://learn.microsoft.com/en-us/azure/developer/azure-developer-cli/get-started>
- gotchas: "Version: 1.23.7"; "--template, -t <path> (required for this task) (required): Initializes an application from a template; accepts a local directory path, including `./dir`, `../dir`, or an absolute path."; "Prerequisite: Azure Developer CLI (`azd`) installed."; "Docs conflict: Current command reference says `azd init --template` creates a new directory named after the template, with `.` to initialize in the current directory. This behavior may be newer than version 1.23.7; the reference does not state when it changed."

Next: https://sincecutoff.com/v1/changes.md?tool=azd&score=0&cursor=eyJzY29yZSI6MCwic2VxIjoxNDU2LCJzaW5jZSI6bnVsbCwidG9vbCI6ImF6ZCIsInYiOjF9
Save `next_cursor`; next visit, pass it to get only what was published since.
<!-- end of page -->