Azure Deployment Environments
What it is
Azure Deployment Environments (ADE) provides governed, self-service Azure infrastructure environments from reusable environment definitions. A platform team controls templates, project/environment types, identities, subscriptions, and policies; developers request the approved environment.
Why it exists
Teams need temporary development, test, and investigation environments quickly, without each team independently creating insecure or inconsistent infrastructure.
Key ideas
- An environment definition is the reusable infrastructure template; projects make appropriate definitions available to developers.
- ADE separates platform governance from developer self-service: the platform team curates templates and permissions while developers provision within that boundary.
- Use lifecycle/cost controls for temporary environments. A self-service environment without deletion ownership becomes unmanaged spend.
- ADE is in maintenance mode as of the current documentation, so use it where its existing capabilities fit and evaluate platform direction for new long-lived strategy decisions.
Exam decision
Choose ADE when the requirement is governed on-demand Azure application infrastructure from approved templates. It is not merely an Azure Pipelines environment/approval record; the two operate at different layers.
Related
deployment-environment · infrastructure-as-code · bicep · azure-policy