• Sign in to the Azure portal using an account with the Owner or Contributor role in the Azure subscription.

• In the Azure portal, search for "Virtual networks" and click on it.

• On the Virtual Networks blade, click "+ Create" to create a new virtual network.

• On the Basics tab of the Create virtual network blade, specify the following settings:

• On the IP addresses tab of the Create virtual network blade, set the IPv4 address space to "10.0.0.0/16".

• In the Subnet name column, click on "default" and on the Edit subnet blade, specify the following settings:

• Click "Review + create" and then click "Create" to create the virtual network.

Navigate back to the Virtual Networks blade.

Click on the "myVirtualNetwork" entry.

In the Settings section, click on "Subnets".

On the Subnets blade, click "+ Subnet" to add a new subnet.

On the Add subnet blade, specify the following settings:

Click "Save" to add the new subnet.

Note: The virtual network now has two subnets: Public and Private.

In the Azure portal, search for "Network security groups" and click on it.

On the Network security groups blade, click "+ Create" to create a new network security group.

On the Basics tab of the Create network security group blade, specify the following settings:

Click "Review + create" and then click "Create" to create the network security group.

On the myNsgPrivate blade, in the Settings section, click "Outbound security rules".

On the Outbound security rules blade, click "+ Add" to add a new outbound security rule.

On the Add outbound security rule blade, specify the following settings to allow outbound traffic to Azure Storage:

On the Add outbound security rule blade, click Add to create the new outbound rule.

On the myNsgPrivate blade, in the Settings section, click Outbound security rules, and then click + Add.

On the Add outbound security rule blade, specify the following settings to explicitly deny outbound traffic to the Internet (leave all other values with their default settings):

Note: This rule overrides a default rule in all network security groups that allows outbound internet communication.

Note: In the next steps, you will create an inbound security rule that allows Remote Desktop Protocol (RDP) traffic to the subnet. The rule overrides a default security rule that denies all inbound traffic from the internet. Remote Desktop connections are allowed to the subnet so that connectivity can be tested in a later step.

On the Add inbound security rule blade, click Add to create the new inbound rule.

On the myNsgPrivate blade, in the Settings section, click Inbound security rules and then click + Add.

On the Add inbound security rule blade, specify the following settings (leave all other values with their default values):

Note: Now you will associate the network security group with the Private subnet.

On the Subnets blade, select + Associate and specify the following settings in the Associate subnet section and then click OK:

In this task, you will create a network security group with one inbound security rule (RDP). You will also associate the network security group with the Public subnet. This will allow RDP access to the Public VM.

In the Azure portal, in the Search resources, services, and docs text box at the top of the Azure portal page, type Network security groups and press the Enter key.

On the Network security groups blade, click + Create.

On the Basics tab of the Create network security group blade, specify the following settings:

Click Review + Create and then click Create.

Note: In the next steps, you will create an outbound security rule that allows communication with the Azure Storage service.

In the Azure portal, navigate back to the Network security groups blade and click the myNsgPublic entry.

On the myNsgPublic blade, in the Settings section, click Inbound security rules and then click + Add.

On the Add inbound security rule blade, specify the following settings (leave all other values with their default values):

On the Add inbound security rule blade, click Add to create the new inbound rule.

Note: Now you will associate the network security group with the Public subnet.

On the Subnets blade, select + Associate and specify the following settings in the Associate subnet section and then click OK:

In this task, you will create a storage account with a file share and obtain the storage account key.

In the Azure portal, in the Search resources, services, and docs text box at the top of the Azure portal page, type Storage accounts and press the Enter key.

On the Storage accounts blade, click + Create.

On the Basics tab of the Create storage account blade, specify the following settings (leave others with their default values):

On the Basics tab of the Create storage account blade, click Review + Create, wait for the validation process to complete, and click Create.

Note: Wait for the Storage account to be created. This should take about 2 minutes.

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.

On the Resource groups blade, in the list of resource group, click the AZ500LAB12 entry.

On the AZ500LAB12 resource group blade, in the list of resources, click the entry representing the newly created storage account.

On the storage account Overview blade, click File Shares under the Data storage tab, and then click + File Share.

On the New file share blade, specify the following settings:

Setting Value Name my-file-share On the New file share blade, click Create.

Note: Now, retrieve and record the PowerShell script that creates a drive mapping to the Azure file share.

On the storage account blade, in the list of file shares, click my-file-share.

On the my-file-share blade, click Connect.

On the Connect blade, on the Windows tab, copy the PowerShell script that creates a Z drive mapping to the file share.

Note: Record this script. You will need this later in this lab in order to map the file share from the Azure virtual machine on the Private subnet.

Navigate back to the storage account blade, then in the Security + networking section, click Networking.

Under Firewalls and virtual networks blade, select the Enabled from selected virtual networks and IP addresses option and click the + Add existing virtual network link.

On the Add networks blade, specify the following settings:

On the Add networks blade, click Add.

Back on the storage account blade, click Save.

Note: At this point in the lab you have configured a virtual network, a network security group, and a storage account with a file share.

In this task, you will create two virtual machines one in the Private subnet and one in the Public subnet.

Note: The first virtual machine will be connected to the Private subnet.

In the Azure portal, in the Search resources, services, and docs text box at the top of the Azure portal page, type Virtual machines and press the Enter key.

On the Virtual machines blade, click + Create and, in the dropdown list, click + Azure Virtual machine

On the Basics tab of the Create a virtual machine blade, specify the following settings (leave others with their default values):

Already have a Windows Server license Not selected

