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