wsl az command not found error windows cli not shared 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.

The term 'Get-AzVM' is not recognized as the name of a cmdlet

TL;DR

The Az PowerShell module is not installed (or not loaded) in your session. Install it from the PowerShell Gallery, import it, and the cmdlets appear. Do not confuse this with the az CLI; they are different tools.

The error

The term 'Get-AzVM' is not recognized as the name of a cmdlet, function, script file, or operable program.

Fix it

1. Install the module: Install-Module -Name Az -Scope CurrentUser -Repository PSGallery -Force. Expected: the install completes without errors.
2. Import it: Import-Module Az. Expected: no output, meaning success.
3. Verify: Get-Command Get-AzVM. Expected: it resolves to the Az.Compute cmdlet.
4. Connect: Connect-AzAccount. Expected: interactive login succeeds.
5. Retry your command. Expected: Get-AzVM returns your VMs.

When to use this

• An agent sees "not recognized as the name of a cmdlet" for any Get-Az, New-Az, or Set-Az* command.
• Fresh machines or CI agents running Azure PowerShell for the first time.

When NOT to use this

• "'az' is not recognized". That is the Azure CLI, a separate install.
• AzureRM cmdlets (Get-AzureRmVM). Those are the retired module; migrate to Az.

Compatibility

• PowerShell 5.1 and 7+, Az module (current). AzureRM is retired and should not be installed.

Variant phrasings

• "The term 'Connect-AzAccount' is not recognized"
• Any "not recognized as the name of a cmdlet" for Az.* commands

Root cause

Windows ships no Azure modules. The Az module comes from the PowerShell Gallery, and without it PowerShell has no idea what Get-AzVM is. CI agents and fresh VMs hit this on every first run until the module install becomes part of setup.

Edge cases

• Both AzureRM and Az installed side by side cause conflicts. Uninstall AzureRM.
• Execution policy can block the install. Set-ExecutionPolicy RemoteSigned -Scope CurrentUser first if needed.

The troubleshooting guide at syncluv/azure-mastery-labs (troubleshooting.md) documents the "AzPowerShell module not found" pattern: Azure PowerShell cmdlets like Get-AzVM fail with "not recognized as the name of a cmdlet" when the Az module is missing, with the fix being Install-Module Az followed by Connect-AzAccount. The same guide notes the parallel Azure CLI symptom ("az is not recognized") as a separate PATH problem, confirming these are two distinct tools with distinct fixes.

Not specified by the original author.

TL;DR: Enable WSL integration for that distro: Docker Desktop > Settings > Resources > WSL Integration > toggle your distro on > Apply & Restart. The docker CLI inside WSL comes from Desktop's integration, not from a Linux install; a distro without the toggle has no docker binary at all.

The error

The command 'docker' could not be found in this WSL 2 distro. We recommend to activate the WSL integration in Docker Desktop settings.

Fix it

1. Open Docker Desktop Settings > Resources > WSL Integration.
2. Toggle ON the distro where you want docker.
3. Apply & Restart.

4. In the distro, verify: docker ps Expected: works.

When this applies

• Multiple WSL distros, docker missing in some
• After installing a new distro

When this does NOT apply

• Native Linux (install docker properly there)
• "Cannot connect to the Docker daemon" inside WSL (integration on but Desktop not running)

Versions

Docker Desktop 4.x with WSL2 backend.

Why it happens

Desktop injects the CLI and credentials into each enabled distro via its integration. Distros not toggled get nothing, hence 'command not found' rather than a connection error.

Edge cases

• Do NOT apt install docker-ce inside the WSL distro alongside Desktop integration; the two daemons fight over the socket.
• 'Enable integration with my default WSL distro' covers only the default; extra distros need individual toggles.
• After Windows updates, integration sometimes silently disables; re-toggle fixes it.

Asked: how to fix The command "docker" could not be found in this WSL 2 distro. Verified answer: Fixes 'The command docker could not be found in this WSL 2 distro' when Docker Desktop's WSL integration is off for that distro. Use when docker works in one WSL distro or PowerShell but not another. The fix steps above were cross-checked against the accepted community answer at https://stackoverflow.com/questions/72483632/ubuntu-error-the-command-docker-could-not-be-found-in-this-wsl-2-distro (so:72483632), which confirms the same resolution.