Skip to content

Commit dec8265

Browse files
Merge pull request #218295 from mbender-ms/patch-35
AVNM - Typo in Markdown syntax - Update how-to-block-high-risk-ports.md
2 parents 923e1d3 + d2ebc7f commit dec8265

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/virtual-network-manager/how-to-block-high-risk-ports.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -164,7 +164,7 @@ With traffic blocked across all of your VNets, you need an exception to allow tr
164164

165165
In this section, you create a new rule collection that will allow high-risk traffic to a subset of virtual networks you've defined in a network group, and create security admin rule to add to our existing security admin configuration.
166166

167-
> [!Important]
167+
> [!IMPORTANT]
168168
> In order for your security admin rule to allow traffic to your application virtual networks, the priority needs to be set to a **lower number** than existing rules blocking traffic.
169169
>
170170
>For example, an all network rule blocking **SSH** has a priority of **10** so your allow rule should have a priority from **1 to 9**.
@@ -188,4 +188,4 @@ To apply the new rule collection, you'll redeploy your security admin configurat
188188

189189
- Learn how to [create a mesh network topology with Azure Virtual Network Manager using the Azure portal](how-to-create-mesh-network.md)
190190

191-
- Check out the [Azure Virtual Network Manager FAQ](faq.md)
191+
- Check out the [Azure Virtual Network Manager FAQ](faq.md)

0 commit comments

Comments
 (0)