Normalize Azure resource-name casing in inventory comparisons

Source facts

Microsoft says resource and resource-group names are case-insensitive unless the resource’s valid-character rules explicitly state otherwise. APIs may return casing different from what was originally supplied, or from the table’s presentation. Its guidance is to compare names without case sensitivity. Microsoft Learn.

Applicability

Use this review for inventory reconciliation that compares Azure names from multiple management surfaces. Identify the exact resource type and check its current naming rules, including any stated exception. Preserve subscription, resource group and resource type as part of the matching context.

DSE recommendation

DSE recommends reviewing name-comparison logic before escalating a casing-only discrepancy as a missing asset. Keep the originally returned display value for evidence while applying the approved normalization to comparisons. Have the inventory owner test matching behavior against the actual resource types in scope. Do not merge records solely because their normalized short names match.

Verification

Compare representative records whose name casing differs but whose complete resource context agrees. Also include distinct resources with the same short name in different scopes to confirm that normalization does not collapse them. Retain the inputs, matching decision and resource-type exception review. Investigate differences beyond casing separately, using the authoritative resource identifiers where available.

Official references

Microsoft Learn: Naming rules and restrictions for Azure resources.