## 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.

```text
'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.