How Should You Structure Dev, UAT, Staging and Prod in Azure?

This is one of those decisions that can look simple at the beginning of a project and become increasingly important as the environment grows.

Should each environment have its own Resource Group?

Should Production have a separate Subscription?

Where should shared services live?

How should naming, tagging and CI/CD fit into the design?

There isn't one universal answer. The right structure depends on factors such as security boundaries, ownership, lifecycle, deployment processes and operational requirements.

In this article, I look at:

• Dev, UAT, Staging and Production environment boundaries
• Resource Groups vs Azure Subscriptions
• Production isolation
• Naming conventions
• Azure tagging
• CI/CD considerations
• Blue/Green deployment considerations
• Common environment architecture mistakes

The main idea is that environment architecture should be designed around clear operational and security boundaries rather than simply creating more Resource Groups.

I would be interested to hear how others structure Dev, UAT, Staging and Production in enterprise Azure environments.

Full article:

https://www.linkedin.com/pulse/how-should-you-structure-dev-uat-staging-prod-azure-chethan-raj-ktfac/