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

Author: roygara

articles/api-management/api-management-howto-deploy-multi-region.md

@@ -5,7 +5,7 @@ description: Learn how to deploy a Premium tier Azure API Management instance to
 author: dlepow
 ms.service: api-management
 ms.topic: how-to
-ms.date: 01/26/2023
+ms.date: 01/26/2024
 ms.author: danlep
 ---
 
@@ -125,12 +125,15 @@ Under some conditions, you might need to temporarily disable routing to one of t
 * To redirect traffic to other regions during a planned disaster recovery drill that simulates an unavailable region, or during a regional failure 
 
 To disable routing to a regional gateway in your API Management instance, update the gateway's `disableGateway` property value to `true`. You can set the value using the [Create or update service](/rest/api/apimanagement/current-ga/api-management-service/create-or-update) REST API, the [az apim update](/cli/azure/apim#az-apim-update) command in the Azure CLI, the [set-azapimanagement](/powershell/module/az.apimanagement/set-azapimanagement) Azure PowerShell cmdlet, or other Azure tools.
+
+>[!NOTE]
+> You can only disable routing to a regional gateway when you are using API Management's default routing, not a custom routing solution. 
 
 To disable a regional gateway using the Azure CLI:
 
 1. Use the [az apim show](/cli/azure/apim#az-apim-show) command to show the locations, gateway status, and regional URLs configured for the API Management instance. 
     ```azurecli
-    az apim show --name contoso --resource-group myResourceGroup \
+    az apim show --name contoso --resource-group apim-hello-world-resource \
         --query "additionalLocations[].{Location:location,Disabled:disableGateway,Url:gatewayRegionalUrl}" \
         --output table
     ```
@@ -144,7 +147,7 @@ To disable a regional gateway using the Azure CLI:
     ```
 1. Use the [az apim update](/cli/azure/apim#az-apim-update) command to disable the gateway in an available location, such as West US 2.
     ```azurecli
-    az apim update --name contoso --resource-group myResourceGroup \
+    az apim update --name contoso --resource-group apim-hello-world-resource \
     --set additionalLocations[location="West US 2"].disableGateway=true
     ```
 

articles/azure-arc/resource-bridge/system-requirements.md

@@ -175,7 +175,7 @@ By default, these files are generated in the current CLI directory when `createc
 
 ### Kubeconfig
 
-The appliance VM hosts a management Kubernetes cluster. The kubeconfig is a low-privilege Kubernetes configuration file that is used to maintain the appliance VM. By default, it's generated in the current CLI directory when the `deploy` command completes. The kubeconfig should be saved in a secure location to the management machine, because it's required for maintaining the appliance VM. 
+The appliance VM hosts a management Kubernetes cluster. The kubeconfig is a low-privilege Kubernetes configuration file that is used to maintain the appliance VM. By default, it's generated in the current CLI directory when the `deploy` command completes. The kubeconfig should be saved in a secure location on the management machine, because it's required for maintaining the appliance VM. If the kubeconfig is lost, it can be retrieved by running the `az arcappliance get-credentials` command.
 
 ### HCI login configuration file (Azure Stack HCI only)
 

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/mqtt-automotive-connectivity-and-data-solution.md

@@ -4,7 +4,7 @@ description: 'Describes the use case of automotive messaging'
 ms.topic: conceptual
 ms.custom:
   - ignite-2023
-ms.date: 11/15/2023
+ms.date: 01/29/2024
 author: msmarioo
 ms.author: marioo
 ms.subservice: mqtt
@@ -286,7 +286,7 @@ Other contributors:
 * [Jeff Beman](https://www.linkedin.com/in/jeff-beman-4730726/) | Principal Program Manager, Mobility CVP
 * [Frederick Chong](https://www.linkedin.com/in/frederick-chong-5a00224) | Principal PM Manager, MCIGET SDV & Mobility
 * [Felipe Prezado](https://www.linkedin.com/in/filipe-prezado-9606bb14) | Principal Program Manager, MCIGET SDV & Mobility
-* [Ashita Rastogi](https://www.linkedin.com/in/ashitarastogi/) | Principal Program Manager, Azure Messaging
+* Ashita Rastogi | Lead Principal Program Manager, Azure Messaging
 * [Henning Rauch](https://www.linkedin.com/in/henning-rauch-adx) | Principal Program Manager, Azure Data Explorer (Kusto)
 * [Rajagopal Ravipati](https://www.linkedin.com/in/rajagopal-ravipati-79020a4/) | Partner Software Engineering Manager, Azure Messaging
 * [Larry Sullivan](https://www.linkedin.com/in/larry-sullivan-1972654/) | Partner Group Software Engineering Manager, Energy & CVP

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