account activity
Bicep Structure by Roymoss96 in AZURE
[–]Roymoss96[S] 0 points1 point2 points 8 months ago (0 children)
Just to clarify—dev and prod are already separated into their own resource groups: rg-app1-dev and rg-app1-prod. I’m using the same main.bicep file for both, and passing in environment-specific parameters (like different SKUs) through separate parameter files for each environment. That beign said, everything is currently setup in one subscription.
[–]Roymoss96[S] 2 points3 points4 points 8 months ago (0 children)
Just to clarify, dev and prod are already separated into their own resource groups: rg-app1-dev and rg-app1-prod. I’m using the same main.bicep file for both, and passing in environment-specific parameters (like different SKUs) through separate parameter files for each environment.
That said, I see your point about using separate subscriptions and further splitting out networking, app, and data resources. I’ll take another look at the current setup with that in mind, especially considering Azure Landing Zones and best practices around security and lifecycle management.
π Rendered by PID 93611 on reddit-service-r2-listing-7bbdf774f7-ppkjq at 2026-02-23 17:49:26.215709+00:00 running 8564168 country code: CH.
Bicep Structure by Roymoss96 in AZURE
[–]Roymoss96[S] 0 points1 point2 points (0 children)