**TL;DR:** Symptom: StorageAccountAlreadyTaken: the storage account name is already in use Cause: Storage account names are globally unique across all of Azure. The name you want belongs to someone else (or to a soft-deleted account of yours). CONFIRM IT CONFIRM: az storage account check-name --name [name] returns reason AlreadyExists. FIX FIX: pick a different name (add a short org/region suffix).

## The error

```text
StorageAccountAlreadyTaken: the storage account name is already in use Cause: Storage account names are globally unique across all of Azure. The name you want belongs to someone else (or to a soft-deleted account of yours). CONFIRM IT CONFIRM: az storage account check-name --name [name] returns reas
```

## The fix

**TL;DR:** Symptom: StorageAccountAlreadyTaken: the storage account name is already in use Cause: Storage account names are globally unique across all of Azure. The name you want belongs to someone else (or to a soft-deleted account of yours). CONFIRM IT CONFIRM: az storage account check-name --name [name] returns reason AlreadyExists. FIX FIX: pick a different name (add a short org/region suffix).

## The fix

SYMPTOM
StorageAccountAlreadyTaken: the storage account name is already in use

CAUSE
Storage account names are globally unique across all of Azure. The name you want belongs to someone else (or to a soft-deleted account of yours). There is no override.

CONFIRM IT
CONFIRM: `az storage account check-name --name [name]` returns reason AlreadyExists.

FIX
FIX: pick a different name (add a short org/region suffix). If it was YOUR recently deleted account and name reuse matters, check whether soft-delete retention still holds it; otherwise move on - the name may be unrecoverable.

VERIFY
VERIFY: `az storage account check-name` returns NameAvailable, then create.

## When to use this

- This covers exactly what the title says: Diagnose.
- You are setting this up for the first time, or auditing an existing setup.
- You want the key gotchas in one place before you start.

## When not to use this

- You are doing a different workflow with Diagnose; these steps are specific to the title above.
- You need the full reference docs; this is the short path, not the manual.

## Compatibility

- Not pinned to a specific version; follows current Diagnose behavior.