Container App Job resources must use standard naming
November 27, 2025 ยท View on GitHub
SYNOPSIS
Container App Job resources 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 Container App Job, the Cloud Adoption Framework (CAF) recommends using the caj- prefix.
Requirements for Container App Job resource names:
- Between 2 and 32 characters long.
- Lowercase letters, numbers, and hyphens.
- Start with letter and end with alphanumeric.
- Can not contain consecutive hyphens.
RECOMMENDATION
Consider creating Container App Job resources with a standard name. Additionally consider using Azure Policy to only permit creation using a standard naming convention.
EXAMPLES
Configure with Bicep
To deploy resources that pass this rule:
- Set the
nameproperty to a string that matches the naming requirements. - Optionally, consider constraining name parameters with
minLengthandmaxLengthattributes.
For example:
@minLength(2)
@maxLength(32)
@description('The name of the resource.')
param name string
@description('The location resources will be deployed.')
param location string = resourceGroup().location
resource job 'Microsoft.App/jobs@2025-01-01' = {
name: name
location: location
identity: {
type: 'SystemAssigned'
}
properties: {
environmentId: containerEnv.id
template: {
containers: containers
}
workloadProfileName: workloadProfileName
configuration: {
replicaTimeout: 300
triggerType: 'Manual'
manualTriggerConfig: {}
}
}
}
Configure with Azure template
To deploy resources that pass this rule:
- Set the
nameproperty to a string that matches the naming requirements. - Optionally, consider constraining name parameters with
minLengthandmaxLengthattributes.
For example:
{
"$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
"contentVersion": "1.0.0.0",
"parameters": {
"name": {
"type": "string",
"minLength": 2,
"maxLength": 32,
"metadata": {
"description": "The name of the resource."
}
},
"location": {
"type": "string",
"defaultValue": "[resourceGroup().location]",
"metadata": {
"description": "The location resources will be deployed."
}
}
},
"resources": [
{
"type": "Microsoft.App/jobs",
"apiVersion": "2025-01-01",
"name": "[parameters('name')]",
"location": "[parameters('location')]",
"identity": {
"type": "SystemAssigned"
},
"properties": {
"environmentId": "[resourceId('Microsoft.App/managedEnvironments', parameters('name'))]",
"template": {
"containers": "[variables('containers')]"
},
"workloadProfileName": "[parameters('workloadProfileName')]",
"configuration": {
"replicaTimeout": 300,
"triggerType": "Manual",
"manualTriggerConfig": {}
}
}
}
]
}
NOTES
This rule does not check if Container App Job resource names are unique.
Rule configuration
To configure this rule set the AZURE_CONTAINER_APP_JOB_NAME_FORMAT configuration value to a regular expression
that matches the required format.
For example:
configuration:
AZURE_CONTAINER_APP_JOB_NAME_FORMAT: '^caj-'