Tutorial: Deploy & configure Azure Firewall and policy using the Azure portal (2024)

Article
06/06/2024

Controlling outbound network access is an important part of an overall network security plan. For example, you may want to limit access to web sites. Or, you may want to limit the outbound IP addresses and ports that can be accessed.

One way you can control outbound network access from an Azure subnet is with Azure Firewall and Firewall Policy. With Azure Firewall and Firewall Policy, you can configure:

Application rules that define fully qualified domain names (FQDNs) that can be accessed from a subnet.
Network rules that define source address, protocol, destination port, and destination address.

Network traffic is subjected to the configured firewall rules when you route your network traffic to the firewall as the subnet default gateway.

For this tutorial, you create a simplified single VNet with two subnets for easy deployment.

AzureFirewallSubnet - the firewall is in this subnet.
Workload-SN - the workload server is in this subnet. This subnet's network traffic goes through the firewall.

For production deployments, a hub and spoke model is recommended, where the firewall is in its own VNet. The workload servers are in peered VNets in the same region with one or more subnets.

In this tutorial, you learn how to:

Set up a test network environment
Deploy a firewall and firewall policy
Create a default route
Configure an application rule to allow access to www.google.com
Configure a network rule to allow access to external DNS servers
Configure a NAT rule to allow a remote desktop to the test server
Test the firewall

If you prefer, you can complete this procedure using Azure PowerShell.

Prerequisites

If you don't have an Azure subscription, create a free account before you begin.

Set up the network

First, create a resource group to contain the resources needed to deploy the firewall. Then create a VNet, subnets, and a test server.

Create a resource group

The resource group contains all the resources for the tutorial.

Sign in to the Azure portal.
On the Azure portal menu, select Resource groups or search for and select Resource groups from any page, then select Create. Enter or select the following values:
Setting Value
Subscription Select your Azure subscription.
Resource group Enter Test-FW-RG.
Region Select a region. All other resources that you create must be in the same region.
Select Review + create.
Select Create.

Create a VNet

This VNet will have two subnets.

Note

The size of the AzureFirewallSubnet subnet is /26. For more information about the subnet size, see Azure Firewall FAQ.

On the Azure portal menu or from the Home page, select Create a resource.
Select Networking.
See Also
Azure Firewall rule processing logic Azure Firewall vs WAF Azure Firewall – Cloud Network Security Solutions | Microsoft Azure Best practice and use case scenario of Azure Firewall ? - Microsoft Q&A
Search for Virtual network and select Create.
Enter or select the following values:
Setting Value
Subscription Select your Azure subscription.
Resource group Select Test-FW-RG.
Name Enter Test-FW-VN.
Region Select the same location that you used previously.
Select Next.
On the Security tab, select Next.
For IPv4 Address space, accept the default 10.0.0.0/16.
Under Subnets, select default.
On the Edit subnet page, for Subnet purpose, select Azure Firewall.
The firewall will be in this subnet, and the subnet name must be AzureFirewallSubnet.
For Starting address, type 10.0.1.0.
Select Save.

Next, create a subnet for the workload server.

Select Add subnet.
For Subnet name, type Workload-SN.
For Starting address, type 10.0.2.0/24.
Select Add.
Select Review + create.
Select Create.

Create a virtual machine

Now create the workload virtual machine, and place it in the Workload-SN subnet.

On the Azure portal menu or from the Home page, select Create a resource.
Select Windows Server 2019 Datacenter.

Enter or select these values for the virtual machine:

Setting	Value
Subscription	Select your Azure subscription.
Resource group	Select Test-FW-RG.
Virtual machine name	Enter Srv-Work.
Region	Select the same location that you used previously.
Username	Enter a username.
Password	Enter a password.

Under Inbound port rules, Public inbound ports, select None.
Accept the other defaults and select Next: Disks.
Accept the disk defaults and select Next: Networking.
Make sure that Test-FW-VN is selected for the virtual network and the subnet is Workload-SN.
For Public IP, select None.
Accept the other defaults and select Next: Management.
Select Next:Monitoring.
Select Disable to disable boot diagnostics. Accept the other defaults and select Review + create.
Review the settings on the summary page, and then select Create.
See Also
No inbound traffic to external firewall interfaces in Azure and change to default NSG behaviour
After the deployment completes, select the Srv-Work resource and note the private IP address for later use.

Deploy the firewall and policy

Deploy the firewall into the VNet.

On the Azure portal menu or from the Home page, select Create a resource.
Type firewall in the search box and press Enter.
Select Firewall and then select Create.

On the Create a Firewall page, use the following table to configure the firewall:

Setting	Value
Subscription	Select your Azure subscription.
Resource group	Select Test-FW-RG.
Name	Enter Test-FW01.
Region	Select the same location that you used previously.
Firewall management	Select Use a Firewall Policy to manage this firewall.
Firewall policy	Select Add new, and enter fw-test-pol. Select the same region that you used previously.
Choose a virtual network	Select Use existing, and then select Test-FW-VN.
Public IP address	Select Add new, and enter fw-pip for the Name.

