This site is under development and subject to change. Please do not rely on the information contained here. Look out for some exciting updates to Azure Landing Zones coming in 2025!
Azure Landing Zones Documentation
Home GitHub Issue Toggle Dark/Light/Auto mode Toggle Dark/Light/Auto mode Toggle Dark/Light/Auto mode Back to homepage

Contributing

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 opencode@microsoft.com with any additional questions or comments.

Please familiarize yourself with our code of conduct and the MIT License associated with this repository to ensure all code contributions are submitted in accordance with these terms.

Raising an Issue

To raise an issue, please go to our issues log and raise a new issue.

Fill out the Bug or Feature template in full and submit the issue for triage.

Feature Requests

Please raise a feature request as an issue

Contributing to Code

  • Fixes a bug or feature reported and accepted in our Accelerator issues log on the accelerator repo
  • New features should be relevant to, and improve upon, existing core functionality
  • PR contains documentation update
  • PR is rebased against the latest main branch
  • PR is squashed into one commit per logical change
  • PR commit message should be concise but descriptive (will be used to generate release notes)

Contributing to documentation

  • Fixes a documentation bug or feature reported and accepted in this repository’s issues log
  • New features should be relevant to, and improve upon, existing core documentation
  • PR is rebased against the latest main branch
  • PR is squashed into one commit per logical change
  • PR commit message should be concise but descriptive (will be used to generate release notes)