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:

In a future blog post, let’s make this work in Azure DevOps :-)
Published on:
Learn moreRelated posts
Powering Real-Time Gaming Experiences with Azure Cosmos DB for NoSQL
Scenario: When Every Millisecond Counts in Gaming Imagine millions of players logging in at the exact moment a new game season launches. Leade...
Access Azure Virtual Desktop and Windows 365 Cloud PC from non-managed devices
Check out this article via web browser: Access Azure Virtual Desktop and Windows 365 Cloud PC from non-managed devices Many organizations use ...
Power Pages + Azure AD B2C: “The Provided Application Is Not Valid” Error
If you are new to configuring Azure AD B2C as Identity Provider in Power Pages, refer Power Pages : Set up Azure AD B2C After completing the s...
Semantic Reranking with Azure SQL, SQL Server 2025 and Cohere Rerank models
Supporting re‑ranking has been one of the most common requests lately. While not always essential, it can be a valuable addition to a solution...
How Azure Cosmos DB Powers ARM’s Federated Future: Scaling for the Next Billion Requests
The Cloud at Hyperscale: ARM’s Mission and Growth Azure Resource Manager (ARM) is the backbone of Azure’s resource provisioning and management...
Automating Business PDFs Using Azure Document Intelligence and Power Automate
In today’s data-driven enterprises, critical business information often arrives in the form of PDFs—bank statements, invoices, policy document...
Azure Developer CLI (azd) Dec 2025 – Extensions Enhancements, Foundry Rebranding, and Azure Pipelines Improvements
This post announces the December release of the Azure Developer CLI (`azd`). The post Azure Developer CLI (azd) Dec 2025 – Extensions En...