jtracey93
commented
4 months ago Hey @tw3lveparsecs,
The guidance here: https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/considerations/regions#traditional-hub-and-spoke-architecture is the ALZ guidance, whilst the over link is about data landing zones scenarios; whilst similar they are different things that work with each other.
The guidance from us in the ALZ team is as per: https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/considerations/regions#traditional-hub-and-spoke-architecture
Most customers can do this all in single subscriptions across regions for each platform element. e.g. multiple regions deployed in the same connectivity subscription etc.
There are some scenarios, mainly around avoiding quota limits for scale or data sovereignty requirements, that may lead you to separate subs per region for the platform elements, but most do not have a need for this.
Hope that help
Jack 👍
Describe the solution you'd like
When deploying to multiple regions, there is conflicting information on whether to use new platform landing zone subscriptions (identity, management, connectivity) or the existing subscription.
Are we able to get some clarity on the recommended approach? Should we use the existing subscription or create a new subscription for each region?
One article recommends using the existing subscription: https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/considerations/regions#traditional-hub-and-spoke-architecture
Another article recommends using a different subscription for each region: https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/scenarios/cloud-scale-analytics/eslz-network-considerations-cross-region