# Azure/Enterprise-Scale

The Azure Landing Zones (Enterprise-Scale) architecture provides prescriptive guidance coupled with Azure best practices, and it follows design principles across the critical design areas for organizations to define their Azure architecture

Repository: https://github.com/Azure/Enterprise-Scale
Canonical: https://ross.abutalabs.com/products/enterprise-scale
Homepage: https://aka.ms/alz
Language: PowerShell
License: MIT
License Family: permissive
Topics: azure, arm, enterprise-scale, architecture, policy-driven, alz, azure-landing-zones, azure-policy, eslz, landing-zone, landing-zones
Last push: 2026-08-26T06:21:55+00:00

## Health v2 (maintenance only)
Score: 98/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 99, release rhythm 97, longevity 100
- inputs: {"age_days": 2301, "days_push": 7, "days_rel": 22, "gap_med": 13, "n_releases_24m": 32}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1955, forks 1065 (observed 2026-08-28T04:05:58.966644+00:00)

## What it is
Azure Landing Zones (Enterprise-Scale) is a reference implementation providing prescriptive guidance and ARM/PowerShell tooling for deploying a well-architected Azure environment. It encodes Microsoft's best practices for governance, security, and policy-driven management of enterprise Azure estates.

## Use cases
- set up an enterprise Azure landing zone
- deploy Azure governance and policy at scale
- bootstrap a multi-subscription Azure architecture
- implement Azure best practices for security and compliance
- structure management groups and subscriptions in Azure
- accelerate Azure adoption with a reference architecture

## When to choose
- you are adopting Azure at enterprise scale and need a proven target architecture
- you want policy-driven governance, management group hierarchy, and landing zone deployment out of the box
- you need prescriptive Microsoft-aligned guidance for Azure platform design decisions

## When to avoid
- you only run workloads on AWS, GCP, or on-premises
- you need a simple single-subscription Azure setup without governance overhead
- you require a fully custom architecture that diverges significantly from Azure landing zone principles

## Facets
- artifact type: infra-config
- maturity: active
- function: infrastructure-as-code, deployment, security, configuration-management
- domain: cloud-computing, infrastructure-as-code, self-hosted
- platform: cloud, windows
- tags: azure-landing-zones, enterprise-architecture, arm-templates, azure-policy, cloud-governance, reference-implementation, devops

## Member repositories
- Azure/Enterprise-Scale (main) score 98

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:05:58.966644+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T03:06:14.914705+00:00, confidence not recorded.
  - readme: https://github.com/Azure/Enterprise-Scale (fetched 2026-08-28T04:05:58.966644+00:00, sha b391f7321148)
- Data as of 2026-08-30T08:39:29.467469+00:00.