<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Tushar Verma</title>
    <description>The latest articles on DEV Community by Tushar Verma (@tusharrverma).</description>
    <link>https://dev.to/tusharrverma</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4019434%2F5917267a-45a1-4c95-b694-6d6719157c0a.JPG</url>
      <title>DEV Community: Tushar Verma</title>
      <link>https://dev.to/tusharrverma</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/tusharrverma"/>
    <language>en</language>
    <item>
      <title>I built a free Azure naming tool that knows every resource type's rules</title>
      <dc:creator>Tushar Verma</dc:creator>
      <pubDate>Tue, 07 Jul 2026 11:40:00 +0000</pubDate>
      <link>https://dev.to/tusharrverma/i-built-a-free-azure-naming-tool-that-knows-every-resource-types-rules-23kf</link>
      <guid>https://dev.to/tusharrverma/i-built-a-free-azure-naming-tool-that-knows-every-resource-types-rules-23kf</guid>
      <description>&lt;p&gt;Every Azure team needs a naming convention, and Microsoft's Cloud Adoption Framework defines a good one. The annoying part is that the rules are scattered and every resource type is different. Storage accounts: 3 to 24 characters, lowercase, no hyphens, globally unique. Key Vault: 24 characters, and soft delete reserves a deleted vault's name for 90 days. Container registries: alphanumeric only.&lt;/p&gt;

&lt;p&gt;I got tired of cross-referencing the docs and still hitting name errors at deploy time, so I put together AzureNamer.&lt;/p&gt;

&lt;p&gt;What it does:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Generates CAF compliant names for 204 resource types, each with its real length and character rules applied&lt;/li&gt;
&lt;li&gt;Exports the whole set as Terraform, Bicep, JSON, Markdown or CSV&lt;/li&gt;
&lt;li&gt;The Terraform and Bicep exports have a parameterized mode: variable blocks plus derived name expressions, so one file produces correct names for dev, staging and prod. Names the engine had to shorten stay literal with a comment instead of silently drifting&lt;/li&gt;
&lt;li&gt;Parses an existing name back into its components (type, workload, environment, region)&lt;/li&gt;
&lt;li&gt;Includes a naming rules reference page for every resource type and a searchable CAF abbreviations cheat sheet&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It's free, no login, and fully static, so your inputs never leave the browser.&lt;/p&gt;

&lt;p&gt;It started as a side project to scratch my own itch, so feedback is genuinely welcome, especially wrong abbreviations or missing resource types. Hope it saves someone a 2am deploy failure over a name that's one character too long.&lt;/p&gt;

&lt;p&gt;Try it: &lt;a href="https://azurenamingconventions.com" rel="noopener noreferrer"&gt;https://azurenamingconventions.com&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;If you want the background on the CAF standard itself, I wrote a full guide: &lt;a href="https://azurenamingconventions.com/blog/azure-naming-conventions-complete-guide/" rel="noopener noreferrer"&gt;https://azurenamingconventions.com/blog/azure-naming-conventions-complete-guide/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>azure</category>
      <category>devops</category>
      <category>terraform</category>
      <category>cloud</category>
    </item>
  </channel>
</rss>
