Single Subscription Deployment to Dedicated Deployment #2037
-
|
Hi guys, I've got a new Azure environment that I deployed this landing zone template to using the Single subscription config to test it out. I've now got 3x subscriptions created and would like to emulate the recommended Dedicated approach. Since i've already deployed the template as a single subscription, whats the recommended approach to transitioning to the dedicated method? Do I just run the template again? Do I need to delete everything and start over? I haven't managed to find anything in the wiki about this. I also noticed that when deployment finished, the management groups under "platform" were missing. I had to add "identity", "management" and "connectivity" manually. The single subscription I had at the time was just under that "platform" group. I'm not sure if this is intended as part of the single supscription deployment or not. I was thinking I could just move the subscriptions to their appropriate place but I'm not sure if that'll work or not due to the automation. I imagine I would also need to manually move the existing groups and resources to their relevant subscription as well. Apologies if this has been answered before, I had a look and couldn't see any other threads made about it. Really cool template, I'm hoping to convince my boss to use it at work as it'll make managing our env a lot easier. Cheers |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
So i answered my own question through experimentation, and can confirm that you cannot transition from Single to Dedicated once either one is applied. You also shouldn't run the landing zone deployment again with this change of configuration as it will not work properly, and will run into a bunch of script conflicts (and may break the current configuration). To get it to work properly, I nuked my test environment and began from scratch. In this instance, Dedicated worked beautifully. So for anyone that may want to trial this in their own environment, I suggest you do so in a new throw-away tenant, or a separate tenant instance from your PROD. |
Beta Was this translation helpful? Give feedback.
So i answered my own question through experimentation, and can confirm that you cannot transition from Single to Dedicated once either one is applied. You also shouldn't run the landing zone deployment again with this change of configuration as it will not work properly, and will run into a bunch of script conflicts (and may break the current configuration).
To get it to work properly, I nuked my test environment and began from scratch. In this instance, Dedicated worked beautifully.
So for anyone that may want to trial this in their own environment, I suggest you do so in a new throw-away tenant, or a separate tenant instance from your PROD.