{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-526-keep-a-tenant-deployment-name-paired-with-its-original-deployment-location/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260909-526-keep-a-tenant-deployment-name-paired-with-its-original-deployment-location/", "slug": "dse-20260909-526-keep-a-tenant-deployment-name-paired-with-its-original-deployment-location", "url": "https://update.dsesecurity.com/updates/dse-20260909-526-keep-a-tenant-deployment-name-paired-with-its-original-deployment-location/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260909-526-keep-a-tenant-deployment-name-paired-with-its-original-deployment-location.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-526-keep-a-tenant-deployment-name-paired-with-its-original-deployment-location/" }, "title": "Keep a tenant deployment name paired with its original deployment location", "summary": "Why can a rerun fail with InvalidDeploymentLocation even when the intended resources use another region?", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "network-infrastructure", "label": "Networks & infrastructure", "alt": "Resilient network core with engineered blue and gold data paths.", "card_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "slug": "networks-infrastructure", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "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-10T00:23:10+00:00", "modified_at": "2026-09-10T02:11:18+00:00", "reviewed_on": "2026-09-09", "reading_minutes": 2, "word_count": 231, "potentially_affected": "Azure Resource Manager tenant-scope template deployments.", "dse_recommendation": "DSE recommends keeping the deployment-data location explicit alongside the naming convention.", "primary_source": { "name": "Deploy resources to tenant - Azure Resource Manager | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/azure-resource-manager/templates/deploy-to-tenant", "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

A tenant deployment’s location identifies where Azure stores its deployment data, independently of the locations of the resources being deployed. Once used, a deployment name cannot be reused with a different deployment location. For InvalidDeploymentLocation, Microsoft specifies using the earlier location or choosing another deployment name. Microsoft Learn.

\n

Applicability

\n

Apply this distinction when rerunning a tenant-scope template after changing a pipeline’s location input. Identify the deployment’s name and stored location before changing any resource location. The failing pair concerns deployment records, not necessarily where the template intends to place a workload.

\n

DSE recommendation

\n

DSE recommends keeping the deployment-data location explicit alongside the naming convention. For a failed rerun, compare the requested name/location pair with the existing deployment before selecting the correction. Use the established location when preserving the name is intentional, or approve a distinct name when a different deployment-data location is required. Keep the reason for that choice with the release record.

\n

Verification

\n

Inspect the existing tenant deployment and the sanitized invocation that failed. Verify that the revised pair follows the selected convention, then perform the approved retry in its intended scope. Compare the resource locations separately so fixing the deployment record does not accidentally alter the infrastructure plan. Retain the original error and corrected pair; do not report a new name alone as proof that the resource deployment completed.

\n

Official references

\n

Microsoft Learn. Source retrieved September 9, 2026.

", "content_text": "Source facts\nA tenant deployment’s location identifies where Azure stores its deployment data, independently of the locations of the resources being deployed. Once used, a deployment name cannot be reused with a different deployment location. For InvalidDeploymentLocation, Microsoft specifies using the earlier location or choosing another deployment name. Microsoft Learn.\nApplicability\nApply this distinction when rerunning a tenant-scope template after changing a pipeline’s location input. Identify the deployment’s name and stored location before changing any resource location. The failing pair concerns deployment records, not necessarily where the template intends to place a workload.\nDSE recommendation\nDSE recommends keeping the deployment-data location explicit alongside the naming convention. For a failed rerun, compare the requested name/location pair with the existing deployment before selecting the correction. Use the established location when preserving the name is intentional, or approve a distinct name when a different deployment-data location is required. Keep the reason for that choice with the release record.\nVerification\nInspect the existing tenant deployment and the sanitized invocation that failed. Verify that the revised pair follows the selected convention, then perform the approved retry in its intended scope. Compare the resource locations separately so fixing the deployment record does not accidentally alter the infrastructure plan. Retain the original error and corrected pair; do not report a new name alone as proof that the resource deployment completed.\nOfficial references\nMicrosoft Learn. Source retrieved September 9, 2026.", "content_markdown": "## Source facts\n\nA tenant deployment’s location identifies where Azure stores its deployment data, independently of the locations of the resources being deployed. Once used, a deployment name cannot be reused with a different deployment location. For InvalidDeploymentLocation, Microsoft specifies using the earlier location or choosing another deployment name. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/azure-resource-manager/templates/deploy-to-tenant).\n\n## Applicability\n\nApply this distinction when rerunning a tenant-scope template after changing a pipeline’s location input. Identify the deployment’s name and stored location before changing any resource location. The failing pair concerns deployment records, not necessarily where the template intends to place a workload.\n\n## DSE recommendation\n\nDSE recommends keeping the deployment-data location explicit alongside the naming convention. For a failed rerun, compare the requested name/location pair with the existing deployment before selecting the correction. Use the established location when preserving the name is intentional, or approve a distinct name when a different deployment-data location is required. Keep the reason for that choice with the release record.\n\n## Verification\n\nInspect the existing tenant deployment and the sanitized invocation that failed. Verify that the revised pair follows the selected convention, then perform the approved retry in its intended scope. Compare the resource locations separately so fixing the deployment record does not accidentally alter the infrastructure plan. Retain the original error and corrected pair; do not report a new name alone as proof that the resource deployment completed.\n\n## Official references\n\n[Microsoft Learn](https://learn.microsoft.com/en-us/azure/azure-resource-manager/templates/deploy-to-tenant). Source retrieved September 9, 2026." }, "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-20260909-526-keep-a-tenant-deployment-name-paired-with-its-original-deployment-location/", "url": "https://update.dsesecurity.com/updates/dse-20260909-526-keep-a-tenant-deployment-name-paired-with-its-original-deployment-location/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-09" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260909-526-keep-a-tenant-deployment-name-paired-with-its-original-deployment-location/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Keep a tenant deployment name paired with its original deployment location", "item": "https://update.dsesecurity.com/updates/dse-20260909-526-keep-a-tenant-deployment-name-paired-with-its-original-deployment-location/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260909-526-keep-a-tenant-deployment-name-paired-with-its-original-deployment-location/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260909-526-keep-a-tenant-deployment-name-paired-with-its-original-deployment-location/", "url": "https://update.dsesecurity.com/updates/dse-20260909-526-keep-a-tenant-deployment-name-paired-with-its-original-deployment-location/", "headline": "Keep a tenant deployment name paired with its original deployment location", "description": "Why can a rerun fail with InvalidDeploymentLocation even when the intended resources use another region?", "abstract": "Why can a rerun fail with InvalidDeploymentLocation even when the intended resources use another region?", "articleBody": "Source facts\nA tenant deployment’s location identifies where Azure stores its deployment data, independently of the locations of the resources being deployed. Once used, a deployment name cannot be reused with a different deployment location. For InvalidDeploymentLocation, Microsoft specifies using the earlier location or choosing another deployment name. Microsoft Learn.\nApplicability\nApply this distinction when rerunning a tenant-scope template after changing a pipeline’s location input. Identify the deployment’s name and stored location before changing any resource location. The failing pair concerns deployment records, not necessarily where the template intends to place a workload.\nDSE recommendation\nDSE recommends keeping the deployment-data location explicit alongside the naming convention. For a failed rerun, compare the requested name/location pair with the existing deployment before selecting the correction. Use the established location when preserving the name is intentional, or approve a distinct name when a different deployment-data location is required. Keep the reason for that choice with the release record.\nVerification\nInspect the existing tenant deployment and the sanitized invocation that failed. Verify that the revised pair follows the selected convention, then perform the approved retry in its intended scope. Compare the resource locations separately so fixing the deployment record does not accidentally alter the infrastructure plan. Retain the original error and corrected pair; do not report a new name alone as proof that the resource deployment completed.\nOfficial references\nMicrosoft Learn. Source retrieved September 9, 2026.", "datePublished": "2026-09-10T00:23:10+00:00", "dateModified": "2026-09-10T02:11:18+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260909-526-keep-a-tenant-deployment-name-paired-with-its-original-deployment-location/" }, "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-20260909-526-keep-a-tenant-deployment-name-paired-with-its-original-deployment-location/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Keep a tenant deployment name paired with its original deployment location" }, "articleSection": [ "IT", "Networks & Infrastructure" ], "keywords": [ "IT", "Networks & Infrastructure", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "@type": "Thing", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "wordCount": 231, "timeRequired": "PT2M", "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": "Deploy resources to tenant - Azure Resource Manager | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/azure-resource-manager/templates/deploy-to-tenant" } } ] } }