You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Follow the guidelines in this article to provide additional protection for your Azure Virtual Desktop host pool using Azure Firewall.
18
+
Follow the guidelines in this article to provide extra protection for your Azure Virtual Desktop host pool using Azure Firewall.
19
19
20
20
## Prerequisites
21
21
22
22
- A deployed Azure Virtual Desktop environment and host pool.
23
-
- An Azure Firewall deployed with at least one Firewall Manager Policy
23
+
- An Azure Firewall deployed with at least one Firewall Manager Policy.
24
+
- DNS and DNS Proxy enabled in the Firewall Policy to use [FQDN in Network Rules](https://docs.microsoft.com/azure/firewall/fqdn-filtering-network-rules).
24
25
25
26
For more information, see [Tutorial: Create a host pool by using the Azure portal](../virtual-desktop/create-host-pools-azure-marketplace.md)
26
27
@@ -30,48 +31,68 @@ To learn more about Azure Virtual Desktop environments see [Azure Virtual Deskto
30
31
31
32
The Azure virtual machines you create for Azure Virtual Desktop must have access to several Fully Qualified Domain Names (FQDNs) to function properly. Azure Firewall provides an Azure Virtual Desktop FQDN Tag to simplify this configuration. Use the following steps to allow outbound Azure Virtual Desktop platform traffic:
32
33
33
-
You will need to create an Azure Firewall Policy and create Rule Collections for Network Rules and Applications Rules. Give the Rule Collection a priority and an allow or deny action.
34
+
You'll need to create an Azure Firewall Policy and create Rule Collections for Network Rules and Applications Rules. Give the Rule Collection a priority and an allow or deny action.
35
+
In order to identify a specific AVD Host Pool as "Source" in the tables below, [IP Group](https://docs.microsoft.com/azure/firewall/ip-groups) can be created to represent it.
34
36
35
37
### Create network rules
36
38
37
-
| Name | Source type | Source | Protocol | Destination ports | Destination type | Destination |
| Rule Name | IP Address | VNet or Subnet IP Address | TCP | 80 | IP Address | 169.254.169.254, 168.63.129.16 |
40
-
| Rule Name | IP Address | VNet or Subnet IP Address | TCP | 443 | Service Tag | AzureCloud, WindowsVirtualDesktop, AzureFrontDoor.Frontend |
41
-
| Rule Name | IP Address | VNet or Subnet IP Address | TCP, UDP | 53 | IP Address | * |
42
-
|Rule name | IP Address | VNet or Subnet IP Address | TCP | 1688 | IP address | 20.118.99.224, 40.83.235.53 (azkms.core.windows.net)|
43
-
|Rule name | IP Address | VNet or Subnet IP Address | TCP | 1688 | IP address | 23.102.135.246 (kms.core.windows.net)|
39
+
Based on the Azure Virtual Desktop (AVD) [reference article](https://docs.microsoft.com/azure/virtual-desktop/safe-url-list), these are the ***mandatory*** rules to allow outbound access to the control plane and core dependent services:
40
+
41
+
| Name | Source type | Source | Protocol | Destination ports | Destination type | Destination |
| Rule Name | IP Address or Group | IP Group or VNet or Subnet IP Address | TCP | 80 | IP Address | 169.254.169.254, 168.63.129.16 |
44
+
| Rule Name | IP Address or Group | IP Group or VNet or Subnet IP Address | TCP | 443 | Service Tag | WindowsVirtualDesktop, AzureFrontDoor.Frontend, AzureMonitor |
45
+
| Rule Name | IP Address or Group | IP Group or VNet or Subnet IP Address | TCP, UDP | 53 | IP Address | * |
46
+
| Rule name | IP Address or Group | IP Group or VNet or Subnet IP Address | TCP | 1688 | IP address | 20.118.99.224, 40.83.235.53 (azkms.core.windows.net) |
47
+
| Rule name | IP Address or Group | IP Group or VNet or Subnet IP Address | TCP | 1688 | IP address | 23.102.135.246 (kms.core.windows.net) |
48
+
| Rule name | IP Address or Group | IP Group or VNet or Subnet IP Address | TCP | 443 | FQDN | mrsglobalsteus2prod.blob.core.windows.net |
49
+
| Rule name | IP Address or Group | IP Group or VNet or Subnet IP Address | TCP | 443 | FQDN | wvdportalstorageblob.blob.core.windows.net |
50
+
| Rule name | IP Address or Group | IP Group or VNet or Subnet IP Address | TCP | 80 | FQDN | oneocsp.microsoft.com |
51
+
| Rule name | IP Address or Group | IP Group or VNet or Subnet IP Address | TCP | 80 | FQDN |www.microsoft.com|
44
52
45
53
> [!NOTE]
46
54
> Some deployments might not need DNS rules. For example, Azure Active Directory Domain controllers forward DNS queries to Azure DNS at 168.63.129.16.
47
55
56
+
Azure Virtual Desktop (AVD) official documentation reports the following Network rules as **optional** depending on the usage and scenario:
57
+
58
+
| Name | Source type | Source | Protocol | Destination ports | Destination type | Destination |
| Rule Name | IP Address | VNet or Subnet IP Address | Https:443 | FQDN Tag | WindowsVirtualDesktop, WindowsUpdate, Windows Diagnostics, MicrosoftActiveProtectionService |
68
+
Azure Virtual Desktop (AVD) official documentation reports the following Application rules as **optional** depending on the usage and scenario:
69
+
70
+
| Name | Source type | Source | Protocol | Destination type | Destination |
| Rule Name | IP Address or Group | VNet or Subnet IP Address | Https:443 | FQDN Tag | WindowsUpdate, Windows Diagnostics, MicrosoftActiveProtectionService |
73
+
| Rule Name | IP Address or Group | VNet or Subnet IP Address | Https:443 | FQDN |*.events.data.microsoft.com |
74
+
| Rule Name | IP Address or Group | VNet or Subnet IP Address | Https:443 | FQDN |*.sfx.ms |
75
+
| Rule Name | IP Address or Group | VNet or Subnet IP Address | Https:443 | FQDN |*.digicert.com |
76
+
| Rule Name | IP Address or Group | VNet or Subnet IP Address | Https:443 | FQDN |*.azure-dns.com, *.azure-dns.net |
53
77
54
78
> [!IMPORTANT]
55
79
> We recommend that you don't use TLS inspection with Azure Virtual Desktop. For more information, see the [proxy server guidelines](../virtual-desktop/proxy-server-support.md#dont-use-ssl-termination-on-the-proxy-server).
56
80
81
+
## Azure Firewall Policy Sample
82
+
All the mandatory and optional rules mentioned above can be easily deployed a single Azure Firewall Policy using the template published at [this link](https://github.com/Azure/RDS-Templates/tree/master/AzureFirewallPolicyForAVD).
83
+
Before deploying into production, it's highly recommended to review all the Network and Application rules defined, ensure alignment with Azure Virtual Desktop official documentation and security requirements.
84
+
57
85
## Host pool outbound access to the Internet
58
86
59
-
Depending on your organization needs, you might want to enable secure outbound internet access for your end users. If the list of allowed destinations is well-defined (for example, for [Microsoft 365 access](/microsoft-365/enterprise/microsoft-365-ip-web-service)), you can use Azure Firewall application and network rules to configure the required access. This routes end-user traffic directly to the internet for best performance. If you need to allow network connectivity for Windows 365 or Intune, see [Network requirments for Windows 365](/windows-365/requirements-network#allow-network-connectivity) and [Network endpoints for Intune](/mem/intune/fundamentals/intune-endpoints).
87
+
Depending on your organization needs, you might want to enable secure outbound internet access for your end users. If the list of allowed destinations is well-defined (for example, for [Microsoft 365 access](/microsoft-365/enterprise/microsoft-365-ip-web-service)), you can use Azure Firewall application and network rules to configure the required access. This routes end-user traffic directly to the internet for best performance. If you need to allow network connectivity for Windows 365 or Intune, see [Network requirements for Windows 365](/windows-365/requirements-network#allow-network-connectivity) and [Network endpoints for Intune](/mem/intune/fundamentals/intune-endpoints).
60
88
61
89
If you want to filter outbound user internet traffic by using an existing on-premises secure web gateway, you can configure web browsers or other applications running on the Azure Virtual Desktop host pool with an explicit proxy configuration. For example, see [How to use Microsoft Edge command-line options to configure proxy settings](/deployedge/edge-learnmore-cmdline-options-proxy-settings). These proxy settings only influence your end-user internet access, allowing the Azure Virtual Desktop platform outbound traffic directly via Azure Firewall.
62
90
63
91
## Control user access to the web
64
92
65
93
Admins can allow or deny user access to different website categories. Add a rule to your Application Collection from your specific IP address to web categories you want to allow or deny. Review all the [web categories](web-categories.md).
66
94
67
-
## Additional considerations
68
-
69
-
You might need to configure additional firewall rules, depending on your requirements:
70
-
71
-
- NTP server access
72
-
73
-
By default, virtual machines running Windows connect to `time.windows.com` over UDP port 123 for time synchronization. Create a network rule to allow this access, or for a time server that you use in your environment.
74
-
75
95
## Next steps
76
96
77
97
- Learn more about Azure Virtual Desktop: [What is Azure Virtual Desktop?](../virtual-desktop/overview.md)
0 commit comments