Close
Back
Back

    Browse Platforms

  • Browse All
Professional Level

Attach a Firewall to a Virtual Network in Azure

What's a Hands-on Lab?Get Started
1.25 hours
  • 4 Learning Objectives

About this Hands-on Lab

Your company needs to restrict outgoing traffic from their server using a firewall. They want you to block users from visiting anything besides `https://microsoft.com` and they don’t want to allow port 53 outbound from the server. You will create a firewall and connect it to your virtual network as a solution.

Learning Objectives

Successfully complete this lab by achieving the following learning objectives:

Create a Firewall
  1. Log in to the Azure portal with the credentials provided.
  2. Create a new Azure firewall named AZ-FW.
  3. Use the existing virtual network provisioned with this lab.
  4. Create a new public IP for the firewall.
Create a Route Table
  1. Create a new route table.
  2. Route all traffic (0.0.0.0/0) to a virtual appliance (your Azure firewall’s private IP).
Configure Rule Collections for Firewall
  1. Configure an application rule collection to allow www.microsoft.com.
  2. Add a network rule to allow UDP port 53 outbound to Google public DNS servers (8.8.8.8 and 8.8.4.4).
  3. Add a NAT rule that will route traffic from the firewall public IP to the private IP of the server over 3389 (RDP).
  4. Add the public DNS servers to the network interface of the server.
Test Connectivity
  1. Log in to the server using the public IP address of the firewall.
  2. Open Internet Explorer and go to https://www.microsoft.com.
  3. Test DNS.
Contact SalesGet Started

Additional Resources

Log in to the Azure portal, where you will see a Windows server is already deployed with this hands-on lab.

First, create a new Azure firewall named FW-1 followed by a route table named RT-FW to route all traffic through the firewall. On the firewall, configure an application rule collection to allow www.microsoft.com from the network.

Next, add a network rule collection to allow UDP port 53 from the network to 8.8.8.8 and 8.8.4.4. Also, create a network address translation (NAT) rule that will allow you to log in to the server from the firewall public IP.

Finally, add the Google DNS servers to the network interface and test the firewall from the Windows Server. (HINT: Use nslookup -type=TXT test.dns.google.com. dns.google. to test the network rule.)

Note: When you connect via RDP, use the public IP of FW-1.

What are Hands-on Labs

Hands-on Labs are real environments created by industry experts to help you learn. These environments help you gain knowledge and experience, practice without compromising your system, test without risk, destroy without fear, and let you learn from your mistakes. Hands-on Labs: practice your skills before delivering in the real world.

Get Started
Who’s going to be learning?
MyselfMy Organization

How many seats do you need?

  • $499 USD per seat per year
  • Billed Annually
  • Renews in 12 months

Ready to accelerate learning?

For over 25 licenses, a member of our sales team will walk you through a custom tailored solution for your business.

$2,495.00

Checkout
Sign In
Welcome Back!

Don't have an account?

Thanks for reaching out!

You’ll hear from us shortly. In the meantime, why not check out what our customers have to say about ACG?

Why Businesses Love ACG