Event Grid System Topics must use standard naming#
Operational Excellence · Event Grid · Rule · 2025_06 · Awareness
Event Grid system topics without a standard naming convention may be difficult to identify and manage.
Description#
An effective naming convention allows operators to quickly identify resources, related systems, and their purpose. Identifying resources easily is important to improve operational efficiency, reduce the time to respond to incidents, and minimize the risk of human error.
Some of the benefits of using standardized tagging and naming conventions are:
- They provide consistency and clarity for resource identification and discovery across the Azure Portal, CLIs, and APIs.
- They enable filtering and grouping of resources for billing, monitoring, security, and compliance purposes.
- They support resource lifecycle management, such as provisioning, decommissioning, backup, and recovery.
For example, if you come upon a security incident, it's critical to quickly identify affected systems, the functions that those systems support, and the potential business impact.
For Event Grid system topics, the Cloud Adoption Framework (CAF) recommends using the egst-
prefix.
Requirements for Event Grid system topic names:
- At least 3 character, but no more than 50.
- Can include alphanumeric, and hyphen characters.
- Event Grid system topics must be unique within a resource group.
Recommendation#
Consider creating Event Grid system topics with a standard name. Additionally consider using Azure Policy to only permit creation using a standard naming convention.
Examples#
Configure with Bicep#
To deploy Event Grid topics that pass this rule:
- Set the
name
property to a string that matches the naming requirements. - Optionally, consider constraining name parameters with
minLength
andmaxLength
attributes.
For example:
@minLength(3)
@maxLength(50)
@description('The name of the resource.')
param name string
@description('The location resources will be deployed.')
param location string = resourceGroup().location
resource systemTopic 'Microsoft.EventGrid/systemTopics@2025-02-15' = {
name: name
location: location
identity: {
type: 'SystemAssigned'
}
properties: {
source: storageId
topicType: 'Microsoft.Storage.StorageAccounts'
}
}
Configure with Azure Verified Modules
A pre-validated module supported by Microsoft is available from the Azure Bicep public registry. To reference the module, please use the following syntax:
To use the latest version:
Configure with Azure template#
To deploy Event Grid topics that pass this rule:
- Set the
name
property to a string that matches the naming requirements. - Optionally, consider constraining name parameters with
minLength
andmaxLength
attributes.
For example:
{
"$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
"contentVersion": "1.0.0.0",
"metadata": {
"_generator": {
"name": "bicep",
"version": "0.34.44.8038",
"templateHash": "2337278938882386088"
}
},
"parameters": {
"name": {
"type": "string",
"minLength": 3,
"maxLength": 50,
"metadata": {
"description": "The name of the resource."
}
},
"location": {
"type": "string",
"defaultValue": "[resourceGroup().location]",
"metadata": {
"description": "The location resources will be deployed."
}
},
"storageId": {
"type": "string",
"metadata": {
"description": "The resource ID of the storage account."
}
}
},
"resources": [
{
"type": "Microsoft.EventGrid/systemTopics",
"apiVersion": "2025-02-15",
"name": "[parameters('name')]",
"location": "[parameters('location')]",
"identity": {
"type": "SystemAssigned"
},
"properties": {
"source": "[parameters('storageId')]",
"topicType": "Microsoft.Storage.StorageAccounts"
}
}
]
}
Notes#
This rule does not check if Event Grid system topic names are unique.
Rule configuration#
AZURE_EVENTGRID_SYSTEM_TOPIC_NAME_FORMAT
To configure this rule set the AZURE_EVENTGRID_SYSTEM_TOPIC_NAME_FORMAT
configuration value to a regular expression
that matches the required format.
For example:
Links#
- OE:04 Tools and processes
- Recommended abbreviations for Azure resource types
- Naming rules and restrictions for Azure resources
- Define your naming convention
- Azure deployment reference