Merge pull request #264489 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: Taojunshen

articles/azure-arc/servers/ssh-arc-troubleshoot.md

@@ -120,6 +120,15 @@ Resolution:
 - Confirm success by running ```az provider show -n Microsoft.HybridConnectivity```, verify that `registrationState` is set to `Registered`
 - Restart the hybrid agent on the Arc-enabled server
 
+### Cannot connect after updating CLI tool and Arc agent
+
+This issue occurs when the updated command creates a new service configuration before the Arc agent is updated. This will only impact Azure Arc versions older than 1.31 when updating to a version 1.31 or newer. Error:
+
+- Connection closed by UNKNOWN port 65535
+
+  Resolution:
+
+  - Delete the existing service configuration and allow it to be re-created by the CLI command at the next connection. Run ```az rest --method delete --uri https://management.azure.com/subscriptions/<SUB_ID>/resourceGroups/<RG_NAME>/providers/Microsoft.HybridCompute/machines/<VM_NAME>/providers/Microsoft.HybridConnectivity/endpoints/default/serviceconfigurations/SSH?api-version=2023-03-15```
 
  ## Disable SSH to Arc-enabled servers
 

articles/azure-monitor/alerts/alerts-troubleshoot.md

@@ -150,14 +150,15 @@ If you can see a fired alert in the portal, but its configured action did not tr
 
     1. **Did your webhook become unresponsive or return errors?** 
 
-        The webhook response timeout period is 10 seconds. When the HTTP endpoint does not respond or when the following HTTP status codes are returned, the webhook call is retried up to two times:
-        
-    - `408`
-    -  `429`
-    - `503`
-    - `504`
-   
-        One retry occurs after 10 seconds and another retry occurs after 100 seconds. If the second retry fails, the endpoint is not called again for 15 minutes for any action group.
+        Webhook action groups generally follow these rules when called:
+        - When a webhook is invoked, if the first call fails, it is retried at least 1 more time, and up to 5 times (5 retries) at various delay intervals (5, 20, 40 seconds).
+            - The delay between 1st and 2nd attempt is 5 seconds
+            - The delay between 2nd and 3rd attempt is 20 seconds
+            - The delay between 3rd and 4th attempt is 5 seconds
+            - The delay between 4th and 5th attempt is 40 seconds
+            - The delay between 5th and 6th attempt is 5 seconds
+        - After retries attempted to call the webhook fail, no action group calls the endpoint for 15 minutes.
+        - The retry logic assumes that the call can be retried. The status codes: 408, 429, 503, 504, or `HttpRequestException`, `WebException`, or `TaskCancellationException` allow for the call to be retried.
 
 ## Action or notification happened more than once 
 

articles/azure-sql-edge/high-availability-sql-edge-containers.md

