Azure Landing Zones (ALZ) - Bicep

Welcome to the Azure Landing Zones Bicep repo.

Detailed information about how to use, deploy and extend artifacts found in this repo can be found on our Wiki:

• Home
• Deployment Flow
  • Network Topology: Hub and Spoke
  • Network Topology: Virtual WAN
• Consumer Guide
• How Does ALZ-Bicep Implement Azure Policies?
  • Adding Custom Azure Policy Definitions
  • Assigning Azure Policies
• Contributing
• Telemetry Tracking Using Customer Usage Attribution (PID)
• Azure Container Registry Deployment - Private Bicep Registry
• Frequently Asked Questions
• Sample Pipelines
  • GitHub Actions
  • Azure DevOps
• Code Tours

Overview

The Azure Landing Zones Bicep repo provides an approach for deploying and managing the core platform capabilities of Cloud Adoption Framework Azure Landing Zones conceptual architecture using Bicep.

In its current incarnation each module can be deployed separately via command line but in future releases a more automated approach, via orchestration modules, will be published; but due to current Bicep & ARM limitations this is not possible today.

Have you seen our page in the Azure Architecture Center here: Azure landing zones - Bicep modules design considerations

Getting Started

To get started with ALZ Bicep, please refer to the Deployment Flow wiki page for:

1. Prerequisites and dependencies for the overall implementation.
2. High-level deployment flow.
3. Links to more detailed instructions on individual modules.

Azure Enablement Show Videos

We have created a short 3-part series of video on the Azure Enablement Show that can be found below:

Part 1 - Introduction to Azure Landing Zones Bicep

Part 2 - Azure Landing Zones Bicep - Enabling platform services

Part 3 - Azure Landing Zones Bicep - Enabling landing zones

Contributing

This project welcomes contributions and suggestions. Please review our Contributing guide in the Wiki. Once your PR is created and submitted a member of the team will triage, review and discuss with you 👍 Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit the Microsoft Contributor License Agreement page. When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA. This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Telemetry

When you deploy one or more modules in Azure Landing Zones Bicep repo, Microsoft can identify the installation of said module/s with the deployed Azure resources. Microsoft can correlate these resources used to support the software. Microsoft collects this information to provide the best experiences with their products and to operate their business. The telemetry is collected through customer usage attribution. The data is collected and governed by Microsoft's privacy policies.

If you don't wish to send usage data to Microsoft, details on how to turn it off can be found here.

Trademarks

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.

Security

If you believe you have found a security vulnerability in this repository, please refer to this guide on how to report it.

Support

For support on the artifacts contained in this repository, please refer to this guide for more details.