The Relationship of Management Group's and Subscriptions

[josh-at-unisuper]

Using the following models, which is recommended?

1 subscription for the Landing Zone "app"?
or
Having many subscriptions to divide the various environments?

└───Tenant Root Group
    ├───Company - Non-Production (Management Group)
    │   │
    │   └───Landing Zones - Non-Production (Management Group)
    │       │
    │       ├───App LZ (1 Subscription) - Non-Production (Management Group)
    │       │   └───App - Non-Production (Subscription)
    │       │
    │       └───App LZ (Many Subscriptions) - Non-Production (Management Group)
    │           ├───App - Development (Subscription)
    │           ├───App - Private (Subscription)
    │           ├───App - Regression (Subscription)
    │           ├───App - Shared (Subscription)
    │           └───App - Test (Subscription)
    │
    └───Company - Production (Management Group)
        │
        └───Landing Zones - Production (Management Group)
            │
            ├───App LZ (1 Subscription) - Production (Management Group)
            │   ├───App - Disaster Recovery (Subscription)
            │   └───App - Production (Subscription)
            │
            └───App LZ (Many Subscriptions) - Production (Management Group)
                ├───App - Disaster Recovery (Subscription)
                └───App - Production (Subscription)

[jtracey93]

Hey @josh-at-unisuper,

Have you seen our guidance on handling dev/test/prod here: https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/ready/enterprise-scale/faq#how-do-we-handle-devtestproduction-workload-landing-zones-in-enterprise-scale-architecture

Might be what you are looking for.

Let us know if not 👍