{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260917-058-normalize-azure-resource-name-casing-in-inventory-comparisons/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260917-058-normalize-azure-resource-name-casing-in-inventory-comparisons/", "slug": "dse-20260917-058-normalize-azure-resource-name-casing-in-inventory-comparisons", "url": "https://update.dsesecurity.com/updates/dse-20260917-058-normalize-azure-resource-name-casing-in-inventory-comparisons/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260917-058-normalize-azure-resource-name-casing-in-inventory-comparisons.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260917-058-normalize-azure-resource-name-casing-in-inventory-comparisons/" }, "title": "Normalize Azure resource-name casing in inventory comparisons", "summary": "Avoid treating casing differences returned by APIs as separate resources.", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "cyber-defense", "label": "Cyber defense", "alt": "Layered glass and metal cyber-defense structure with controlled blue and gold signal paths.", "card_url": "https://update.dsesecurity.com/assets/editorial/cyber-defense-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/cyber-defense-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/cyber-defense-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "cybersecurity", "name": "Cybersecurity", "url": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-09-17T16:34:02+00:00", "modified_at": "2026-09-17T16:38:45+00:00", "reviewed_on": "2026-09-17", "reading_minutes": 1, "word_count": 209, "potentially_affected": "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.", "primary_source": { "name": "Naming rules and restrictions for Azure resources - Azure Resource Manager | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/resource-name-rules", "published_on": null, "authority": "Microsoft Learn" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Source facts

\n

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.

\n

Applicability

\n

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.

\n

DSE recommendation

\n

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.

\n

Verification

\n

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.

\n

Official references

\n

Microsoft Learn: Naming rules and restrictions for Azure resources.

", "content_text": "Source facts\nMicrosoft 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.\nApplicability\nUse 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.\nDSE recommendation\nDSE 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.\nVerification\nCompare 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.\nOfficial references\nMicrosoft Learn: Naming rules and restrictions for Azure resources.", "content_markdown": "## Source facts\n\nMicrosoft 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](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/resource-name-rules).\n\n## Applicability\n\nUse 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.\n\n## DSE recommendation\n\nDSE 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.\n\n## Verification\n\nCompare 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.\n\n## Official references\n\n[Microsoft Learn: Naming rules and restrictions for Azure resources](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/resource-name-rules)." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/dse-20260917-058-normalize-azure-resource-name-casing-in-inventory-comparisons/", "url": "https://update.dsesecurity.com/updates/dse-20260917-058-normalize-azure-resource-name-casing-in-inventory-comparisons/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-17" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260917-058-normalize-azure-resource-name-casing-in-inventory-comparisons/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Normalize Azure resource-name casing in inventory comparisons", "item": "https://update.dsesecurity.com/updates/dse-20260917-058-normalize-azure-resource-name-casing-in-inventory-comparisons/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260917-058-normalize-azure-resource-name-casing-in-inventory-comparisons/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260917-058-normalize-azure-resource-name-casing-in-inventory-comparisons/", "url": "https://update.dsesecurity.com/updates/dse-20260917-058-normalize-azure-resource-name-casing-in-inventory-comparisons/", "headline": "Normalize Azure resource-name casing in inventory comparisons", "description": "Avoid treating casing differences returned by APIs as separate resources.", "abstract": "Avoid treating casing differences returned by APIs as separate resources.", "articleBody": "Source facts\nMicrosoft 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.\nApplicability\nUse 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.\nDSE recommendation\nDSE 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.\nVerification\nCompare 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.\nOfficial references\nMicrosoft Learn: Naming rules and restrictions for Azure resources.", "datePublished": "2026-09-17T16:34:02+00:00", "dateModified": "2026-09-17T16:38:45+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260917-058-normalize-azure-resource-name-casing-in-inventory-comparisons/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/dse-20260917-058-normalize-azure-resource-name-casing-in-inventory-comparisons/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/cyber-defense-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/cyber-defense-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Normalize Azure resource-name casing in inventory comparisons" }, "articleSection": [ "Cybersecurity", "IT" ], "keywords": [ "Cybersecurity", "IT", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Cybersecurity", "url": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "wordCount": 209, "timeRequired": "PT1M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Naming rules and restrictions for Azure resources - Azure Resource Manager | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/resource-name-rules" } } ] } }