{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260917-030-check-resource-group-name-uniqueness-before-creating-an-azure-maintenance/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260917-030-check-resource-group-name-uniqueness-before-creating-an-azure-maintenance/", "slug": "dse-20260917-030-check-resource-group-name-uniqueness-before-creating-an-azure-maintenance", "url": "https://update.dsesecurity.com/updates/dse-20260917-030-check-resource-group-name-uniqueness-before-creating-an-azure-maintenance/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260917-030-check-resource-group-name-uniqueness-before-creating-an-azure-maintenance.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260917-030-check-resource-group-name-uniqueness-before-creating-an-azure-maintenance/" }, "title": "Check resource-group name uniqueness before creating an Azure maintenance configuration", "summary": "DSE recommends checking existing configuration names in the intended resource group before building a regional deployment loop.", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "managed-it", "label": "Managed IT operations", "alt": "A controlled technology lifecycle progressing from assessment to approved production.", "card_url": "https://update.dsesecurity.com/assets/editorial/managed-it-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/managed-it-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "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:30+00:00", "modified_at": "2026-09-17T16:35:03+00:00", "reviewed_on": "2026-09-17", "reading_minutes": 1, "word_count": 216, "potentially_affected": "This guide applies to an Azure CLI maintenance-configuration deployment when an automation run is creating a named resource or preparing configurations for more than one location.", "dse_recommendation": "DSE recommends checking existing configuration names in the intended resource group before building a regional deployment loop.", "primary_source": { "name": "Maintenance Configurations for Azure virtual machines using the Azure CLI - Azure Virtual Machines | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/virtual-machines/maintenance-configurations-cli", "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 maintenance configuration names must be unique within their resource group. Creating a configuration with the same name but a different location produces an error. Its CLI procedure lists configurations and their identifiers before assigning a configuration to a machine. Microsoft Learn

\n

Applicability

\n

This guide applies to an Azure CLI maintenance-configuration deployment when an automation run is creating a named resource or preparing configurations for more than one location.

\n

DSE recommendation

\n

DSE recommends checking existing configuration names in the intended resource group before building a regional deployment loop. Record the full resource identifier and location of any matching configuration, and decide whether the request should use that resource or create a separately named one. Keep name selection and target-machine assignment as distinct review steps. Do not assume changing the location parameter creates an independent configuration with the same name.

\n

Verification

\n

Inspect the returned configuration list and compare each name, resource group, location, and identifier with the deployment plan. If creation fails because the name already exists, resolve the identity conflict before retrying or changing assignments. Confirm that each target refers to the intended configuration identifier, and retain the final mapping with the deployment record.

\n

Official references

\n", "content_text": "Source facts\nMicrosoft says maintenance configuration names must be unique within their resource group. Creating a configuration with the same name but a different location produces an error. Its CLI procedure lists configurations and their identifiers before assigning a configuration to a machine. Microsoft Learn\nApplicability\nThis guide applies to an Azure CLI maintenance-configuration deployment when an automation run is creating a named resource or preparing configurations for more than one location.\nDSE recommendation\nDSE recommends checking existing configuration names in the intended resource group before building a regional deployment loop. Record the full resource identifier and location of any matching configuration, and decide whether the request should use that resource or create a separately named one. Keep name selection and target-machine assignment as distinct review steps. Do not assume changing the location parameter creates an independent configuration with the same name.\nVerification\nInspect the returned configuration list and compare each name, resource group, location, and identifier with the deployment plan. If creation fails because the name already exists, resolve the identity conflict before retrying or changing assignments. Confirm that each target refers to the intended configuration identifier, and retain the final mapping with the deployment record.\nOfficial references\n\nMicrosoft: Maintenance Configurations for Azure virtual machines using the Azure CLI – Azure Virtual Machines | Microsoft Learn", "content_markdown": "## Source facts\n\nMicrosoft says maintenance configuration names must be unique within their resource group. Creating a configuration with the same name but a different location produces an error. Its CLI procedure lists configurations and their identifiers before assigning a configuration to a machine. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/virtual-machines/maintenance-configurations-cli)\n\n## Applicability\n\nThis guide applies to an Azure CLI maintenance-configuration deployment when an automation run is creating a named resource or preparing configurations for more than one location.\n\n## DSE recommendation\n\nDSE recommends checking existing configuration names in the intended resource group before building a regional deployment loop. Record the full resource identifier and location of any matching configuration, and decide whether the request should use that resource or create a separately named one. Keep name selection and target-machine assignment as distinct review steps. Do not assume changing the location parameter creates an independent configuration with the same name.\n\n## Verification\n\nInspect the returned configuration list and compare each name, resource group, location, and identifier with the deployment plan. If creation fails because the name already exists, resolve the identity conflict before retrying or changing assignments. Confirm that each target refers to the intended configuration identifier, and retain the final mapping with the deployment record.\n\n## Official references\n\n- [Microsoft: Maintenance Configurations for Azure virtual machines using the Azure CLI – Azure Virtual Machines | Microsoft Learn](https://learn.microsoft.com/en-us/azure/virtual-machines/maintenance-configurations-cli)" }, "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-030-check-resource-group-name-uniqueness-before-creating-an-azure-maintenance/", "url": "https://update.dsesecurity.com/updates/dse-20260917-030-check-resource-group-name-uniqueness-before-creating-an-azure-maintenance/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-17" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260917-030-check-resource-group-name-uniqueness-before-creating-an-azure-maintenance/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Check resource-group name uniqueness before creating an Azure maintenance configuration", "item": "https://update.dsesecurity.com/updates/dse-20260917-030-check-resource-group-name-uniqueness-before-creating-an-azure-maintenance/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260917-030-check-resource-group-name-uniqueness-before-creating-an-azure-maintenance/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260917-030-check-resource-group-name-uniqueness-before-creating-an-azure-maintenance/", "url": "https://update.dsesecurity.com/updates/dse-20260917-030-check-resource-group-name-uniqueness-before-creating-an-azure-maintenance/", "headline": "Check resource-group name uniqueness before creating an Azure maintenance configuration", "description": "DSE recommends checking existing configuration names in the intended resource group before building a regional deployment loop.", "abstract": "DSE recommends checking existing configuration names in the intended resource group before building a regional deployment loop.", "articleBody": "Source facts\nMicrosoft says maintenance configuration names must be unique within their resource group. Creating a configuration with the same name but a different location produces an error. Its CLI procedure lists configurations and their identifiers before assigning a configuration to a machine. Microsoft Learn\nApplicability\nThis guide applies to an Azure CLI maintenance-configuration deployment when an automation run is creating a named resource or preparing configurations for more than one location.\nDSE recommendation\nDSE recommends checking existing configuration names in the intended resource group before building a regional deployment loop. Record the full resource identifier and location of any matching configuration, and decide whether the request should use that resource or create a separately named one. Keep name selection and target-machine assignment as distinct review steps. Do not assume changing the location parameter creates an independent configuration with the same name.\nVerification\nInspect the returned configuration list and compare each name, resource group, location, and identifier with the deployment plan. If creation fails because the name already exists, resolve the identity conflict before retrying or changing assignments. Confirm that each target refers to the intended configuration identifier, and retain the final mapping with the deployment record.\nOfficial references\n\nMicrosoft: Maintenance Configurations for Azure virtual machines using the Azure CLI – Azure Virtual Machines | Microsoft Learn", "datePublished": "2026-09-17T16:34:30+00:00", "dateModified": "2026-09-17T16:35:03+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260917-030-check-resource-group-name-uniqueness-before-creating-an-azure-maintenance/" }, "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-030-check-resource-group-name-uniqueness-before-creating-an-azure-maintenance/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Check resource-group name uniqueness before creating an Azure maintenance configuration" }, "articleSection": [ "IT" ], "keywords": [ "IT", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "wordCount": 216, "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": "Maintenance Configurations for Azure virtual machines using the Azure CLI - Azure Virtual Machines | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/virtual-machines/maintenance-configurations-cli" } } ] } }