search

cykreng / Enterprise-Scale-AppService

8 stars 9 forks source link

Azure Gov Deployment - Name Length Checking #51

Open haithamshahin333 opened 3 years ago

haithamshahin333 commented 3 years ago

Issue:

When deploying to Azure Gov, may need to consider name checking on length given that regions have longer names than in Azure Commercial which ultimately result in longer resource names (which can result in deployment errors).

Example:

Location: usgovvirginia workloadName: ase703hs Error: When creating Microsoft.Network/virtualNetworks/virtualNetworkPeerings resource between hub and spoke

{
    "status": "Failed",
    "error": {
        "code": "InvalidResourceName",
        "message": "Resource name vnet-hub-ase703hs-dev-usgovvirginia-001-vnet-spoke-ase703hs-dev-usgovvirginia-001 is invalid. The name can be up to 80 characters long. It must begin with a word character, and it must end with a word character or with '_'. The name may contain word characters or '.', '-', '_'.",
        "details": []
    }
}