Azure firewall rules with multiple IP or ranges issue

prasantc 856 Reputation points
2023-10-02T00:52:56.4766667+00:00

I found the following information about IP separated with commas and Azure rule still accepts the rule without error.

Spaces Between IP Addresses or Ranges:

When specifying multiple IP addresses or ranges, separate them with a comma and no spaces. For example: 192.168.1.1,192.168.1.2.

Spaces Around Commas:

Ensure there are no spaces immediately before or after the commas used to separate IP addresses or ranges. Incorrect: 192.168.1.1, 192.168.1.2.

Apparently, entire rule does not work when there is a comma in between

Azure Firewall
Azure Firewall
An Azure network security service that is used to protect Azure Virtual Network resources.
580 questions
{count} votes

1 answer

Sort by: Most helpful
  1. KapilAnanth-MSFT 36,861 Reputation points Microsoft Employee
    2023-10-10T09:39:59.3266667+00:00

    @prasantc

    I did a lab and I was able to reproduce the behavior of Azure firewall adding implicit spaces.

    I was able to add a list of IPs with both

    • Just comma separated
    • Comma separated plus space

    However,

    • Spaces only separated list did not work.

    Is this the issue you are looking at?

    Are you interested in knowing what is the recommended way to do this?

    In any case, the rule I created worked perfectly.

    • It does not matter if you use a "comma separated" or "comma separated plus space".
    • I created a rule that allowed 8.8.8.8 and 1.1.1.1
    • User's image
    • 8.8.8.8 (dns.google)
      • User's image
    • one.one.one.one (1.1.1.1)
      • User's image
    • while accessing www.google.com
      • User's image

    Cheers,

    Kapil

    0 comments No comments