@@ -41,7 +41,7 @@ To create a container in Kubernetes, see [Deploy a Azure SQL Edge container in K
 ## Next steps
 
 To deploy Azure SQL Edge containers in Azure Kubernetes Service (AKS), see the following articles:
-- [Deploy a Azure SQL Edge container in Kubernetes](deploy-Kubernetes.md)
+- [Deploy an Azure SQL Edge container in Kubernetes](deploy-Kubernetes.md)
 - [Machine Learning and Artificial Intelligence with ONNX in SQL Edge](onnx-overview.md).
 - [Building an end to end IoT Solution with SQL Edge using IoT Edge](tutorial-deploy-azure-resources.md).
 - [Data Streaming in Azure SQL Edge](stream-data.md)

articles/dms/howto-sql-server-to-azure-sql-managed-instance-powershell-offline.md

@@ -41,7 +41,7 @@ To complete these steps, you need:
 * To enable the TCP/IP protocol, which is disabled by default with SQL Server Express installation. Enable the TCP/IP protocol by following the article [Enable or Disable a Server Network Protocol](/sql/database-engine/configure-windows/enable-or-disable-a-server-network-protocol#SSMSProcedure).
 * To configure your [Windows Firewall for database engine access](/sql/database-engine/configure-windows/configure-a-windows-firewall-for-database-engine-access).
 * An Azure subscription. If you don't have one, [create a free account](https://azure.microsoft.com/free/) before you begin.
-* A SQL Managed Instance. You can create a SQL Managed Instance by following the detail in the article [Create a ASQL Managed Instance](/azure/azure-sql/managed-instance/instance-create-quickstart).
+* A SQL Managed Instance. You can create a SQL Managed Instance by following the detail in the article [Create an Azure SQL Managed Instance](/azure/azure-sql/managed-instance/instance-create-quickstart).
 * To download and install [Data Migration Assistant](https://www.microsoft.com/download/details.aspx?id=53595) v3.3 or later.
 * A Microsoft Azure Virtual Network created using the Azure Resource Manager deployment model, which provides the Azure Database Migration Service with site-to-site connectivity to your on-premises source servers by using either [ExpressRoute](../expressroute/expressroute-introduction.md) or [VPN](../vpn-gateway/vpn-gateway-about-vpngateways.md).
 * A completed assessment of your on-premises database and schema migration using Data Migration Assistant, as described in the article [Performing a SQL Server migration assessment](/sql/dma/dma-assesssqlonprem).
@@ -113,7 +113,7 @@ $sourceConnInfo = New-AzDmsConnInfo -ServerType SQL `
   -TrustServerCertificate:$true
 ```
 
-The next example shows creation of Connection Info for a Azure SQL Managed Instance named ‘targetmanagedinstance’:
+The next example shows creation of Connection Info for an Azure SQL Managed Instance named ‘targetmanagedinstance’:
 
 ```powershell
 $targetResourceId = (Get-AzSqlInstance -Name "targetmanagedinstance").Id
@@ -180,7 +180,7 @@ $backupFileShare = New-AzDmsFileShare -Path $backupFileSharePath -Credential $ba
 
 The next step is to select the source and target databases by using the `New-AzDmsSelectedDB` cmdlet.
 
-The following example is for migrating a single database from SQL Server to a Azure SQL Managed Instance:
+The following example is for migrating a single database from SQL Server to an Azure SQL Managed Instance:
 
 ```powershell
 $selectedDbs = @()
@@ -190,7 +190,7 @@ $selectedDbs += New-AzDmsSelectedDB -MigrateSqlServerSqlDbMi `
   -BackupFileShare $backupFileShare `
 ```
 
-If an entire SQL Server instance needs a lift-and-shift into a Azure SQL Managed Instance, then a loop to take all databases from the source is provided below. In the following example, for $Server, $SourceUserName, and $SourcePassword, provide your source SQL Server details.
+If an entire SQL Server instance needs a lift-and-shift into an Azure SQL Managed Instance, then a loop to take all databases from the source is provided below. In the following example, for $Server, $SourceUserName, and $SourcePassword, provide your source SQL Server details.
 
 ```powershell
 $Query = "(select name as Database_Name from master.sys.databases where Database_id>4)";

articles/event-grid/push-delivery-overview.md

@@ -82,7 +82,7 @@ The following articles provide you with information on how to use Event Grid or
 
 - [Learn about System Topics](system-topics.md)
 - [Learn about Partner Topics](partner-events-overview.md)
-- [Learn bout Event Domains](event-domains.md)
+- [Learn about Event Domains](event-domains.md)
 - [Learn about event handlers](event-handlers.md)
 - [Learn about event filtering](event-filtering.md)
 - [Publish and subscribe using custom topics](custom-event-quickstart-portal.md).

articles/networking/nva-accelerated-connections.md

@@ -69,6 +69,8 @@ This list will be updated as more regions become available. The following region
 * West US
 * East US 2
 * Central US
+* South UK
+* West Europe
 
 ## Supported SKUs
 

articles/service-fabric/service-fabric-tutorial-create-vnet-and-linux-cluster.md

@@ -104,7 +104,6 @@ The following is a template snippet for the Service Fabric Linux extension:
          "durabilityLevel": "Silver",
          "enableParallelJobs": true,
          "nicPrefixOverride": "[variables('subnet0Prefix')]",
-         "dataPath": "D:\\\\SvcFab",
          "certificate": {
            "commonNames": [
              "[parameters('certificateCommonName')]"

articles/virtual-desktop/install-windows-client-per-user.md

@@ -9,7 +9,7 @@ ms.author: daknappe
 
 # Install the Remote Desktop client for Windows on a per-user basis with Intune or Configuration Manager
 
-You can install the [Remote Desktop client for Windows](./users/connect-windows.md) on either a per-system or per-user basis. Installing it on a per-system basis installs the client on the machines for all users by default, and administrators control updates. Per-user installation installs the application to a subfolder within the local AppData folder of each user's profile, enabling users to install updates with needing administrative rights.
+You can install the [Remote Desktop client for Windows](./users/connect-windows.md) on either a per-system or per-user basis. Installing it on a per-system basis installs the client on the machines for all users by default, and administrators control updates. Per-user installation installs the application to a subfolder within the local AppData folder of each user's profile, enabling users to install updates without needing administrative rights.
 
 When you install the client using `msiexec.exe`, per-system is the default method of client installation. You can use the parameters `ALLUSERS=2 MSIINSTALLPERUSER=1` with `msiexec` to install the client per-user, however if you're deploying the client with Intune or Configuration Manager, using `msiexec` directly to install the client causes it to be installed per-system, regardless of the parameters used. Wrapping the `msiexec` command in a PowerShell script enables the client to be successfully installed per-user.
 

articles/virtual-machines/linux/disk-encryption-key-vault-aad.md

@@ -92,7 +92,7 @@ When you need encryption to be enabled on a running VM in Azure, Azure Disk Encr
 
 
 ### <a name="bkmk_ADappPSH"></a> Set up a Microsoft Entra app and service principal with Azure PowerShell
-To execute the following commands, get and use the [Azure PowerShell module](/powershell/azure/what-is-azure-powershell).https://learn.microsoft.com/en-us/powershell/azure/what-is-azure-powershell?view=azps-11.2.0
+To execute the following commands, get and use the [Azure PowerShell module](/powershell/azure/what-is-azure-powershell).
 
 1. Use the [New-AzADApplication](/powershell/module/az.resources/new-azadapplication) PowerShell cmdlet to create a Microsoft Entra application. MyApplicationHomePage and the MyApplicationUri can be any values you wish.