Azure策略部署报错CaseSensitiveDeploymentParameterNamesFound求助

I’ve run into this exact headache before with Azure policy and ARM template parameters—those case-sensitive rules can be sneaky! Let’s break down how to resolve this CaseSensitiveDeploymentParameterNamesFound error tied to your vmName parameter.

Root Cause #

Azure ARM templates treat parameter names as strictly case-sensitive. Even a single letter differing in case (like vmname vs vmName) gets recognized as two separate parameters. When your policy definition has inconsistent casing for vmName across sections (policy parameters, deployment template, parameter mappings), Azure flags this as duplicate parameters, hence the error.

Step-by-Step Fixes #

1. Standardize Parameter Casing Everywhere
   Go through your entire policy definition and lock in a single casing for the VM name parameter (stick with camelCase vmName for consistency, or all lowercase—just don’t mix them):

   • Check the top-level parameters block of your policy: confirm it’s defined as "vmName": { ... } (matching your chosen casing).
   • Verify the deployment template section (inside the DeployIfNotExists rule’s deployment property): the template’s own parameters must match the casing, and all references like [parameters('vmName')] must use the exact same string.

2. Fix Parameter Mappings in the Policy
   In the deployment block where you pass values to the extension template, ensure the parameter key matches your standardized casing. For example:

   "deployment": {
     "properties": {
       "mode": "incremental",
       "template": { /* your CustomScriptExtension template */ },
       "parameters": {
         "vmName": { "value": "[field('name')]" } // Correct casing matches policy and template params
       }
     }
   }
   

   Avoid writing "vmname": "[field('name')]" here if your parameter is defined as vmName.

3. Clean Up Old Assignments and Republish
   Azure sometimes caches outdated policy definitions. Delete any existing assignments of this policy, re-publish your updated (casing-consistent) policy definition, then create a new assignment. This ensures Azure picks up the corrected parameter structure fully.

4. Validate the Extension Template Fragment
   Isolate the CustomScriptExtension ARM template part and double-check for hidden casing issues. For example, confirm the extension name uses the correct parameter:

   "name": "[concat(parameters('vmName'), '/CustomScriptExtension')]"
   

   You can even test this template manually on a single VM to rule out other issues.

Example of a Consistent Snippet #

Here’s a condensed, casing-consistent example of how the parameter flow should look:

{
  "properties": {
    "displayName": "Deploy CustomScriptExtension to Target Linux VMs",
    "policyType": "Custom",
    "mode": "Indexed",
    "parameters": {
      "vmName": {
        "type": "string",
        "metadata": { "description": "Name of the target virtual machine" }
      }
    },
    "policyRule": {
      "if": { /* your condition for OpenSuse/Ubuntu/Oracle Linux VMs */ },
      "then": {
        "effect": "DeployIfNotExists",
        "details": {
          "type": "Microsoft.Compute/virtualMachines/extensions",
          "existenceCondition": { /* your extension existence check */ },
          "deployment": {
            "properties": {
              "mode": "incremental",
              "template": {
                "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
                "contentVersion": "1.0.0.0",
                "parameters": {
                  "vmName": { "type": "string" },
                  "location": { "type": "string" }
                },
                "resources": [
                  {
                    "type": "Microsoft.Compute/virtualMachines/extensions",
                    "apiVersion": "2023-07-01",
                    "name": "[concat(parameters('vmName'), '/CustomScriptExtension')]",
                    "location": "[parameters('location')]",
                    "properties": {
                      "publisher": "Microsoft.Azure.Extensions",
                      "type": "CustomScript",
                      "typeHandlerVersion": "2.1",
                      "autoUpgradeMinorVersion": true,
                      "settings": {
                        "fileUris": ["https://your-storage-account.blob.core.windows.net/scripts/bac.sh"],
                        "commandToExecute": "sudo bash bac.sh"
                      }
                    }
                  }
                ]
              },
              "parameters": {
                "vmName": { "value": "[field('name')]" },
                "location": { "value": "[field('location')]" }
              }
            }
          }
        }
      }
    }
  }
}

Double-check every instance of the VM name parameter across the policy and template—even one mismatched character will trigger that error. Once you’ve standardized the casing and re-deployed the policy, the CaseSensitiveDeploymentParameterNamesFound error should vanish.

内容的提问来源于stack exchange，提问作者Tech Enthusiast