Extend the Azure landing-zone foundation you already run so that additional Azure regions become qualified options for workloads, without creating separate governance models or copying an identical platform footprint into every region.
This repository provides guidance and a browser-based planning workbook for platform and workload teams. It helps you qualify candidate regions, choose the connectivity and shared services each region needs, prepare the platform, and make workload-specific placement decisions. Enabling a region does not require moving workloads or deploying every workload across multiple regions.
- Read the guidance or start with Getting started.
- Use the region planning workbook to compare regions, record qualification evidence and regional designs, and export to Excel or save a JSON planning record.
- Download the whitepaper or executive brief.
The scope is Azure public-cloud regions. This is guidance and planning tooling, not a deployable landing-zone implementation or a guarantee of service availability. Availability is inferred from a published pricing snapshot; prices and estimated latency are planning inputs that must be revalidated for a workload.
The primary article text lives in content/. Website tooling lives in site/, and GitHub Pages serves the generated docs/ folder. The repository also contains editable whitepaper, PowerPoint, and Word-generation sources.
| Task | Guide |
|---|---|
| Write or update articles, diagrams, and related formats; prepare a CAF export | Authoring and maintaining the guidance |
| Generate the website, PDFs, decks, or Word edition; publish the site | Building and publishing |
| Collect Azure service-availability indicators, prices, region metadata, and latency | Azure data collection |
| Maintain the planning workbook and geography views | Region planning workbook |
Contributions and feedback are welcome. See Contributing for the workflow and Microsoft Contributor License Agreement. Use GitHub issues for non-security bugs, documentation corrections, and suggestions. Do not post security vulnerabilities publicly; follow Security.
This project follows the Microsoft Open Source Code of Conduct and is licensed under the MIT License. Third-party assets retain their own terms, and the license does not grant rights to Microsoft or other trademarks; see Contributing.