The Mission Landing Zone can only be deployed to one region per subscription

[LManning-Dev]

Description

The deployment contains at least one module that has a static name: set-identity-sub-defender
This module gets stored as a deployment at the subscription level
When a 2nd instance of the MLZ is deployed to a DR site, an error occurs
The deployment 'set-identity-sub-defender' already exists in location

Note: If you deploy to the same region, no error is encountered. Possibly in this scenario the deployment item is able to be overwritten.

Steps to Reproduce

Steps to reproduce the behavior:

1. deploy to eastus (any location)
2. deploy to westus (any location other than step 1) to the same subscription(s) as 1

Expected behavior

Able to deploy a second MLZ region

Actual behavior

Error: The deployment 'set-identity-sub-defender' already exists in location 'eastus'
InvalidDeploymentLocation

Screenshots

Additional context

If you deploy to the same region, no error is encountered. Possibly in this scenario the deployment item is able to be overwritten.

Recommended Solution:
Change ALL deployment module names to end with the deploymentNameSuffix
(It looks like this was changed for many of them already: name: 'set-hub-sub-defender-${deploymentNameSuffix}')

I.E.
name: 'set-${spoke.name}-sub-defender'
name: 'set-${spoke.name}-sub-defender-${deploymentNameSuffix}'

List of modules that probably require the change
name: 'set-${spoke.name}-sub-defender'
name: 'azure-monitor-private-link'
name: 'azure-private-dns'

Thank you

Operating System:
Terraform Version:
Cloud (public, Azure Government, etc.):