Deny inbound NSG Rule creation via Azure Policy
In this blog article, we will cover how to deny the creation of inbound Network Security Group Rules if the inbound NSG Rule contains Internet, Any, or 0.0.0.0/0 as source and the destination port contains 22, 3389 or *".
Note: If users have the required permissions, they can create exemption for their resources. Which make this policy ineffective for that resource.
Custom Policy Definition creation
You can follow the steps below to create a custom policy:
1) From the Azure portal, access Azure policy, then definitions blade.
2) Create a new policy definition.
3) Add the definition location (which subscription will be hosting this policy), Name, and description.
4) Set the category to use existing and select Networking (as below):
5) Then add the below policy definition into the rule field:
Note: you can add more default ports for which this policy will be evaluated. These are the default port used in this policy.
"*",
"22",
"3389",
6) Then save the policy.
Policy Assignment
Now you can assign this policy as per your requirements.
1) From Azure policies page, and access definitions blade -> select the created custom policy, and click assign policy (you can assign on the Subscription level or a specific resource group depending on your business requirements).
2) To update the port list at time of policy assignment. Go to Parameters tab, then uncheck the box "Only show parameters that need input or review" and select of the three dots next to the "blocked ports" box.
3) It will open the editor; update the ports you want to include in this policy and click save.
4) Click Next, and Next, update the "Non-compliance message" as per your requirement.
5) Click review + create and review the output. Once verified create the policy assignment.
Policy assignment usually takes around 5-15 minutes to take effect.
To update the list of ports after the policy assignment. Edit the policy assignment, go to the parameters tab and edit the ports.
Disclaimer
Please note that products and options presented in this article are subject to change. This article reflects custom policy for Azure Network Security Rules in September 2024.
If users have the required permissions, they can create exemption for their resources. Which make this policy ineffective for that resource.
References
Tutorial: Create a custom policy definition - Azure Policy | Microsoft Learn
Programmatically create policies - Azure Policy | Microsoft Learn
Published on:
Learn moreRelated posts
Azure Cosmos DB with DiskANN Part 2: Scaling to 1 Billion Vectors with
Introduction In the first part of our series on Azure Cosmos DB Vector Search with DiskANN, we explored the fundamentals of vector indexing an...
Azure Service Bus Integration with Dynamics Business Central and External Systems – Part 2: Financials Integration
Introduction In this blog post, we’ll explore how to integrate financial data between an external system (EXT) and Microsoft Dynamics 365 Busi...
Azure Toolkit for IntelliJ: Introducing the enhanced Java Code Quality Analyzer!
Discover the latest updates to the Azure Toolkit for IntelliJ, featuring an enhanced Java Code Quality Analyzer to help you write cleaner, saf...
Azure Boards + GitHub: Recent Updates
Over the past several months, we’ve delivered a series of improvements to the Azure Boards + GitHub integration. Whether you’re tracking...
Introducing the Azure MCP Server
This post introduces the Azure MCP Server, bringing the power of the cloud to your AI agents. The post Introducing the Azure MCP Server appear...
Azure OpenAI Service now authorized for all U.S. Government data classification levels
In the coming years, artificial intelligence will continue to be foundational to technical innovations for national security missions. Already...
GPT-4.1 is now available at Azure AI Foundry
Azure AI Foundry and AOAI (Azure OpenAI Services) keeps on getting better all the time! The latest addition in Azure AI Foundry (as of April 1...