Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into Exrlegacy

MekaylaMoore · MekaylaMoore · commit 2a96d3adf214 · 2025-02-13T12:18:19.000-08:00
diff --git a/articles/data-factory/connector-google-adwords.md b/articles/data-factory/connector-google-adwords.md
@@ -7,7 +7,7 @@ author: jianleishen
 ms.subservice: data-movement
 ms.topic: conceptual
 ms.custom: synapse
-ms.date: 05/06/2024
+ms.date: 02/13/2025
 ---
 
 # Copy data from Google Ads using Azure Data Factory or Synapse Analytics
@@ -324,8 +324,6 @@ Upgrade your Google AdWords linked service to the latest Google Ads linked servi
         | USER_AD_DISTANCE_REPORT | distance_view |  
         | VIDEO_PERFORMANCE_REPORT | video | 
 
-    1. If the pipeline is using query to retrieve data from Google AdWords, use [Query Migration tool](https://developers.google.com/google-ads/scripts/docs/reference/query-migration-tool) to translate the AWQL (AdWords Query Language) into GAQL (Google Ads Query Language). 
-
 1. Be aware that there are certain limitations with this upgrade: 
     1. Not all report types from AWQL are supported in GAQL. 
     1. Not all AWQL queries are cleanly translated to GAQL queries.  
diff --git a/articles/data-factory/self-hosted-integration-runtime-proxy-ssis.md b/articles/data-factory/self-hosted-integration-runtime-proxy-ssis.md
@@ -57,7 +57,7 @@ Finally, you download and install the latest version of self-hosted IR, as well
 
   If you use the earlier version of the OLEDB driver for SQL Server (SQL Server Native Client [SQLNCLI]), [download the 64-bit version](https://www.microsoft.com/download/details.aspx?id=50402).  
 
-  If you use the latest version of OLEDB driver for SQL Server (MSOLEDBSQL), [download the 64-bit version](https://www.microsoft.com/download/details.aspx?id=56730).  
+  If you use the latest version of OLEDB driver for SQL Server (MSOLEDBSQL), [download the 64-bit version](https://go.microsoft.com/fwlink/?linkid=2278038).  
   
   If you use OLEDB/ODBC/ADO.NET drivers for other database systems, such as PostgreSQL, MySQL, Oracle, and so on, you can download the 64-bit versions from their websites.
 - If you use data flow components from Azure Feature Pack in your packages, [download and install Azure Feature Pack for SQL Server 2017](https://www.microsoft.com/download/details.aspx?id=54798) on the same machine where your self-hosted IR is installed, if you haven't done so already.
diff --git a/articles/data-factory/tutorial-incremental-copy-multiple-tables-powershell.md b/articles/data-factory/tutorial-incremental-copy-multiple-tables-powershell.md
@@ -225,7 +225,7 @@ END
 
 ### Azure PowerShell
 
-Install the latest Azure PowerShell modules by following the instructions in [Install and configure Azure PowerShell](/powershell/azure/azurerm/install-azurerm-ps).
+Install the latest Azure PowerShell modules by following the instructions in [Install and configure Azure PowerShell](/powershell/azure/install-azure-powershell).
 
 ## Create a data factory
 
diff --git a/articles/iot-operations/connect-to-cloud/howto-create-dataflow.md b/articles/iot-operations/connect-to-cloud/howto-create-dataflow.md
@@ -677,7 +677,7 @@ You can use the **Compute** transform to apply a formula to the source data. Thi
     | Last known value   | Optionally, use the last known value if the current value isn't available.                       |
 
 
-    You can enter or edit a formula in the **Formula** field. The formula can use the fields in the source data. Enter `@` or select **Ctrl + Space** to choose datapoints from a dropdown.
+    You can enter or edit a formula in the **Formula** field. The formula can use the fields in the source data. Enter `@` or select **Ctrl + Space** to choose datapoints from a dropdown. For built-in formulas, select the `<dataflow>` placeholder to see the list of available datapoints.
 
     You can enter MQTT metadata properties using the format `@$metadata.user_properties.<property>` or `@$metadata.topic`. You can also enter $metadata headers using the format `@$metadata.<header>`. The `$metadata` syntax is only needed for MQTT properties that are part of the message header. For more information, see [field references](concept-dataflow-mapping.md#field-references).
 
@@ -701,11 +701,8 @@ You can rename a datapoint using the **Rename** transform. This operation is use
     | New datapoint name | Enter the new name for the datapoint.                                                                   |
     | Description        | Provide a description for the transformation.                                                           |
 
-    Enter `@` or select **Ctrl + Space** to choose datapoints from a dropdown.
-
     You can enter MQTT metadata properties using the format `@$metadata.user_properties.<property>` or `@$metadata.topic`. You can also enter $metadata headers using the format `@$metadata.<header>`. The `$metadata` syntax is only needed for MQTT properties that are part of the message header. For more information, see [field references](concept-dataflow-mapping.md#field-references).
 
-
 1. Select **Apply**.
 
 #### New property
diff --git a/articles/load-balancer/TOC.yml b/articles/load-balancer/TOC.yml
@@ -60,11 +60,11 @@
       href: tutorial-load-balancer-standard-public-zonal-portal.md
     - name: Load balance VMs with multiple availability sets
       href: tutorial-multi-availability-sets-portal.md
-  - name: Cross-region load balancer
+  - name: Globalload balancer
     items:
-    - name: Create cross-region load balancer - Portal
+    - name: Create global load balancer - Portal
       href: tutorial-cross-region-portal.md
-    - name: Deploy cross-region load balancer - ARM template
+    - name: Deploy global load balancer - ARM template
       href: tutorial-deploy-cross-region-load-balancer-template.md
   - name: Gateway load balancer
     items:
@@ -108,13 +108,13 @@
     href: load-balancer-custom-probe-overview.md
   - name: Cross-subscription load balancer
     href: cross-subscription-overview.md
-  - name: Cross-region load balancer
+  - name: Global load balancer
     href: cross-region-overview.md
   - name: Administrative state
     href: admin-state-overview.md
   - name: Reliability
     items:
-    - name: Availability zones and cross-region load balancer
+    - name: Availability zones and global load balancer
       href: ../reliability/reliability-load-balancer.md?toc=/azure/load-balancer/toc.json&bc=/azure/load-balancer/breadcrumb/toc.json
     - name: Availability zone migration
       href: ../reliability/migrate-load-balancer.md?toc=/azure/load-balancer/toc.json&bc=/azure/load-balancer/breadcrumb/toc.json
diff --git a/articles/load-balancer/cross-region-overview.md b/articles/load-balancer/cross-region-overview.md
@@ -1,7 +1,7 @@
 ---
-title: Cross-region load balancer
+title: Global load balancer
 titleSuffix: Azure Load Balancer
-description: Overview of cross region load balancer tier for Azure Load Balancer.
+description: Overview of global load balancer tier for Azure Load Balancer.
 services: load-balancer
 author: mbender-ms
 ms.service: azure-load-balancer
@@ -13,7 +13,7 @@ ms.custom: references_regions
 
 # Global Load Balancer
 
-Azure Standard Load Balancer supports cross-region load balancing enabling geo-redundant high availability scenarios such as:
+Azure Standard Load Balancer supports global load balancing enabling geo-redundant high availability scenarios such as:
 
 * Incoming traffic originating from multiple regions.
 * [Instant global failover](#regional-redundancy) to the next optimal regional deployment.
diff --git a/articles/load-balancer/tutorial-cross-region-portal.md b/articles/load-balancer/tutorial-cross-region-portal.md
@@ -1,24 +1,24 @@
 ---
-title: 'Tutorial: Create a cross-region load balancer'
+title: 'Tutorial: Create an Azure Global Load Balancer'
 titleSuffix: Azure Load Balancer
-description: Get started with this tutorial deploying a cross-region Azure Load Balancer with the Azure portal, Azure CLI, or Azure PowerShell.
+description: Get started with this tutorial deploying a global Load Balancer with the Azure portal, Azure CLI, or Azure PowerShell.
 author: mbender-ms
 ms.author: mbender
 ms.service: azure-load-balancer
 ms.topic: tutorial
 ms.date: 08/01/2024
 ms.custom: template-tutorial, references_regions
-#Customer intent: As a administrator, I want to deploy a cross-region load balancer for global high availability of my application or service.
+#Customer intent: As a administrator, I want to deploy a global load balancer for global high availability of my application or service.
 ---
 
-# Tutorial: Create a cross-region Azure Load Balancer
+# Tutorial: Create an Azure Global Load Balancer
 
-A cross-region load balancer ensures a service is available globally across multiple Azure regions. If one region fails, the traffic is routed to the next closest healthy regional load balancer.  
+A global load balancer ensures a service is available globally across multiple Azure regions. If one region fails, the traffic is routed to the next closest healthy regional load balancer.  
 
 In this tutorial, you learn how to:
 
 > [!div class="checklist"]
-> * Create cross-region load balancer.
+> * Create global load balancer.
 > * Create a backend pool containing two regional load balancers.
 > * Create a load balancer rule.
 > * Test the load balancer.
@@ -56,9 +56,9 @@ If you choose to install and use PowerShell locally, this article requires the A
 ---
 
 
-## Create cross-region load balancer
+## Create global load balancer
 
-In this section, you create a cross-region load balancer with a public IP address, a frontend IP configuration, a backend pool with region load balancers added, and a load balancer rule.
+In this section, you create a global load balancer with a public IP address, a frontend IP configuration, a backend pool with region load balancers added, and a load balancer rule.
 
 # [Azure portal](#tab/azureportal)
 
@@ -87,7 +87,7 @@ In this section, you create a cross-region load balancer with a public IP addres
     | SKU           | Leave the default of **Standard**. |
     | Tier           | Select **Global** |
 
-    :::image type="content" source="./media/tutorial-cross-region-portal/create-cross-region.png" alt-text="Create a cross-region load balancer" border="true":::
+    :::image type="content" source="./media/tutorial-cross-region-portal/create-cross-region.png" alt-text="Create a global load balancer" border="true":::
   
 5. Select **Next: Frontend IP configuration** at the bottom of the page.
 
@@ -158,9 +158,9 @@ Create a resource group with [az group create](/cli/azure/group#az-group-create)
     --location westus
 ```
 
-### Create the cross-region load balancer resource
+### Create the global load balancer resource
 
-Create a cross-region load balancer with [az network cross-region-lb create](/cli/azure/network/cross-region-lb#az-network-cross-region-lb-create):
+Create a global load balancer with [az network cross-region-lb create](/cli/azure/network/cross-region-lb#az-network-cross-region-lb-create):
 
 * Named **myLoadBalancer-CR**.
 * A frontend pool named **myFrontEnd-CR**.
@@ -203,18 +203,18 @@ Create a load balancer rule with [az network cross-region-lb rule create](/cli/a
 
 ## Create backend pool
 
-In this section, you add two regional standard load balancers to the backend pool of the cross-region load balancer.
+In this section, you add two regional standard load balancers to the backend pool of the global load balancer.
 
 > [!IMPORTANT]
 > To complete these steps, ensure that two regional load balancers with backend pools have been deployed in your subscription.  For more information, see, **[Quickstart: Create a public load balancer to load balance VMs using Azure CLI](quickstart-load-balancer-standard-public-cli.md)**.
 
 ### Add the regional frontends to load balancer
 
-In this section, you place the resource IDs of two regional load balancers frontends into variables, and then use the variables to add the frontends to the backend address pool of the cross-region load balancer.
+In this section, you place the resource IDs of two regional load balancers frontends into variables, and then use the variables to add the frontends to the backend address pool of the global load balancer.
 
 Retrieve the resource IDs with [az network lb frontend-ip show](/cli/azure/network/lb/frontend-ip#az-network-lb-frontend-ip-show).
 
-Use [az network cross-region-lb address-pool address add](/cli/azure/network/cross-region-lb/address-pool/address#az-network-cross-region-lb-address-pool-address-add) to add the frontends you placed in variables in the backend pool of the cross-region load balancer:
+Use [az network cross-region-lb address-pool address add](/cli/azure/network/cross-region-lb/address-pool/address#az-network-cross-region-lb-address-pool-address-add) to add the frontends you placed in variables in the backend pool of the global load balancer:
 
 ```azurecli-interactive
   region1id=$(az network lb frontend-ip show \
@@ -264,11 +264,11 @@ New-AzResourceGroup @rg
 
 ```
 
-### Create cross-region load balancer resources
+### Create global load balancer resources
 
-In this section, you create the resources needed for the cross-region load balancer.
+In this section, you create the resources needed for the global load balancer.
 
-A global standard sku public IP is used for the frontend of the cross-region load balancer.
+A global standard sku public IP is used for the frontend of the global load balancer.
 
 * Use [New-AzPublicIpAddress](/powershell/module/az.network/new-azpublicipaddress) to create the public IP address.
 
@@ -278,7 +278,7 @@ A global standard sku public IP is used for the frontend of the cross-region loa
 
 * Create a load balancer rule with [Add-AzLoadBalancerRuleConfig](/powershell/module/az.network/add-azloadbalancerruleconfig).
 
-* Create a cross-region load Balancer with [New-AzLoadBalancer](/powershell/module/az.network/new-azloadbalancer).
+* Create a global load Balancer with [New-AzLoadBalancer](/powershell/module/az.network/new-azloadbalancer).
 
 ```azurepowershell-interactive
 `## Create global IP address for load balancer ##
@@ -316,7 +316,7 @@ $rul = @{
 }
 $rule = New-AzLoadBalancerRuleConfig @rul
 
-## Create cross-region load balancer resource ##
+## Create global load balancer resource ##
 $lbp = @{
     ResourceGroupName = 'myResourceGroupLB-CR'
     Name = 'myLoadBalancer-CR'
@@ -332,7 +332,7 @@ $lb = New-AzLoadBalancer @lbp`
 
 ## Configure backend pool
 
-In this section, you add two regional standard load balancers to the backend pool of the cross-region load balancer.
+In this section, you add two regional standard load balancers to the backend pool of the global load balancer.
 
 > [!IMPORTANT]
 > To complete these steps, ensure that two regional load balancers with backend pools have been deployed in your subscription.  For more information, see, **[Quickstart: Create a public load balancer to load balance VMs using Azure PowerShell](quickstart-load-balancer-standard-public-powershell.md)**.
@@ -341,7 +341,7 @@ In this section, you add two regional standard load balancers to the backend poo
 
 * Use [New-AzLoadBalancerBackendAddressConfig](/powershell/module/az.network/new-azloadbalancerbackendaddressconfig) to create the backend address pool configuration for the load balancer.
 
-* Use [Set-AzLoadBalancerBackendAddressPool](/powershell/module/az.network/new-azloadbalancerbackendaddresspool) to add the regional load balancer frontend to the cross-region backend pool.
+* Use [Set-AzLoadBalancerBackendAddressPool](/powershell/module/az.network/new-azloadbalancerbackendaddresspool) to add the regional load balancer frontend to the global backend pool.
 
 ```azurepowershell-interactive
  ## Place the region one load balancer configuration in a variable ##
@@ -372,21 +372,21 @@ $region2fe = @{
 }
 $R2FE = Get-AzLoadBalancerFrontendIpConfig @region2fe
 
-## Create the cross-region backend address pool configuration for region 1 ##
+## Create the global backend address pool configuration for region 1 ##
 $region1ap = @{
     Name = 'MyBackendPoolConfig-R1'
     LoadBalancerFrontendIPConfigurationId = $R1FE.Id
 }
 $beaddressconfigR1 = New-AzLoadBalancerBackendAddressConfig @region1ap
 
-## Create the cross-region backend address pool configuration for region 2 ##
+## Create the global backend address pool configuration for region 2 ##
 $region2ap = @{
     Name = 'MyBackendPoolConfig-R2'
     LoadBalancerFrontendIPConfigurationId = $R2FE.Id
 }
 $beaddressconfigR2 = New-AzLoadBalancerBackendAddressConfig @region2ap
 
-## Apply the backend address pool configuration for the cross-region load balancer ##
+## Apply the backend address pool configuration for the global load balancer ##
 $bepoolcr = @{
     ResourceGroupName = 'myResourceGroupLB-CR'
     LoadBalancerName = 'myLoadBalancer-CR'
@@ -402,7 +402,7 @@ Set-AzLoadBalancerBackendAddressPool @bepoolcr
 ## Test the load balancer
 
 # [Azure portal](#tab/azureportal)
-In this section, you test the cross-region load balancer. You connect to the public IP address in a web browser.  You stop the virtual machines in one of the regional load balancer backend pools and observe the failover.
+In this section, you test the global load balancer. You connect to the public IP address in a web browser.  You stop the virtual machines in one of the regional load balancer backend pools and observe the failover.
 
 1. Find the public IP address for the load balancer on the **Overview** screen. Select **All services** in the left-hand menu, select **All resources**, and then select **myPublicIP-cr**.
 
@@ -418,7 +418,7 @@ In this section, you test the cross-region load balancer. You connect to the pub
 
 # [Azure CLI](#tab/azurecli/)
 
-In this section, you test the cross-region load balancer. You connect to the public IP address in a web browser.  You stop the virtual machines in one of the regional load balancer backend pools and observe the failover.
+In this section, you test the global load balancer. You connect to the public IP address in a web browser.  You stop the virtual machines in one of the regional load balancer backend pools and observe the failover.
 
 1. To get the public IP address of the load balancer, use [az network public-ip show](/cli/azure/network/public-ip#az-network-public-ip-show):
 
@@ -437,7 +437,7 @@ In this section, you test the cross-region load balancer. You connect to the pub
 
 # [Azure PowerShell](#tab/azurepowershell/)
 
-In this section, you test the cross-region load balancer. You connect to the public IP address in a web browser.  You stop the virtual machines in one of the regional load balancer backend pools and observe the failover.
+In this section, you test the global load balancer. You connect to the public IP address in a web browser.  You stop the virtual machines in one of the regional load balancer backend pools and observe the failover.
 
 1. Use [Get-AzPublicIpAddress](/powershell/module/az.network/get-azpublicipaddress) to get the public IP address of the load balancer:
 
@@ -487,11 +487,11 @@ Remove-AzResourceGroup -Name 'myResourceGroupLB-CR'
 
 In this tutorial, you:
 
-* Created a cross-region load balancer.
-* Added regional load balancers to the backend pool of the cross-region load balancer.
+* Created a global load balancer.
+* Added regional load balancers to the backend pool of the global load balancer.
 * Created a load-balancing rule.
 * Tested the load balancer.
 
-For more information on cross-region load balancer, see:
+For more information on global load balancer, see:
 > [!div class="nextstepaction"]
-> [Cross-region load balancer (Preview)](cross-region-overview.md)
+> [Global load balancer](cross-region-overview.md)
diff --git a/articles/load-balancer/tutorial-deploy-cross-region-load-balancer-template.md b/articles/load-balancer/tutorial-deploy-cross-region-load-balancer-template.md
diff --git a/articles/reliability/reliability-load-balancer.md b/articles/reliability/reliability-load-balancer.md
