Merge pull request #310356 from MicrosoftDocs/main

Auto Publish – main to live - 2026-01-12 06:00 UTC

Author: learn-build-service-prod[bot]

articles/backup/backup-support-matrix-iaas.md

@@ -65,7 +65,7 @@ The following table summarizes the supported operating systems when you're backi
 
 **Scenario** | **OS support**
 --- | ---
-Back up with the Azure VM agent extension for application-consistent backup | - Windows 11 client (64 bit only) <br/><br/> - Windows 10 client (64 bit only) <br/><br/>- Windows Server 2025 (Datacenter, Datacenter Core, and Standard)  <br/><br/>- Windows Server 2022 (Datacenter, Datacenter Core, and Standard)   <br/><br/>- Windows Server 2019 (Datacenter, Datacenter Core, and Standard) <br/><br/> - Windows Server 2016 (Datacenter, Datacenter Core, and Standard) <br/><br/> *Note: Support for backup of Azure VMs running Windows Server 2012 R2 and earlier is limited. Issues related to the Azure Windows VM Agent are not supported, as the agent is [no longer supported](/azure/virtual-machines/extensions/agent-windows#prerequisites) on these operating systems.* <br/><br/> - Windows Server 2012 R2 (Datacenter and Standard) <br/><br/> - Windows Server 2012 (Datacenter and Standard) <br/><br/> - Windows Server 2008 R2 (RTM and SP1 Standard)  <br/><br/> - Windows Server 2008 (64 bit only) <br><br> Note that *32 bit Operating Systems* aren't supported.
+Back up with the Azure VM agent extension for application-consistent backup | - Windows 11 client (64 bit only) <br/><br/> - Windows 10 client (64 bit only) <br/><br/>- Windows Server 2025 (Datacenter, Datacenter Core, and Standard)  <br/><br/>- Windows Server 2022 (Datacenter, Datacenter Core, and Standard)   <br/><br/>- Windows Server 2019 (Datacenter, Datacenter Core, and Standard) <br/><br/> - Windows Server 2016 (Datacenter, Datacenter Core, and Standard) <br><br> Note that *32 bit Operating Systems* aren't supported.
 [Back up Azure VM directly using agentless crash-consistent backup](backup-azure-vms-agentless-multi-disk-crash-consistent-overview.md) | Agentless crash-consistent backups are operating system agnostic. 
 Back up with the MARS agent | [Supported](backup-support-matrix-mars-agent.md#supported-operating-systems) operating systems
 Back up with DPM or MABS | Supported operating systems for backup with [MABS](backup-mabs-protection-matrix.md) and [DPM](/system-center/dpm/dpm-protection-matrix)

articles/oracle/oracle-db/faq-oracle-database-azure.md

@@ -141,9 +141,9 @@ This section includes questions related to networking for Oracle Database@Azure.
 
 We support a comprehensive list of connectivity patterns and network features for Oracle Database@Azure. The list evolves as we continuously release new features and capabilities. For more information, see [Network planning for Oracle Database@Azure](oracle-database-network-plan.md).
 
-### How does Data Guard route traffic between availability zones in the same Azure region work?
+### How does Data Guard route traffic between availability zones in the same Azure region or in cross region work?
 
-You can configure an Oracle Data Guard network path when you set up your deployment. You can configure *cross-zone* Data Guard traffic to traverse only the Azure backbone. However, *cross-region* traffic must traverse the Azure and OCI network backbones.
+While configuring Oracle Data Guard, you can route network traffic through either the Azure or OCI backbone including cross-zone and cross-region connectivity. For cross-region configurations, enable advanced networking features and utilize cross-region VNet peering to ensure that Data Guard traffic exclusively traverses the Azure backbone.
 
 ### What is the latency impact of using OCI connections?
 

articles/synapse-analytics/sql/overview-architecture.md

@@ -69,8 +69,6 @@ In serverless SQL pool, each Compute node is assigned task and set of files to e
 
 Data Movement Service (DMS) is the data transport technology in dedicated SQL pool that coordinates data movement between the Compute nodes. Some queries require data movement to ensure the parallel queries return accurate results. When data movement is required, DMS ensures the right data gets to the right location.
 
-> [!VIDEO https://www.youtube.com/embed/PlyQ8yOb8kc]
-
 ## Distributions
 
 A distribution is the basic unit of storage and processing for parallel queries that run on distributed data in dedicated SQL pool. When dedicated SQL pool runs a query, the work is divided into 60 smaller queries that run in parallel.

articles/virtual-wan/pricing-concepts.md

@@ -46,8 +46,8 @@ The following diagram shows the typical data routes in a network involving Virtu
 |4|Data transfer from a spoke VNet to ExpressRoute connected Data Center/ HQ via Standard vWAN hub in East US|Deployment hour ($0.25/hr) + ExpressRoute Scale Unit ($0.42/hr) + ExpressRoute Connection Unit ($0.05/hr) = $0.72/hr|VNet peering (outbound) ($0.01/GB) + ExpressRoute Metered Outbound Zone 1 ($0.025/GB) = $0.035/GB|
 |4'|Data transfer from ExpressRoute connected Data Center/ HQ to a spoke VNet via Standard vWAN hub in East US|Deployment hour ($0.25/hr) + ExpressRoute Scale Unit ($0.42/hr) + ExpressRoute Connection Unit ($0.05/hr) = $0.72/hr|VNet peering (inbound) ($0.01/GB) = $0.01/GB|
 |4"|Data transfer from ExpressRoute connected Data Center/ HQ to a remote spoke VNet via Standard vWAN hub in Europe|Deployment hour (2x$0.25/hr) + ExpressRoute Scale Unit ($0.42/hr) + ExpressRoute Connection Unit ($0.05/hr) = $0.97/hr|VNet peering (inbound) ($0.01/GB) + hub Data Processing (Europe) ($0.02/GB) + Inter-Region data transfer (East US to Europe) ($0.05/GB) = $0.08/GB|
-|5|Data transfer from a spoke VNet to another spoke VNet via Standard vWAN hub in East US|Deployment hour ($0.25/hr) = $0.25/hr|VNet peering (outbound + inbound) (2x$0.01/GB) + hub Data Processing ($0.02/GB) = $0. 04/GB|
-|6|Data transfer from a spoke VNet connected to a hub in East US to another spoke VNet in Europe (a different region) that is connected to a hub in Europe|Deployment hour (2x$0.25/hr) = $0.50/hr|VNet peering (outbound + inbound) (2x$0.01/GB) + hub Data Processing (2x$0.02/GB) + Inter-Region data transfer (East US to Europe) ($0.05/GB) = $0. 11/GB|
+|5|Data transfer from a spoke VNet to another spoke VNet via Standard vWAN hub in East US|Deployment hour ($0.25/hr) = $0.25/hr|VNet peering (outbound + inbound) (2x$0.01/GB) + hub Data Processing ($0.02/GB) = $0.04/GB|
+|6|Data transfer from a spoke VNet connected to a hub in East US to another spoke VNet in Europe (a different region) that is connected to a hub in Europe|Deployment hour (2x$0.25/hr) = $0.50/hr|VNet peering (outbound + inbound) (2x$0.01/GB) + hub Data Processing (2x$0.02/GB) + Inter-Region data transfer (East US to Europe) ($0.05/GB) = $0.11/GB|
 |7|Data transfer from a spoke VNet to a User VPN (Point-to-Site) via Standard vWAN hub in Europe|Deployment hour ($0.25/hr) + VPN P2S Scale Unit ($0.261/hr) + VPN P2S Connection Unit ($0.0125/hr) = $0.524/hr|VNet peering (outbound) ($0.01/GB) + Standard Outbound Zone 1 ($0.087/GB) = $0.097/GB|
 |7'|Data transfer from a User VPN (Point-to-Site) to a spoke VNet via Standard vWAN hub in Europe|Deployment hour ($0.25/hr) + VPN P2S Scale Unit ($0.261/hr) + VPN P2S Connection Unit ($0.0125/hr) = $0.524/hr|VNet peering (inbound) ($0.01/GB) = $0.01/GB|
 |8|Data transfer from an SD-WAN branch via Network Virtual Appliance in hub in Singapore to another SD-WAN branch in the same region|Standard vWAN hub Deployment hour ($0.25/hr) + NVA Infrastructure Unit ($0.25/hr) = $0.50/hr<br> *Additional third-party licensing charges may apply|Standard Outbound Zone 2 ($0.12/GB) = $0.12/GB|
@@ -187,4 +187,4 @@ Virtual WAN comes in two flavors:
 
 * For current pricing, see [Virtual WAN pricing](https://azure.microsoft.com/pricing/details/virtual-wan/).
 
-* For more information about Virtual WAN, see the [FAQ](virtual-wan-faq.md).
+* For more information about Virtual WAN, see the [FAQ](virtual-wan-faq.md).