Where do you think Visual Studio Subscriptions belong?

[MikaelJcSoderberg]

In the environment I'm normally work in, up to now we have used the Sandbox Management group for all Visual Studio subscriptions.
We are now looking into the lifecycle of the "real" sandboxes(not the Visual Studio ones) and the Visual Studio subscription feels a bit in the way. Some documentation thinks having them there is a good idea, but where do you tink they should be?

In the Sandbox Management group or in a new one directly under out Tenant Root in it's own Management group?

[yabracadabra]

without understanding completely "it feels a bit in the way", could creating an own management group inside/below the sandbox be doable?
since MGs should adhere to the core principle governance purpose, try use:
tenant root/company/azure lz/sandbox/...

limited - follows company rules/compliance with no exceptions
semi-limited - follow company rules/compliance with exceptions
unlimited - as unlimited "as corporately" possible (e.g. only budgets/finance + some networking/identity)

or

tenant root/company/azure lz/sandbox/...

personal
team

or (whatever you see fit, name-wise)

tenant root/company/azure lz/laboratory/...
tenant root/company/azure lz/experiment/...
tenant root/company/azure lz/education/...

sub1
sub2
sub3...

[MikaelJcSoderberg]

In this case I meant that since the Life cycle of "real" Enterprise Scale Sandboxes is controled by our CMDB where ordering/modifying/deletion will be steered from.

Visual Studio Subscriptions are controled if the users have the Liceses and from my group dont have control of the creation/deletion of these.