---
title: "Troubleshoot the Anyscale CLI against the Azure control plane"
description: "Configure the Anyscale CLI to target the Azure control plane, including persisting ANYSCALE_HOST on Windows and selecting the right cloud."
---

# Troubleshoot the Anyscale CLI against the Azure control plane

The Anyscale CLI defaults to the AWS control plane. To run commands against Anyscale on Azure, point the CLI at the Azure control plane by setting `ANYSCALE_HOST=https://console.azure.anyscale.com`. The quickstart covers this for Unix shells; this page covers the Windows persistence path and one common multi-cloud edge case.

For background on the export and the quickstart verification flow, see [Verify the deployment](https://learn.microsoft.com/azure/anyscale-on-azure/quickstart-azure-cli-gateway-envoy#verify-the-deployment).

## Persist `ANYSCALE_HOST` on Windows

On Linux and macOS, you add `export ANYSCALE_HOST=https://console.azure.anyscale.com` to your shell profile (`.bashrc`, `.zshrc`, or equivalent). Windows uses a different mechanism. Pick one of the following.

### Set the user environment variable through System Properties

1.  Press **Win + R**, type `sysdm.cpl`, and press Enter.
2.  On the **Advanced** tab, select **Environment Variables**.
3.  Under **User variables**, select **New**.
4.  Set **Variable name** to `ANYSCALE_HOST` and **Variable value** to `https://console.azure.anyscale.com`.
5.  Select **OK** to save. Restart any open terminals so they pick up the new variable.

### Add the export to your PowerShell profile

The PowerShell profile script runs at the start of every PowerShell session. It's the Windows equivalent of `.bashrc` or `.zshrc`. Append the export to it:

```powershell
Add-Content $PROFILE '$env:ANYSCALE_HOST = "https://console.azure.anyscale.com"'
```

Open a new PowerShell session to apply.

## `anyscale job submit` fails with `Cloud not found`

If your Anyscale organization has clouds in multiple control planes or on multiple providers, the CLI doesn't always default to the cloud you intend. Pass `--cloud <name>` explicitly on each command:

```bash
anyscale job submit -f job.yaml --cloud <cloud-name>
```

For a persistent default, set a default cloud in **Organization settings > Clouds** in the Anyscale console. The default applies to commands that don't specify `--cloud` explicitly.

## Related Azure docs

-   [Quickstart: Verify the deployment](https://learn.microsoft.com/azure/anyscale-on-azure/quickstart-azure-cli-gateway-envoy#verify-the-deployment) covers the initial `ANYSCALE_HOST` export and the `anyscale login` flow.
-   [Anyscale CLI reference](/reference/quickstart-cli.md) is the canonical reference for the `--cloud`, `--host`, and authentication flags.

---

Previous: [Troubleshoot Envoy Gateway on Anyscale on Azure](/kb/azure/troubleshoot-envoy-gateway.md) | Next: [Recover a deleted operator extension](/kb/azure/recover-deleted-operator-extension.md)