Skip to main content

Apply effective naming conventions in Azure using the Azure Naming Tool

Everyone who works in software development knows this: naming things is hard. And when you need to create a lot of resources in Azure, naming things there can even be harder. If you recognize this struggle, I have some good news for you. With the help of the Azure Naming Tool, applying a good and consistent naming strategy becomes a lot easier.

Why naming conventions matter

  • Consistency and Clarity: Consistent naming conventions provide clarity, making it easier for team members to understand the purpose and function of each resource. This reduces confusion and enhances productivity.
  • Simplified Management: A structured naming convention simplifies resource management by grouping related resources together and enabling straightforward identification. This is particularly useful in large-scale environments where numerous resources are deployed.

  • Enhanced Security and Compliance: Proper naming conventions can help ensure compliance with security policies and regulatory requirements. By incorporating specific identifiers, such as environment and region, you can better manage access controls and audit trails.

  • Improved Automation: Automation tools often rely on consistent naming conventions to perform tasks efficiently. With clear and predictable names, automation scripts can easily identify and manage resources, reducing the risk of errors.

Introducing the Azure Naming tool

There is a lot of documentation out there to help you with a good naming strategy for your Azure resources. But instead of reading through all this information, let’s use the Azure Naming tool instead.

The Azure Naming Tool was created to help administrators define and manage their naming conventions, while providing a simple interface for users to generate a compliant name. The tool was developed using a naming pattern based on Microsoft's best practices. Once an administrator has defined the organizational components, users can use the tool to generate a name for the desired Azure resource.

The easiest way to get the tool up and running is through docker:

  • Go to the latest release and download the AzureNamingTool.zip.
  • Extract the zip file and build the docker image locally:
docker build -t azurenamingtool .
  • Now you can run the image using the following command:
docker run -d -p 9000:80 --mount source=azurenamingtoolvol,target=/app/settings azurenamingtool:latest
  • Go to http://localhost:9000 to access the tool.
    • Remark: The first time you do this, you need create an admin account.

 


    • The first thing we need to do is set some basic configuration. Go to the Admin section and login with the chosen password:

     

    • Now we can go to the Configuration section and add a new organization:

     

    • Let’s also add a new application:

     

    • There is a lot more we can configure. Certainly check out the other sections. But we’ll move on to the Generate section to generate a name for a specific resource.

     

    • First we need to specify a Generation Mode. In this case we only want to generate a name for a single resource. So we can leave the Generate Single Resource Type Name selected.

     

    • Next step is to select the desired resource type; filter the categories first and then you can select the specific resource:

     

    • Now we need to select a few things:
      • An (optional) unit or department
      • A project
      • An environment
      • A location
      • An instance

     

    • If we now click on the Generate button at the bottom a name is generated taking into account the naming conventions for the specific resource and the configured information:

     

    • The generated name is stored inside the tool and can be accessed later through the Generated Names Log section.

     

      Also check out the following video to get more details:

      More information

      Abbreviation recommendations for Azure resources - Cloud Adoption Framework | Microsoft Learn

      Define your naming convention - Cloud Adoption Framework | Microsoft Learn

      Develop your naming and tagging strategy for Azure resources - Cloud Adoption Framework | Microsoft Learn

      Home · mspnp/AzureNamingTool Wiki

      mspnp/AzureNamingTool: The Azure Naming Tool is a .NET 8 Blazor application, with a RESTful API. The UI consists of several pages to allow the configuration and generation of Azure Resource names. The API provides a programmatic interface for the functionality.

      Deep Diving into the Azure Naming Tool - Soltisweb

      Popular posts from this blog

      Podman– Command execution failed with exit code 125

      After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

      Cache stampede: when our cache turned against us

      While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...

      A complex system designed from scratch never works

      A few years ago, I worked as an architect on a big mainframe rewrite. I still count it as one of my failures. Not because the technology was wrong, but because I couldn't convince the management team to simplify the approach. Years later, the organization is still struggling to get the new system up and running. I left the project at the time, because I couldn't put my name behind an approach that would take very long and cost a lot of money without a working system to show for it along the way. Gall’s Law That memory keeps coming back to me, because it's a textbook case of Gall's Law playing out in real life. Gall's Law , from John Gall's Systemantics , states it plainly: A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works, and it cannot be patched to make it work. You have to start over with a simple system that works. What does that mean in practice,...