Note: For public inbound ports, we will rely on the precreated NSG.

Click Next: Disks > and, on the Disks tab of the Create a virtual machine blade, set the OS disk type to Standard HDD and click Next: Networking >.

Click Next: Networking >, on the Networking tab of the Create a virtual machine blade, specify the following settings (leave others with their default values):

Click Next: Management >, on the Management tab of the Create a virtual machine blade, accept the default settings and click Review + create.

On the Review + create blade, ensure that validation was successful and click Create.

Note: The second virtual machine will be connected to the Public subnet.

On the Virtual machines blade, click + Add and, in the dropdown list, click + Azure Virtual machine.

On the Basics tab of the Create a virtual machine blade, specify the following settings (leave others with their default values):

Note: For public inbound ports, we will rely on the pre-created NSG.

Click Next: Disks > and, on the Disks tab of the Create a virtual machine blade, set the OS disk type to Standard HDD and click Next: Networking >.

Click Next: Networking >, on the Networking tab of the Create a virtual machine blade, specify the following settings (leave others with their default values):

Click Next: Management >, on the Management tab of the Create a virtual machine blade, accept the default settings and click Review + create.

On the Review + create blade, ensure that validation was successful and click Create.

Note: You can continue to the next task once the deployment of the myVMPrivate Azure VM is completed.

In this task, you will connect to the myVMPrivate virtual machine via Remote Desktop and map a drive to the file share.

Navigate back to the Virtual machines blade.

On the Virtual machines blade, click the myVMPrivate entry.

On the myVMPrivate blade, click Connect and, in the drop-down menu, click RDP.

Click Download RDP File and use it to connect to the myVMPrivate Azure VM via Remote Desktop. When prompted to authenticate, provide the following credentials:

Note: Wait for the Remote Desktop session to open and Server Manager to load.

Note: You will now map drive Z to an Azure File share within the Remote Desktop session to a Windows Server 2022 computer

Within the Remote Desktop session to myVMPrivate, click Start and then click Windows PowerShell ISE.

Within the Windows PowerShell ISE window, open the Script pane, then paste and run the PowerShell script that you recorded earlier in this lab. The script has the following format:

 $connectTestResult = Test-NetConnection -ComputerName <storage_account_name>.file.core.windows.net -Port 445
 if ($connectTestResult.TcpTestSucceeded) {
    # Save the password so the drive will persist on reboot
    cmd.exe /C "cmdkey /add:`"<storage_account_name>.file.core.windows.net`" /user:`"localhost\<storage_account_name>`"  /pass:`"<storage_account_key>`""
    # Mount the drive
    New-PSDrive -Name Z -PSProvider FileSystem -Root "\\<storage_account_name>.file.core.windows.net\my-file-share" -Persist
 } else {
    Write-Error -Message "Unable to reach the Azure storage account via port 445. Check to make sure your organization or ISP is not blocking port 445, or use Azure P2S VPN, Azure S2S VPN, or Express Route to tunnel SMB traffic over a different port."
 }

Note: The <storage_account_name> placeholder represents the name of the storage account hosting the file share and <storage_account_key> on its primary key

Start File Explorer and verify that the Z: drive mapping has been successfully created.

Next, from the console pane of the Windows PowerShell ISE console, run the following to verify that the virtual machine has no outbound connectivity to the internet:

 Test-NetConnection -ComputerName www.bing.com -Port 80

Note: The test will fail because the network security group associated with the Private subnet does not allow outbound access to the internet.

Terminate the Remote Desktop session to the myVMPrivate Azure VM.

Note: At this point, you have confirmed that the virtual machine in the Private subnet can access the storage account.

Navigate back to the Virtual machines blade.

On the Virtual machines blade, click the myVMPublic entry.

On the myVMPublic blade, click Connect and, in the drop-down menu, click RDP.

Click Download RDP File and use it to connect to the myVMPublic Azure VM via Remote Desktop. When prompted to authenticate, provide the following credentials:

Note: Wait for the Remote Desktop session to open and Server Manager to load.

Note: You will now map drive Z to an Azure File share within the Remote Desktop session to a Windows Server 2022 computer

Within the Remote Desktop session to myVMPublic, click Start and then click Windows PowerShell ISE.

Within the Windows PowerShell ISE window, open the Script pane, then paste and run the same PowerShell script that you ran within the Remote Desktop session to the myVMPrivate Azure VM.

Note: This time, you will receive the New-PSDrive: Access is denied error.

Note: Access is denied because the myVmPublic virtual machine is deployed in the Public subnet. The Public subnet does not have a service endpoint enabled for Azure Storage. The storage account only allows network access from the Private subnet.

Next, from the console pane of the Windows PowerShell ISE console, run the following to verify that the virtual machine has outbound connectivity to the internet:

 Test-NetConnection -ComputerName www.bing.com -Port 80

Note: The test will succeed because there is no outbound security rule to deny internet on the Public subnet.

Terminate the Remote Desktop session to the myVMPublic Azure VM.

Note: At this point, you have confirmed that the virtual machine in the Public subnet cannot access the storage account, but has access to the internet.

Clean up resources

Remember to remove any newly created Azure resources that you no longer use. Removing unused resources ensures you will not incur unexpected costs.

Open the Cloud Shell by clicking the first icon in the top right of the Azure Portal. If prompted, select PowerShell and Create Storage.

Ensure PowerShell is selected in the drop-down menu in the upper-left corner of the Cloud Shell pane.

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 "AZ500LAB12" -Force -AsJob

Close the Cloud Shell pane.