Scenario
You have been asked to install Azure Firewall. This will help your organization control inbound and outbound network access which is an important part of an overall network security plan. Specifically, you would like to create and test the following infrastructure components:
– A virtual network with a workload subnet and a jump host subnet.
– A virtual machine is each subnet.
– A custom route that ensures all outbound workload traffic from the workload subnet must use the firewall.
– Firewall Application rules that only allow outbound traffic to www.bing.com.
– Firewall Network rules that allow external DNS server lookups.
Exercise 1: Deploy and test an Azure Firewall
Task 1: Use a template to deploy the lab environment.
1. Sign-in to the Azure portal https://portal.azure.com/.
2. In the Azure portal, in the Search resources, services, and docs text box at the top of the Azure portal page, type Deploy a custom template and press the Enter key.
3. On the Custom deployment blade, click the Build your own template in the editor option.
4. On the Edit template blade, click Load file, locate the \Allfiles\Labs\08\template.json file and click Open.
NOTE: Review the content of the template and note that it deploys an Azure VM hosting Windows Server 2019 Datacenter.
5. On the Edit template blade, click Save.
6. On the Custom deployment blade, ensure that the following settings are configured (leave any others with their default values):
| Setting | Value |
| Subscription | the name of the Azure subscription you will be using in this lab |
| Resource group | click Create new and type the name AZ500LAB08 |
| Location | (US) East US |
NOTE: To identify Azure regions where you can provision Azure VMs, refer to https://azure.microsoft.com/en-us/regions/offers/
7. Click Review + create, and then click Create.
NOTE: Wait for the deployment to complete. This should take about 2 minutes.
Task 2: Deploy the Azure firewall
1. In the Azure portal, in the Search resources, services, and docs text box at the top of the Azure portal page, type Firewalls and press the Enter key.
2. On the Firewalls blade, click + Add.
3. On the Basics tab of the Create a firewall blade, specify the following settings (leave others with their default values):
| Setting | Value |
| Resource group | AZ500LAB08 |
| Name | Test-FW01 |
| Region | (US) East US |
| Firewall management | Use Firewall rules (classic) to manage this firewall |
| Choose a virtual network | click the Use existing option and, in the drop-down list, select Test-FW-VN |
| Public IP address | clck Add new and type the name TEST-FW-PIP and click OK |
4. Click Review + create and then click Create.
NOTE: Wait for the deployment to complete. This should take about 5 minutes.
5. In the Azure portal, in the Search resources, services, and docs text box at the top of the Azure portal page, type Resource groups and press the Enter key.
6. On the Resource groups blade, in the list of resource group, click the AZ500LAB08 entry.
NOTE: On the AZ500LAB08 resource group blade, review the list of resources. You can sort by Type.
7. In the list of resources, click the entry representing the Test-FW01 firewall.
8. On the Test-FW01 blade, identify the Private IP address that was assigned to the firewall.
NOTE: You will need this information in the next task.
Task 3: Create a default route
1. In the Azure portal, in the Search resources, services, and docs text box at the top of the Azure portal page, type Route tables and press the Enter key.
2.On the Route tables blade, click + Add.
3. On the Create route table blade, specify the following settings:
| Setting | Value |
| Name | Firewall-route |
| Resource group | AZ500LAB08 |
| Region | East US |
4. Click Review + create, then click Create, and wait for the provisioning to complete.
5. On the Route tables blade, click Refresh, and, in the list of route tables, click the Firewall-route entry.
6. On the Firewall-route blade, in the Settings section, click Subnets and then, on the Firewall-route | Subnets blade, click + Associate.
7. On the Associate subnet blade, specify the following settings:
| Setting | Value |
| Virtual network | Test-FW-VN |
| Subnet | Workload-SN |
NOTE: Ensure the Workload-SN subnet is selected for this route, otherwise the firewall won’t work correctly.
8. Click OK to associate the firewall to the virtual network subnet.
9. Back on the Firewall-route blade, in the Settings section, click Routes and then click + Add.
10. On the Add route blade, specify the following settings:
| Setting | Value |
| Route name | FW-DG |
| Address prefix | 0.0.0.0/0 |
| Next hop type | Virtual appliance |
| Next hop address | the private IP address of the firewall that you identified in the previous task |
NOTE: Azure Firewall is actually a managed service, but virtual appliance works in this situation.
11. Click OK to add the route.
Task 4: Configure an application rule
1. In the Azure portal, navigate back to the Test-FW01 firewall.
2. On the Test-FW01 blade, in the Settings section, click Rules.
3. On the Test-FW01 | Rules blade, click the Application rule collection tab, and then click + Add application rule collection.
4. On the Add application rule collection blade, specify the following settings (leave others with their default values):
| Setting | Value |
| Name | App-Coll01 |
| Priority | 200 |
| Action | 200 |
5. On the Add application rule collection blade, create a new entry in the Target FQDNs section with the following settings (leave others with their default values):
| Setting | Value |
| name | AllowGH |
| Source type | IP Address |
| Source | 10.0.2.0/24 |
| Protocol port | http:80, https:443 |
| Target FQDNS | www.bing.com |
6. Click Add to add the Target FQDNs-based application rule.
NOTE: 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.
Task 5: Configure a network rule
1. In the Azure portal, navigate back to the Test-FW01 | Rules blade.
2. On the Test-FW01 | Rules blade, click the Network rule collection tab and then click + Add network rule collection.
3. On the Add network rule collection blade, specify the following settings (leave others with their default values):
| Setting | Value |
| Name | Net-Coll01 |
| Priority | 200 |
| Action | Allow |
4. On the Add network rule collection blade, create a new entry in the IP Addresses section with the following settings (leave others with their default values):
| Setting | Value |
| Name | AllowDNS |
| Protocol | UDP |
| Source type | IP address |
| Source Addresses | 10.0.2.0/24 |
| Destination type | IP address |
| Destination Address | 209.244.0.3,209.244.0.4 |
| Destination Ports | 53 |
5. Click Add to add the network rule.
NOTE: The destination addresses used in this case are known public DNS servers.
Task 6: Configure the virtual machine DNS servers
1. In the Azure portal, navigate back to the AZ500LAB08 resource group.
2. On the AZ500LAB08 blade, in the list of resources, click the Srv-Work virtual machine.
3. On the Srv-Work blade, in the Settings section, click Networking.
4. On the Srv-Work | Networking blade, click the link next to the Network interface entry.
5. On the network interface blade, in the Settings section, click DNS servers, select the Custom option, add the two DNS servers referenced in the network rule: 209.244.0.3 and 209.244.0.4, and click Save to save the change.
6. Return to the Srv-Work virtual machine page.
NOTE:
– Wait for the update to complete.
– Updating the DNS servers for a network interface will automatically restart the virtual machine to which that interface is attached, and if applicable, any other virtual machines in the same availability set.
Task 7: Test the firewall
1. In the Azure portal, navigate back to the AZ500LAB08 resource group.
2. On the AZ500LAB08 blade, in the list of resources, click the Srv-Jump virtual machine.
3. On the Srv-Jump blade, click Connect and, in the drop down menu, click RDP.
4. Click Download RDP File and use it to connect to the Srv-Jump Azure VM via Remote Desktop. When prompted to authenticate, provide the following credntials:
| Setting | Value |
| User name | localadmin |
| Password | Pa55w.rd1234 |
NOTE:
– The following steps are performed in the Remote Desktop session to the Srv-Jump Azure VM.
– You will connect to the Srv-Work virtual machine. This is being done so we can test the ability to access the bing.com website.
5. Within the Remote Desktop session to Srv-Jump, right-click Start, in the right-click menu, click Run, and, from the Run dialog box, run the following to connect to Srv-Work.
mstsc /v:Srv-Work
6. When prompted to authenticate, provide the following credentials:
| Setting | Value |
| User name | localadmin |
| Password | Pa55w.rd1234 |
NOTE: Wait for the Remote Desktop session to be established and the Server Manager interface to load.
7. Within the Remote Desktop session to Srv-Work, in Server Manager, click Local Server and then click IE Enhanced Security Configuration.
8. In the Internet Explorer Enhanced Security Configuration dialog box, set both options to Off and click OK.
9. Within the Remote Desktop session to Srv-Work, start Internet Explorer and browse to https://www.bing.com.
NOTE: The website should successfully display. The firewall allows you access.
10. Browse to http://www.microsoft.com/
NOTE: Within the browser page, you should receive a message with text resembling the following: HTTP request from 10.0.2.4:xxxxx to microsoft.com:80. Action: Deny. No rule matched. Proceeding with default action. This is expected, since the firewall blocks access to this website.
11. Terminate both Remote Desktop sessions.
RESULT: You have successfully configured and tested the Azure Firewall.
Clean up resources
1. In the Azure portal, open the Cloud Shell by clicking the first icon in the top right of the Azure Portal. If prompted, click PowerShell and Create storage.
2. Ensure PowerShell is selected in the drop-down menu in the upper-left corner of the Cloud Shell pane.
3. In the PowerShell session within the Cloud Shell pane, run the following to remove the resource group you created in this lab:
Remove-AzResourceGroup -Name "AZ500LAB08" -Force -AsJob
4. Close the Cloud Shell pane.
I'm Not the PRO 