Smaller Azure deployments with deployment stacks
We used to deploy the entire subscription in one go. The network, shared services, and workloads all went through the same Bicep entrypoint. It was straightforward to follow: one deployment described the environment. That became harder to maintain as the templates grew. We were using Azure Verified Modules (AVM), and combining those modules in a subscription-wide deployment brought us up against ARM’s 4 MB template limit. The Bicep files could look manageable while the compiled template included the definitions of all those modules. ...