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
Copy file name to clipboardExpand all lines: articles/firewall/protect-azure-virtual-desktop.md
+14-16Lines changed: 14 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,9 +19,8 @@ Follow the guidelines in this article to provide additional protection for your
19
19
20
20
## Prerequisites
21
21
22
-
23
22
- A deployed Azure Virtual Desktop environment and host pool.
24
-
- An Azure Firewall deployed with at least one Firewall Manager Policy
23
+
- An Azure Firewall deployed with at least one Firewall Manager Policy
25
24
26
25
For more information, see [Tutorial: Create a host pool by using the Azure portal](../virtual-desktop/create-host-pools-azure-marketplace.md)
27
26
@@ -31,26 +30,25 @@ To learn more about Azure Virtual Desktop environments see [Azure Virtual Deskto
31
30
32
31
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:
33
32
34
-
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.
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.
35
34
36
35
### Create network rules
37
36
38
-
| Name | Source type | Source | Protocol | Destination ports | Destination type | Destination |
39
-
| --- | --- | --- | --- | --- | --- | --- |
40
-
| Rule Name | IP Address | VNet or Subnet IP Address |80 | TCP |IP Address | 169.254.169.254, 168.63.129.16 |
41
-
| Rule Name | IP Address | VNet or Subnet IP Address |443 | TCP | Service Tag | AzureCloud, WindowsVirtualDesktop |
42
-
| Rule Name | IP Address | VNet or Subnet IP Address |53 |TCP, UDP | IP Address | * |
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 |
41
+
| Rule Name | IP Address | VNet or Subnet IP Address | TCP, UDP |53 |IP Address | *|
43
42
44
43
> [!NOTE]
45
44
> 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.
46
45
47
-
### Create application rules
48
-
49
-
| Name | Source type | Source | Protocol | Destination type | Destination|
50
-
| --- | --- | --- | --- | --- | --- |
51
-
| Rule Name | IP Address | VNet or Subnet IP Address | Https:443 | FQDN Tag | WindowsVirtualDesktop, WindowsUpdate, Windows Diagnostics, MicrosoftActiveProtectionService |
52
-
| Rule Name | IP Address | VNet or Subnet IP Address | Https:1688 | FQDN | kms.core.windows.net |
46
+
### Create application rules
53
47
48
+
| Name | Source type | Source | Protocol | Destination type | Destination |
| Rule Name | IP Address | VNet or Subnet IP Address | Https:443 | FQDN Tag | WindowsVirtualDesktop, WindowsUpdate, Windows Diagnostics, MicrosoftActiveProtectionService |
51
+
| Rule Name | IP Address | VNet or Subnet IP Address | Https:1688 | FQDN | kms.core.windows.net |
54
52
55
53
> [!IMPORTANT]
56
54
> 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).
@@ -59,11 +57,11 @@ You will need to create an Azure Firewall Policy and create Rule Collections for
59
57
60
58
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).
61
59
62
-
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.
60
+
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.
63
61
64
62
## Control user access to the web
65
63
66
-
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).
64
+
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).
Copy file name to clipboardExpand all lines: articles/synapse-analytics/sql-data-warehouse/backup-and-restore.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -69,7 +69,7 @@ A geo-backup is created once per day to a [paired data center](../../best-practi
69
69
If you do not require geo-backups for your dedicated SQL pool, you can disable them and save on disaster recovery storage costs. To do so, refer to [How to guide: Disable geo-backups for a dedicated SQL pool (formerly SQL DW)](disable-geo-backup.md). Note that if you disable geo-backups, you will not be able to recover your dedicated SQL pool to your paired Azure region if your primary Azure data center is unavailable.
70
70
71
71
> [!NOTE]
72
-
> If you require a shorter RPO for geo-backups, vote for this capability [here](https://feedback.azure.com/forums/307516-sql-data-warehouse). You can also create a user-defined restore point and restore from the newly created restore point to a new data warehouse in a different region. Once you have restored, you have the data warehouse online and can pause it indefinitely to save compute costs. The paused database incurs storage charges at the Azure Premium Storage rate. Should you need an active copy of the data warehouse, you can resume which should take only a few minutes.
72
+
> If you require a shorter RPO for geo-backups, vote for this capability [here](https://feedback.azure.com/forums/307516-sql-data-warehouse). You can also create a user-defined restore point and restore from the newly created restore point to a new data warehouse in a different region. After you have restored, you have the data warehouse online and can pause it indefinitely to save compute costs. The paused database incurs storage charges at the Azure Premium Storage rate. Another common pattern for a shorter recovery point is to ingest data into primary and secondary instances of a data warehouse in parallel. In this scenario, data is ingested from a source (or sources) and persisted to two separate instances of the data warehouse (primary and secondary). To save on compute costs, you can pause the secondary instance of the warehouse. If you need an active copy of the data warehouse, you can resume, which should take only a few minutes.
0 commit comments