From Homebrew Core to a new installation model for macOS
Over the past few years, Azure CLI usage on macOS has continued to grow—across individual developers, open source contributors, and large enterprises. As adoption increases, so do expectations around security, reliability, and enterprise readiness.
Starting with Azure CLI 2.86.0, we are beginning an important evolution of the macOS experience by introducing new installation options, initially available as Preview:
- Homebrew Cask (recommended)
- Offline / air-gapped tarball (.tar.gz)
This post explains why these changes are necessary, what is different from before, and how we recommend customers think about the transition. Detailed installation and usage steps are documented on Microsoft Learn.
Why are we changing how Azure CLI is installed on macOS?
Historically, Azure CLI on macOS has been distributed via Homebrew Core. This model has worked well for many years, especially for developer-focused, source-based tooling. However, as macOS and enterprise security requirements continue to evolve, this distribution model introduces real technical and compliance constraints.
To support future enterprise-grade security scenarios on macOS, Azure CLI must be able to rely on:
- Precompiled, verified binaries
- Code signing and notarization requirements enforced by macOS
These requirements represent a fundamental shift from how Homebrew Core is designed to operate.
Why Homebrew Core is no longer sufficient
Homebrew Core is optimized for source-driven and fully open-source software distribution. Formulae in Homebrew Core are typically built from source or rely on build processes that are fully transparent and reproducible within the Homebrew ecosystem.
As Azure CLI evolves, this model is no longer sufficient for several reasons:
- Future macOS authentication capabilities depend on platform-level components, not just Python code. These components integrate with the macOS Keychain and system-level security features.
- Such components must be distributed as precompiled binaries, rather than built from source during installation.
- On macOS, these binaries must be cryptographically signed and notarized to meet security and compliance requirements.
Because of these constraints, continuing to rely solely on Homebrew Core would limit Azure CLI’s ability to support important enterprise scenarios on macOS going forward.
Why Homebrew Cask
Homebrew Cask is designed to distribute prebuilt, signed software on macOS. It provides a packaging model that aligns with modern macOS security expectations while preserving a familiar Homebrew experience.
By moving to Homebrew Cask, Azure CLI can:
- Ship precompiled, signed artifacts
- Better align with evolving macOS security requirements
- Enable future support for more secure authentication scenarios on macOS, such as broker-based authentication
This change is about establishing a durable installation foundation, not forcing changes to users’ current authentication experience.
New installation options in Azure CLI 2.86.0 (Preview)
Starting with Azure CLI 2.86.0, we are introducing two new installation options on macOS, both initially available in Preview.
Homebrew Cask (recommended)
Homebrew Cask is the recommended installation path moving forward. It provides:
- A familiar Homebrew-based workflow
- A self-contained, prebuilt bundle
- A distribution model aligned with evolving macOS security requirements
During the Preview period, Homebrew Core remains available.
We recommend users explore and adopt Homebrew Cask where appropriate and share feedback during this phase.
Offline / air-gapped tarball
For environments where Homebrew is not available or permitted—such as restricted or air-gapped enterprise environments—we are also introducing an offline tarball installation option.
This option:
- Uses the same Azure CLI artifact as Homebrew Cask
- Supports both Apple Silicon and Intel Macs
- Allows full control over installation paths and Python runtimes
The difference between these two options lies in how the same artifact is installed and managed, not in Azure CLI functionality.
Preview now, GA later
Both installation options are currently in Preview as part of Azure CLI 2.86.0.
During this phase, we are focused on:
- Collecting feedback from real-world usage
- Validating behavior across macOS versions and architectures
- Identifying and addressing issues before broader rollout
The timeline for General Availability is not finalized. We will communicate clearly with customers ahead of any GA transition or required changes.
How we recommend customers proceed
We recommend customers start adopting the new installation options during the Preview phase.
Homebrew Cask is expected to become the standard installation model for Azure CLI on macOS. Adopting it early helps ensure a smoother transition as we move toward that model.
During Preview, we encourage users to try the new experience and share feedback to help us refine it before broader rollout.
Detailed installation and configuration steps are available on Install Azure CLI on macOS - Preview | Microsoft Learn
Microsoft