Namesmith door Molly Grant

Namesmith turns a workload, an environment and a region into consistent Azure resource names and
governance tags. You pick the resource types you are creating, and Namesmith builds a name for
each one that follows the Cloud Adoption Framework pattern, then checks it against that resource
type's real Azure naming rules before you paste it into the portal, an Azure CLI command, or a
Bicep or Terraform file. It runs entirely offline in your browser.

It is built for people who work in Azure day to day: cloud administrators, DevOps and platform
engineers standing up resource groups, storage accounts, key vaults, function apps and virtual
machines, and anyone studying for an Azure certification. The per-resource-type rules are the
part that trips people up, and Namesmith encodes them so you catch a problem before Azure rejects
the name.

What you get:

• A composer for 26 common resource types, each with its Cloud Adoption Framework abbreviation.
• Live validation against each type's real Azure rules: length, character set, case, start and
  end constraints, and global-uniqueness scope, with a plain reason for every issue.
• A governance tag editor with suggested keys.
• One-click export to a name and tag table, an Azure CLI --tags string, a Bicep tags block, a
  Terraform tags block, or JSON.

Privacy, by design:

• Everything you enter stays in your browser. Namesmith makes no network requests and keeps no
  account.
• It asks for a single permission, local storage, used only to save your naming project so it
  survives closing the tab.
• No Azure account, subscription id or secret is requested or stored. The names and tags are
  drafts for you to review, not live Azure state.

Abbreviations follow Microsoft's Cloud Adoption Framework naming recommendation. Namesmith is an
independent tool and is not affiliated with, endorsed by, or sponsored by Microsoft.