Just for an example, makes sense to close port 80 – HTTP inbound (unless you plan to expose unencrypted admin access to the Internet)<\/p>\n\n\n\n However, as soon as you disable port TCP 80, you have two different warnings<\/p>\n\n\n\n Looking at the rules, you can see that there are two default rules (with the lowest priority available) dedicated to permit Virtual Network traffic and Azure Load Balancer traffic<\/p>\n\n\n\n So, the question that I tried to answer was: does it make sense to create rules with a higher priority just to replicate what the default ones do (and remove the warnings)?<\/p>\n\n\n\n Virtual Network Access<\/strong><\/p>\n\n\n\n Let’s start with VNet traffic: as for the Microsoft documentation https:\/\/docs.microsoft.com\/en-us\/azure\/virtual-network\/virtual-networks-faq<\/a> they are used to create virtual networks in the Cloud (or to extend your datacentre network). They are also used for peering VMs https:\/\/docs.microsoft.com\/en-us\/azure\/virtual-network\/virtual-network-peering-overview<\/a><\/p>\n\n\n\n If you are deploying virtual SBCs that do not require direct communication with other VMs, you can safely ignore the warning<\/strong><\/p>\n\n\n\n![\"\"](\"https:\/\/modern-workplace.uk\/wp-content\/uploads\/2020\/12\/Deny_01-1.jpg\")
<\/a><\/figure>\n\n\n\nWarning #1 \u2013 This rule denies traffic from AzureLoadBalancer and may affect virtual machine connectivity. To allow access, add an inbound rule with higher priority to allow AzureLoadBalancer to VirtualNetwork.\nWarning #2 \u2013 This rule denies virtual network access. If you wish to allow access to your virtual network, add an inbound rule with higher priority to Allow VirtualNetwork to VirtualNetwork.\n<\/code><\/pre>\n\n\n\n<\/a><\/figure>\n\n\n\n<\/a><\/figure>\n\n\n\n