Accept the other default values, then select Next: Tags.
Select Next : Review + create.
Review the summary, and then select Create to create the firewall.
This will take a few minutes to deploy.
After deployment completes, go to the Test-FW-RG resource group, and select the Test-FW01 firewall.
Note the firewall private and public IP addresses. You'll use these addresses later.

Create a default route

For the Workload-SN subnet, configure the outbound default route to go through the firewall.

On the Azure portal menu, select All services or search for and select All services from any page.
Under Networking, select Route tables.
Select Create, then enter or select the following values:
Setting Value
Subscription Select your Azure subscription.
Resource group Select Test-FW-RG.
Region Select the same location that you used previously.
Name Enter Firewall-route.
Select Review + create.
Select Create.

After deployment completes, select Go to resource.

On the Firewall-route page, under Settings, select Subnets and then select Associate.
For Virtual network select Test-FW-VN.
For Subnet, select Workload-SN.
Select OK.
Select Routes and then select Add.
For Route name, enter fw-dg.
For Destination type select IP Addresses.
For Destination IP addresses/CIDR ranges prefix, enter 0.0.0.0/0.
For Next hop type, select Virtual appliance.
Azure Firewall is actually a managed service, but virtual appliance works in this situation.
For Next hop address, enter the private IP address for the firewall that you noted previously.
Select Add.

Configure an application rule

This is the application rule that allows outbound access to www.google.com.

Open the Test-FW-RG resource group, and select the fw-test-pol firewall policy.
Under Settings, Select Application rules.
Select Add a rule collection.
For Name, enter App-Coll01.
For Priority, enter 200.
For Rule collection action, select Allow.
Under Rules, for Name, enter Allow-Google.
For Source type, select IP address.
For Source, enter 10.0.2.0/24.
For Protocol:port, enter http, https.
For Destination Type, select FQDN.
For Destination, enter www.google.com
Select Add.

Azure Firewall includes a built-in rule collection for infrastructure FQDNs that are allowed by default. These FQDNs are specific for the platform and can't be used for other purposes. For more information, see Infrastructure FQDNs.

Configure a network rule

This is the network rule that allows outbound access to two IP addresses at port 53 (DNS).

Select Network rules.
Select Add a rule collection.
For Name, enter Net-Coll01.
For Priority, enter 200.
For Rule collection action, select Allow.
For Rule collection group, select DefaultNetworkRuleCollectionGroup.
Under Rules, for Name, enter Allow-DNS.
For Source type, select IP Address.
For Source, enter 10.0.2.0/24.
For Protocol, select UDP.
For Destination Ports, enter 53.
For Destination type select IP address.
For Destination, enter 209.244.0.3,209.244.0.4.
These are public DNS servers operated by CenturyLink.
Select Add.

Configure a DNAT rule

This rule allows you to connect a remote desktop to the Srv-Work virtual machine through the firewall.

Select the DNAT rules.
Select Add a rule collection.
For Name, enter RDP.
For Priority, enter 200.
For Rule collection group, select DefaultDnatRuleCollectionGroup.
Under Rules, for Name, enter rdp-nat.
For Source type, select IP address.
For Source, enter *.
For Protocol, select TCP.
For Destination Ports, enter 3389.
For Destination, enter the firewall public IP address.
For Translated type, select IP Address.
For Translated address, enter the Srv-work private IP address.
For Translated port, enter 3389.
Select Add.

Change the primary and secondary DNS address for the Srv-Work network interface

For testing purposes in this tutorial, configure the server's primary and secondary DNS addresses. This isn't a general Azure Firewall requirement.

On the Azure portal menu, select Resource groups or search for and select Resource groups from any page. Select the Test-FW-RG resource group.
Select the network interface for the Srv-Work virtual machine.
Under Settings, select DNS servers.
Under DNS servers, select Custom.
Enter 209.244.0.3 in the Add DNS server text box, and 209.244.0.4 in the next text box.
Select Save.
Restart the Srv-Work virtual machine.

Test the firewall

Now, test the firewall to confirm that it works as expected.

Connect a remote desktop to firewall public IP address and sign in to the Srv-Work virtual machine.
Open Microsoft Edge and browse to https://www.google.com.
Select OK > Close on the Internet Explorer security alerts.
You should see the Google home page.
Browse to https://www.microsoft.com.
You should be blocked by the firewall.

So now you've verified that the firewall rules are working:

You can browse to the one allowed FQDN, but not to any others.
You can resolve DNS names using the configured external DNS server.

Clean up resources

You can keep your firewall resources for the next tutorial, or if no longer needed, delete the Test-FW-RG resource group to delete all firewall-related resources.

Next steps

Deploy and configure Azure Firewall Premium