Loading...

Resource naming reloaded: Azure Policy and Bicep for the winner!

Resource naming reloaded: Azure Policy and Bicep for the winner!

Let’s solidify naming conventions with Azure Policy

In one of my last blog posts, How to use Azure Policy to enforce resource naming conventions in your DevOps pipelines I explained how one could leverage Azure Policy to standardize naming of your Azure resources. But it would be too easy, if it was that easy. We have a few issues with that:

  • some resources can’t handle the pattern that Microsoft suggests - for example Storage Accounts can only have lowercase letters and numbers in the name and only up to 24 characters
  • if we want people to stick to a certain pattern it’s easier if they can choose from a list of valid values

So we will parameterize the resource name with in Organization Unit, the appName that the requester provides us with, the location, the appType, the environment and the instance. This is how that looks like in Bicep:

param orgUnit string = 'Contoso' // Organization Unit
param appName string // Name provided by the requester
@allowed([
'weu' // Short name for West Europe
'eus' // Short name for East US
])
param shortLocation string // Selectable location for naming purposes
@allowed([
'storageaccount'
'webapp'
'functionapp'
'logicapp'
'sqlserver'
'cosmosdb'
])
param appType string // Selectable app type from a predefined array
@allowed([
'Dev'
'Demo'
'Test'
'Prod'
])
param environment string // Environment (e.g., 'Prod', 'Dev', etc.)
@allowed([
'01', '02', '03', '04', '05'
])
param instanceNumber string // Instance number or other identifier
// Mapping for short location codes to full Azure region names
var locationMapping = {
weu: 'westeurope'
eus: 'eastus'
}
// Get the full Azure location name for deployment
var fullLocation = locationMapping[shortLocation]
// Base resource name using short location code
var baseResourceName = '${orgUnit}-${appName}-${shortLocation}-${appType}-${environment}-${instanceNumber}'
// Exception for storage account
var storageAccountName = toLower('${appName}${environment}${instanceNumber}')
var truncatedStorageAccountName = length(storageAccountName) > 24 ? substring(storageAccountName, 0, 24) : storageAccountName
// Final resource name with exception handling
var resourceName = appType == 'storageaccount' ? truncatedStorageAccountName : baseResourceName
// Resource declaration for an Azure Storage Account
resource storageAccount 'Microsoft.Storage/storageAccounts@2021-04-01' = if (appType == 'storageaccount') {
name: resourceName
location: fullLocation // Use full location name for deployment
sku: {
name: 'Standard_LRS'
}
kind: 'StorageV2'
}
// Resource declaration for an Azure Web App
resource webApp 'Microsoft.Web/sites@2021-02-01' = if (appType == 'webapp') {
name: resourceName
location: fullLocation // Use full location name for deployment
kind: 'app'
properties: {
serverFarmId: 'your-app-service-plan-id'
}
}
// Resource declaration for an Azure Function App
resource functionApp 'Microsoft.Web/sites@2021-02-01' = if (appType == 'functionapp') {
name: resourceName
location: fullLocation // Use full location name for deployment
kind: 'functionapp'
properties: {
serverFarmId: 'your-app-service-plan-id'
}
}
// Resource declaration for an Azure Logic App
resource logicApp 'Microsoft.Logic/workflows@2019-05-01' = if (appType == 'logicapp') {
name: resourceName
location: fullLocation // Use full location name for deployment
properties: {
definition: {
'$schema': 'https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json#'
actions: {}
contentVersion: '1.0.0.0'
outputs: {}
parameters: {}
triggers: {}
}
parameters: {} // Add your logic app parameters here
}
}
// Resource declaration for an Azure SQL Server
resource sqlServer 'Microsoft.Sql/servers@2021-05-01-preview' = if (appType == 'sqlserver') {
name: resourceName
location: fullLocation // Use full location name for deployment
properties: {
administratorLogin: 'your-admin-login'
administratorLoginPassword: 'your-admin-password'
}
}
// Resource declaration for an Azure Cosmos DB Account
resource cosmosDb 'Microsoft.DocumentDB/databaseAccounts@2021-04-15' = if (appType == 'cosmosdb') {
name: resourceName
location: fullLocation // Use full location name for deployment
kind: 'GlobalDocumentDB'
properties: {
databaseAccountOfferType: 'Standard'
locations:fullLocation
}
}
// Output the generated resource name and location for verification
output resourceName string = resourceName
output fullLocation string = fullLocation

Save this as main.bicep, We can now deploy this using Azure CLI:

$resourceGroup = "<your resourcegroup>"
az deployment group create --resource-group $resourceGroup --template-file main.bicep

As a result, we get nicely named resources:

Logic app in Azure Portal

In a future blog post, let’s make this work in Azure DevOps :-)

Published on:

Learn more
Luise Freese: Consultant & MVP
Luise Freese: Consultant & MVP

Recent content on Luise Freese: Consultant & MVP

Share post:

Related posts

Accelerate Your Growth: Azure Cosmos DB Partner Acceleration Program

Accelerate Your Growth: Azure Cosmos DB Partner Acceleration Program Unlock 360° Success with the Cosmos DB Engineering Team Are you ready to ...

11 hours ago

Transforming Field Operations with AI, Azure Maps & Dynamics 365

Efficient field operations are the backbone of successful, data-driven organizations. Yet, many businesses continue to struggle with scattered...

2 days ago

Failures Happen in Cloud, but how Azure Cosmos DB keeps your Applications Online

The only thing that’s constant in distributed systems is failures. No cloud platform is immune to failures — from regional outages and transie...

4 days ago

The `azd` extension to configure GitHub Copilot coding agent integration with Azure

This post shares how to set up the GitHub Copilot coding agent integration with Azure resources and services by using the Azure Developer CLI ...

4 days ago

Announcing Azure MCP Server 1.0.0 Stable Release – A New Era for Agentic Workflows

Today marks a major milestone for agentic development on Azure: the stable release of the Azure MCP Server 1.0! The post Announcing Azure MCP ...

6 days ago

From Backup to Discovery: Veeam’s Search Engine Powered by Azure Cosmos DB

This article was co-authored by Zack Rossman, Staff Software Engineer, Veeam; Ashlie Martinez, Staff Software Engineer, Veeam; and James Nguye...

6 days ago

Azure SDK Release (October 2025)

Azure SDK releases every month. In this post, you'll find this month's highlights and release notes. The post Azure SDK Release (October 2025)...

7 days ago

Microsoft Copilot (Microsoft 365): [Copilot Extensibility] No-Code Publishing for Azure AI Foundry Agents to Microsoft 365 Copilot Agent Store

Developers can now publish Azure AI Foundry Agents directly to the Microsoft 365 Copilot Agent Store with a simplified, no-code experience. Pr...

7 days ago

Azure Marketplace and AppSource: A Unified AI Apps and Agents Marketplace

The Microsoft AI Apps and Agents Marketplace is set to transform how businesses discover, purchase, and deploy AI-powered solutions. This new ...

10 days ago
Stay up to date with latest Microsoft Dynamics 365 and Power Platform news!
* Yes, I agree to the privacy policy