# Keep a tenant deployment name paired with its original deployment location

> Why can a rerun fail with InvalidDeploymentLocation even when the intended resources use another region?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-526-keep-a-tenant-deployment-name-paired-with-its-original-deployment-location/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:23:10+00:00
- Modified: 2026-09-10T02:11:18+00:00
- Last reviewed by DSE: 2026-09-09
- Resource type: Guide
- DSE priority: Information
- Topics: IT, Networks & Infrastructure
- Reading time: 2 minutes

## What you need to know

Why can a rerun fail with InvalidDeploymentLocation even when the intended resources use another region?

## Potentially affected

Azure Resource Manager tenant-scope template deployments.

## DSE recommendation

DSE recommends keeping the deployment-data location explicit alongside the naming convention.

## Article

## Source facts

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](https://learn.microsoft.com/en-us/azure/azure-resource-manager/templates/deploy-to-tenant).

## Applicability

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.

## DSE recommendation

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.

## Verification

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.

## Official references

[Microsoft Learn](https://learn.microsoft.com/en-us/azure/azure-resource-manager/templates/deploy-to-tenant). Source retrieved September 9, 2026.

## Primary reference

- Name: Deploy resources to tenant - Azure Resource Manager | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/azure-resource-manager/templates/deploy-to-tenant
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Keep a tenant deployment name paired with its original deployment location,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-526-keep-a-tenant-deployment-name-paired-with-its-original-deployment-location/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.