Use valid VNET names#
Operational Excellence · Virtual Network · Rule · 2020_06 · Awareness
Virtual Network (VNET) names should meet naming requirements.
Description#
When naming Azure resources, resource names must meet service requirements. The requirements for Virtual Network names are:
- Between 2 and 64 characters long.
- Alphanumerics, underscores, periods, and hyphens.
- Start with alphanumeric.
- End alphanumeric or underscore.
- VNET names must be unique within a resource group.
Recommendation#
Consider using names that meet Virtual Network naming requirements. Additionally consider naming resources with a standard naming convention.
Notes#
This rule does not check if Virtual Network names are unique.
Links#
- OE:04 Continuous integration
- Naming rules and restrictions for Azure resources
- Recommended abbreviations for Azure resource types
- Parameters in Bicep
- Bicep functions
- Azure deployment reference