Welcome to the Azure Network Security community repository. This repo is designed to help:
- Deploy Azure NetSec resources programmatically using scripts and templates.
- Manage configuration of NetSec resources at scale using scripts, templates, Logic Apps (API), and Azure Policy
- Integrate NetSec resources with other tools, such as Azure Sentinel.
- Discover best practices and interesting techniques.
- Contribute back to your community with samples you create and think others would find useful.
- Azure Firewall Docs
- Azure Firewall Manager Docs
- Azure WAF Docs
- Azure DDoS Protection Docs
- Azure Networking Feedback
- Technical Community Blog
Please find the latest artifacts in this repo on our What's New Page
All automations within this repository are provided as is, without SLA or official support. However, if you have an issue please fill out a bug report and reference the automation artifact, so the community can try to solve it.
This project has its own Wiki which will provide you with further information about the Azure Network Security community, how to contribute, templates to use and other resources.
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.microsoft.com.
Note: If you are a first time contributor to this repository, Fork the repo before cloning.
Brand new or update to a contribution via these methods:
- Submit for review directly on GitHub website
- Browse to the folder you want to upload your file to
- Choose Upload Files and browse to your file.
- You will be required to create your own branch and then submit the Pull Request for review.
- Use GitHub Desktop or Visual Studio or VSCode
- Fork the repo
- Clone the repo
- Create your own branch
- Do your additions/updates in GitHub Desktop
- Push your changes to GitHub
- After you push your changes, you will need to submit the Pull Request (PR)
- After submission, check the Pull Request for comments
- Make changes as suggested and update your branch or explain why no change is needed. Resolve the comment when done.
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., label, 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.