# Install azure-dev with Homebrew, chocolatey, scoop, winget Developer CLI that provides commands for working with Azure resources. Version 1.29.0 via Homebrew; verified 2026-07-30. Also installable with chocolatey: choco install azd. ## Install ```sh sudo av install brew:azure-dev ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install azure-dev ``` Evidence: local Homebrew formula metadata ### Windows - Chocolatey (92%): ```sh choco install azd ``` Evidence: Chocolatey community package catalog: azd from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='11','authy-desktop' - Scoop (92%): ```sh scoop install extras/azd ``` Evidence: Scoop official bucket manifest trees: bucket/azd.json from https://api.github.com/repos/ScoopInstaller/Extras/git/trees/master?recursive=1 - winget (92%): ```sh winget install --id Microsoft.Azd -e ``` Evidence: Windows Package Manager source index: Microsoft.Azd from https://cdn.winget.microsoft.com/cache/source.msix ## Package facts - **Package key:** brew:azure-dev - **Package manager:** Homebrew - **Version:** 1.29.0 - **Source summary:** Developer CLI that provides commands for working with Azure resources - **Homepage:** - **Repository:** - **Last updated:** 2026-07-30T03:00:39Z - **Generated:** 2026-08-03T19:37:03+00:00 ## Executables - azd (alias) ## Install behavior - Bottle: not available ## Freshness - Page generated: 2026-08-03 - Package-manager version: 1.29.0 ## Project history and usage Azure Developer CLI, invoked as `azd`, is Microsoft's project-oriented Azure application CLI. Where `az` manages Azure resources directly, `azd` packages repeatable app workflows such as init, provision, deploy, pipeline setup, and environment management around `azure.yaml` templates. ### Project history The Azure/azure-dev repository's public release stream starts with `azure-dev-cli_0.1.0-beta.1` in July 2022. Its README describes a developer-centric CLI meant to take code to cloud quickly, with recommended Azure practices and template-driven workflows built in. The tool grew around the `azure.yaml` project file and per-environment `.azure//.env` files. Microsoft Learn documents `azure.yaml` as the configuration file for azd projects and explains that environment variables are stored in environment-specific `.env` files under `.azure`. ### Adoption history `azd` adoption is tied to Azure sample templates, app modernization demos, and teams that want fewer hand-written provisioning commands. The input package facts list Homebrew, Chocolatey, Scoop, and winget packages, showing the tool is aimed at developer workstations as much as CI. Because `azd` is newer than Azure CLI, package-manager adoption is narrower, but the command is important in Azure docs and samples where a repository can become deployable with `azd init` and `azd up`. ### How it is used Common commands are `azd init`, `azd up`, `azd provision`, `azd deploy`, and `azd env set`. The official schema docs describe `azure.yaml` as the file that tells the CLI about services, infrastructure, resources, hooks, and deployment behavior. `azd` does not document a separate long-lived credential file for the CLI itself; it leans on Azure authentication flows and stores project/environment configuration in the project tree. ### Why package nerds care For package nerds, `azure-dev` is interesting because the Homebrew formula name differs from the command name `azd`, and Microsoft's README now points macOS users at a trusted Azure tap/cask flow while package-manager metadata also records community-distribution paths. It is also a good example of a cloud CLI whose real payload is conventions: the executable is small compared with the project template ecosystem, generated environment files, and CI/CD hooks it orchestrates. ### Timeline - 2022: The Azure/azure-dev release stream begins with `azure-dev-cli_0.1.0-beta.1`. - 2020s: Microsoft Learn documents `azure.yaml` and azd environments as the durable project configuration model. - 2020s: Packages appear for Homebrew, Chocolatey, Scoop, and winget. ### Related projects - Azure CLI (`az`) remains the lower-level Azure resource-management CLI. - Bicep and Terraform are supported infrastructure providers in `azure.yaml`. - Azure sample template repositories provide many of the practical starting points for `azd`. ### Sources - Azure/azure-dev README and GitHub Releases - Microsoft Learn Azure Developer CLI docs - source_facts.package-manager ## Security Notes No matching local secret-handling manifest was found for azure-dev. Nucleus package metadata is still published here so future coverage has a stable package URL. ## Configuration and credential file locations These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval. ## Configuration files - Unix: azure.yaml, .azure//.env ## Other Package-Manager Records - Chocolatey - azd: installed executable or alias match | Chocolatey community package catalog: azd from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='11','authy-desktop' - Scoop - extras/azd: installed executable or alias match | Scoop official bucket manifest trees: bucket/azd.json from https://api.github.com/repos/ScoopInstaller/Extras/git/trees/master?recursive=1 - winget - Microsoft.Azd: installed executable or alias match | Windows Package Manager source index: Microsoft.Azd from https://cdn.winget.microsoft.com/cache/source.msix ## Combined YAML source View the package source record on GitHub. [combined/azure-dev.yml](https://github.com/mxcl/pkgdb/blob/main/combined/azure-dev.yml) ## Sources - pkg.so package database - Geiger risk classifier - curated configuration and credential file locations - curated package history - pkgdb category and tag curation - external package-manager database matches - cross-ecosystem install command graph