Hub/Spoke can only be deployed to one region per subscription

[jrspinella]

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

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

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

Happens in US Gov as well.

Expected behavior Able to deploy a second Hub/Spoke to another region

Software versions used:

• Azure CLI version [e.g. v2.23.0]
• Azure Bicep version [v0.4.8.0]

Additional context