What is the recommended approach for multi-region platform landing zone subscriptions?
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. What is the recommended approach? Should I 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