Skip to content

Latest commit

 

History

History
47 lines (31 loc) · 1.8 KB

CAF.Name.Route.md

File metadata and controls

47 lines (31 loc) · 1.8 KB
Raw
pillar category online version
Operational Excellence
Resource naming

Use standard route table names

SYNOPSIS

Route table names should use a standard prefix.

DESCRIPTION

An effective naming convention allows operators to quickly identify resource type, associated workload, deployment environment and Azure region.

For route tables, the Cloud Adoption Framework recommends using the route- prefix.

Requirements for route table names:

  • At least 1 character, but no more than 80.
  • Can include alphanumeric, underscore, hyphen, period characters.
  • Can only start with a letter or number, and end with a letter, number or underscore.
  • Route table names must be unique within a resource group.

RECOMMENDATION

Consider creating route tables with a standard name. Additionally consider using Azure Policy to only permit creation using a standard naming convention.

NOTES

This rule does not check if route table names are unique.

To configure this rule:

  • Override the CAF_RouteTablePrefix configuration value with an array of allowed prefixes.
  • Override CAF_UseLowerNames with false to allow mixed case in resource names. By default only lower-case letters and other supported characters are allowed. This option affects all resource name rules.

LINKS