az command missing on mac error brew install path broken fails

Not specified by the original author.

TL;DR

az is not recognized as an internal or external command means Windows cannot find the Azure CLI executable: the CLI installed but its folder is not on PATH, or the install did not finish. Reinstall from the official MSI with the add to PATH option checked, or add the install folder to PATH manually, then open a fresh terminal and verify with az version. A terminal opened before the fix will never see the new PATH.

'az' is not recognized as an internal or external command,
operable program or batch file.

Use this when

• cmd prints az is not recognized as an internal or external command, operable program or batch file
• PowerShell prints the term az is not recognized as the name of a cmdlet
• This happens right after installing the Azure CLI on Windows, or in a terminal that was open during the install

Not for this skill when

• az runs but az login fails. The CLI is found there; authentication is the problem, see the related application id skill below
• You are inside Azure Cloud Shell. Cloud Shell always has the CLI; a not recognized message there is a different issue

Steps

1. Check whether the CLI is actually installed. Look for Azure CLI in Add or remove programs, and for its folder under Program Files.

Expected: you know whether this is a missing install (go to step 3) or a PATH problem (go to step 2).

2. If it is installed, add its folder to PATH. Add the Azure CLI bin folder to the system PATH in Environment Variables, then close the terminal completely and open a new one.

Expected: az version prints version info in the fresh terminal.

3. If it is not installed, or the folder is missing, reinstall from the official MSI and keep the add to PATH option checked.

Expected: the installer completes, and a fresh terminal finds az.

4. In PowerShell, confirm the shell resolves it: Get-Command az.

Expected: it resolves to the CLI executable path instead of an error.

5. Verify the install end to end: az version.

Expected: JSON output with the Azure CLI version. Only now try az login or your original command.

Variant phrasings

az not recognized windows

The short version of the same report. It is the PATH problem in step 2 nine times out of ten; do the fresh-terminal check before reinstalling.

the term az is not recognized as the name of a cmdlet

The PowerShell wording of the identical failure. PowerShell and cmd read the same PATH, so the fix is the same: folder on PATH, fresh terminal, Get-Command az to confirm.

az login not recognized

az login never gets to run because the shell cannot find az at all. Fix PATH first (steps 1 to 5); login errors only become visible after az version works.

Root cause

The MSI installer optionally adds the CLI folder to PATH. Unchecking that option, an install that did not finish, or a terminal opened before the install leaves az unresolvable. The step everyone skips is opening a fresh terminal: already-open shells keep the old PATH forever.

Edge cases

• 32-bit and 64-bit installs land in different Program Files folders. Point PATH at the one that actually exists on disk.
• Corporate images sometimes block the MSI PATH change. Set PATH manually in System environment variables instead.
• Multiple Python-based CLI installs can shadow each other. Get-Command az shows which executable the shell actually resolved.

Tool compatibility

Azure CLI on Windows (MSI install), in cmd and PowerShell. The PATH principle is the same for winget installs; the folder location differs.

Related skills

• Please run az login to setup account - the next failure after az is found but not signed in: https://vectle.com/skills/skl_7aKi9fDg6cP5dqjxQPgTHA
• application id not found (AADSTS700016), which az login can hit once the CLI runs: https://vectle.com/skills/skl_A8TLFys-hrvLfD1hrxFnDg
• azure identity not found: https://vectle.com/skills/skl_O0wm7fdvw17HY02tjklDMw

Provenance

Built from the hatchjs.com Q and A on this exact error, linked in the evidence.

The hatchjs.com Q&A ("az is not recognized as an internal or external command") and the kthw-powershell execution troubleshooting notes document this exact failure: after installing the Azure CLI on Windows, the shell cannot find az because the install folder is not on PATH. The confirmed fix is reinstalling with PATH registration or adding the install folder to PATH manually, then opening a fresh terminal session so the new PATH takes effect.

Not specified by the original author.

TL;DR

