Microsoft Cloud Adoption Framework for Azure provides you with guidance and best practices to adopt Azure.
CAF Terraform landing zones team mission statement is to:
- Equip the Site Reliability Engineering teams for Terraform on Azure.
- Democratize an IaC: Infrastructure-as-Configuration.
- Commoditize state management and enterprise-wide composition.
- Standardize deployments using Azure enterprise-scale landing zones.
- Implement Azure enterprise-scale design and approach with native Terraform and DevOps.
- Propose a prescriptive guidance on how to enable DevOps for infrastructure as code on Microsoft Azure.
- Foster a community of Azure Terraformers using a common set of practices and sharing best practices.
You can review the different components parts of the Cloud Adoption Framework for Azure Terraform landing zones and look at the quick intro video below:
When starting an enterprise deployment, we recommend you start creating a configuration repository where you craft the configuration files for your environments.
The best way to start is to clone the platform starter repository and getting started with the configuration files.
If you are reading this, you are probably interested also in reading the doc as below: :books: Read our centralized documentation page
Feel free to open an issue for feature or bug, or to submit a PR.
In case you have any question, you can reach out to tf-landingzones at microsoft dot com.
You can also reach us on Gitter
This project welcomes contributions and suggestions. 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 https://cla.opensource.microsoft.com.
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 [email protected] with any additional questions or comments.