Azure Firewall

Handian Sudianto 5,321 Reputation points
2024-06-24T07:34:11.0466667+00:00

Hello,

Currently i have 3 server with Public IP enabled, and each server have specific rule to allow some ports accessing from internet. What i do is block incoming connection on the NSG.

If i have azure firewall, can i block incoming connection from the firewall? Also can we assign the VM public ip from Azure firewall like we create NAT on the on-prem firewall so we no need to assign public ip to each azure VM NIC.

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

Accepted answer
  1. KapilAnanth-MSFT 47,196 Reputation points Microsoft Employee
    2024-06-26T12:40:20.8333333+00:00

    @Handian Sudianto ,

    Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.

    To answer your query "I think DNAT is like Port Forwarding and not One to One NAT, am I right?"

    • Correct.

    Please note that, with Multiple Firewall IPs,

    • You can specify the IP and Port for DNAT Traffic (incoming to Azure)
    • However, you cannot exclusively specify the IP (and Port) used for SNAT (outgoing from Azure)

    See : Azure Firewall with multiple public IP

    User's image

    Kindly let us know if this helps or you need further assistance on this issue.

    Thanks,

    Kapil


    Please don’t forget to close the thread by clicking "Accept the answer" wherever the information provided helps you, as this can be beneficial to other community members.


1 additional answer

Sort by: Most helpful
  1. Deepanshukatara-6769 10,685 Reputation points
    2024-06-24T07:44:20.79+00:00

    Hi @handian, Welcome to MS Q&A

    I understand your concern about using Azure Firewall to block incoming connections and assigning public IPs to Azure VM NICs. Let me provide some information to address your questions:

    • Azure Firewall allows you to define what traffic to allow or deny through your firewall by creating rule collections. These rule collections include DNAT (Destination Network Address Translation), Network, and Application rules. The Network rule collections can be used to allow or deny traffic based on source IP addresses, destination IP addresses, ports, and protocols, including the ability to filter traffic using service tags. Additionally, you can configure Azure Firewall Destination Network Address Translation (DNAT) to translate and filter inbound internet traffic to your subnets, allowing you to control incoming connections

    .

    • As for assigning public IPs to Azure VM NICs, Azure Firewall can help in this scenario by allowing you to translate and filter inbound internet traffic without the need to assign a public IP to each Azure VM NIC. This can be achieved by configuring DNAT rules in the Azure Firewall to translate your firewall public IP and port to a private IP and port, effectively providing NAT functionality similar to an on-premises firewall .

    I hope this information helps address your concerns about using Azure Firewall to block incoming connections and assign public IPs to Azure VM NICs.

    For more detailed instructions, you can view solutions:

    https://learn.microsoft.com/en-us/azure/firewall/tutorial-firewall-dnat

    https://learn.microsoft.com/en-us/azure/firewall/tutorial-firewall-dnat-policy

    Kindly accept if it helps

    If you have any questions , please let us know

    Thanks

    Deepanshu


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.