The maintainer fixed the formula and confirmed the fix in v3.5.1. The reporter confirmed the fault and the fix landed in 3.5.1.

Steps

1. Following the Crunchy Bridge quickstart on an arm64 Macintosh, the brew-installed cb binary crashed with an invalid instruction error. Running file on the binary showed it was actually an x64 build, so brew was handing out the wrong architecture on Apple Silicon. The thread closed May 2024 with the official fix.
2. brew was shipping the x64 cb binary on arm64 Macs, which then crashed with an invalid instruction. The maintainer fixed the formula and confirmed the fix in v3.5.1. If you still have a broken install, just reinstall: brew reinstall CrunchyData/brew/cb and check with file $(which cb) that you get an arm64 binary. The reporter confirmed the fault and the fix landed in 3.5.1.
3. The thread above nails the cause, so the fix addresses that directly rather than symptoms. Adapt the version numbers and paths to your setup, then verify the behavior the thread confirmed.

When to use

You are seeing this: Running file on the binary showed it was actually an x64 build, so brew was handing out the wrong architecture on Apple Silicon. Use this skill when you run into "Does brew install get an arm64 binary of cb on Mac? (x64 binary crashes)".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: v3.5.1, 3.5.1. If you are on something much newer or older, the details may have shifted.

Why this happens

The thread above nails the cause, so the fix addresses that directly rather than symptoms.

Sources

• https://github.com/CrunchyData/bridge-cli/issues/157

Asked in the thread (https://vectle.com/threads/thrW5aMyc0Vf5lP7L9feYBxQ): Following the Crunchy Bridge quickstart on an arm64 Macintosh, the brew-installed cb binary crashed with an invalid instruction error. Running file on the binary showed it was actually an x64 build, so brew was handing out the wrong architecture on Apple Silicon. The thread closed May 2024 with the official fix. Verified resolution: brew was shipping the x64 cb binary on arm64 Macs, which then crashed with an invalid instruction. The maintainer fixed the formula and confirmed the fix in v3.5.1. If you still have a broken install, just reinstall: brew reinstall CrunchyData/brew/cb and check with file $(which cb) that you get an arm64 binary. The reporter confirmed the fault and the fix landed in 3.5.1. Source: https://github.com/CrunchyData/bridge-cli/issues/157

Not specified by the original author.

TL;DR

Fixed in CLI v0.13.1: upgrade and log in again. Installed cli via homebrew as per the README.md: brew install axiomhq/tap/axiom Tried to authenticate: axiom auth login I logged in, in the browser.

Steps

1. Issue axiomhq/cli#250 (closed, 5 comments): 👋 Hello friends. Given #230 is closed and about the go version, I decided to create a new issue rather than necro the old one. But I suspect it's the same or similar issue. Installed cli via homebrew as per the README.md: brew install axiomhq/tap/axiom Tried to authenticate: axiom auth login I logged in, in the browser.
2. [lukasmalkmus (collaborator)]: axiom auth login failing with API error 404 was a regression from the new API backend rollout. Fixed in CLI v0.13.1: upgrade and log in again.

When to use

You are seeing this: Issue axiomhq/cli#250 (closed, 5 comments): 👋 Hello friends. Use this skill when you run into "brew cli client cannot auth".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: CLI v0.13.1. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Sources

• https://github.com/axiomhq/cli/issues/250

In https://github.com/axiomhq/cli/issues/250, the reporter asked: Issue axiomhq/cli#250 (closed, 5 comments): 👋 Hello friends. Given #230 is closed and about the go version, I decided to create a new issue rather than necro the old one. But I suspect it's the same or similar issue. Installed cli via homebrew as per the README.md: brew install axiomhq/tap/axiom Tried to authenticate: axiom auth login I logged in, in the browser. The verified answer: [lukasmalkmus (collaborator)]: axiom auth login failing with API error 404 was a regression from the new API backend rollout. Fixed in CLI v0.13.1: upgrade and log in again. Source thread: https://github.com/axiomhq/cli/issues/250