Skip to content

Commit 6aedf23

Browse files
authored
Merge pull request #174450 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to master to sync with https://github.com/MicrosoftDocs/azure-docs (branch master)
2 parents 1ea04ce + 840a2ed commit 6aedf23

File tree

4 files changed

+17
-19
lines changed

4 files changed

+17
-19
lines changed

articles/active-directory-b2c/configure-authentication-sample-angular-spa-app.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,7 @@ Before you follow the procedures in this article, make sure that your computer i
5959

6060
* [Visual Studio Code](https://code.visualstudio.com/) or another code editor.
6161
* [Node.js runtime](https://nodejs.org/en/download/) and [npm](https://docs.npmjs.com/downloading-and-installing-node-js-and-npm).
62-
* [Angular LCI](https://angular.io/cli).
62+
* [Angular CLI](https://angular.io/cli).
6363

6464
## Step 1: Configure your user flow
6565

articles/firewall/protect-azure-virtual-desktop.md

Lines changed: 14 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -19,9 +19,8 @@ Follow the guidelines in this article to provide additional protection for your
1919

2020
## Prerequisites
2121

22-
2322
- 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
2524

2625
For more information, see [Tutorial: Create a host pool by using the Azure portal](../virtual-desktop/create-host-pools-azure-marketplace.md)
2726

@@ -31,26 +30,25 @@ To learn more about Azure Virtual Desktop environments see [Azure Virtual Deskto
3130

3231
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:
3332

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.
3534

3635
### Create network rules
3736

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 |
38+
| --------- | ----------- | ------------------------- | -------- | ----------------- | ---------------- | --------------------------------- |
39+
| 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 | * |
4342

4443
> [!NOTE]
4544
> 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.
4645
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
5347

48+
| Name | Source type | Source | Protocol | Destination type | Destination |
49+
| --------- | ----------- | ------------------------- | ---------- | ---------------- | ------------------------------------------------------------------------------------------- |
50+
| 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 |
5452

5553
> [!IMPORTANT]
5654
> 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
5957

6058
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).
6159

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.
6361

6462
## Control user access to the web
6563

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).
6765

6866
## Additional considerations
6967

articles/governance/resource-graph/concepts/query-language.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ properties from related resource types. Here is the list of tables available in
3434
|DesktopVirtualizationResources |Yes |Includes resources _related_ to `Microsoft.DesktopVirtualization`. |
3535
|ExtendedLocationResources |No |Includes resources _related_ to `Microsoft.ExtendedLocation`. |
3636
|GuestConfigurationResources |No |Includes resources _related_ to `Microsoft.GuestConfiguration`. |
37-
|HealthResources|Yes |Includes resources _related_ to `Microsoft.ResourceHealth/availabilitystatuses`. |
37+
|HealthResources|Yes (preview) |Includes resources _related_ to `Microsoft.ResourceHealth/availabilitystatuses`. |
3838
|IoTSecurityResources |No |Includes resources _related_ to `Microsoft.IoTSecurity`. |
3939
|KubernetesConfigurationResources |No |Includes resources _related_ to `Microsoft.KubernetesConfiguration`. |
4040
|MaintenanceResources |Partial, join _to_ only. (preview) |Includes resources _related_ to `Microsoft.Maintenance`. |

articles/synapse-analytics/sql-data-warehouse/backup-and-restore.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ A geo-backup is created once per day to a [paired data center](../../best-practi
6969
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.
7070

7171
> [!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.
7373
7474
## Data residency
7575

0 commit comments

Comments
 (0)