Feature Request: Split Accelerator into separate directories/pipelines (Mgmt Groups & Policy, Connectivity, Management) with independent Terraform state

[greg-court]

Is there an existing issue for this?

• I have searched the existing issues

Infrastructure as Code Type? (Required)

terraform

Starter Module? (Required)

terraform - platform_landing_zone

Use Case (Required)

I know this was mentioned as being considered a few months ago on a YouTube video (I think Jared calls it out in this one?), and I’m aware of the colossal scale of this undertaking, but could we please get this added to the public roadmap so we can get some visibility on the progression of this task?

In my humble opinion, this is probably the single biggest step that will make the accelerator a truly enterprise-grade tool :)

Proposed Solution (Required)

Split the repo into three top-level directories—mgmt-groups-policy/, platform_connectivity/, and platform_management/—each with its own Terraform state/backend and a dedicated pipeline (GitHub Actions/Azure DevOps) that calls the existing pipeline templates.

Benefits: smaller/faster plans, reduced blast radius, least-privilege credentials per pipeline, and a clean path to extend over time.

Important Factoids (Optional)

No response

References (Optional)

No response

[moler-udi]

After working with this for a bit now, I'm kind if scared taking all this into production just because the blast radius on changing anything. As a minimum I would like to see all policy be separated out, as this I see where a lot of future issues might arise.

[jaredfholgate]

We already have this on our road map, but not sure on the timescales.

At the moment this is already possible with multiple accelerator deployments each with different tfvars. However it would also deploy multiple bootstraps as it stands although some manual config could take care of that. I'm not suggesting this is a good or long term solution, just if it is urgently needed.

[thepaulmacca]

Whilst I appreciate the time and effort that's gone into this so far, I'm quite surprised that it's been done like this in the first place to be honest, coming from Microsoft

Was there a specific reason why?