Merge pull request #292466 from MicrosoftDocs/main

12/30/2024 AM Publish

Author: PhilKang0704

.openpublishing.redirection.json

@@ -4471,6 +4471,11 @@
       "source_path_from_root": "/articles/fasttrack/index.yml",
       "redirect_url": "/azure",
       "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/sentinel/data-connectors/threat-intelligence-upload-indicators-api.md",
+      "redirect_url": "/azure/sentinel/data-connectors/threat-intelligence-upload-api",
+      "redirect_document_id": false
     }
   ]
 }

articles/api-management/azure-openai-enable-semantic-caching.md

@@ -62,7 +62,7 @@ Configure a [backend](backends.md) resource for the embeddings API deployment wi
         https://my-aoai.openai.azure.com/openai/deployments/embeddings-deployment/embeddings
         ```
 * **Authorization credentials** - Go to **Managed Identity** tab.
-  * **Client indentity** - Select *System assigned identity* or type in a User assigned managed identity client ID.
+  * **Client identity** - Select *System assigned identity* or type in a User assigned managed identity client ID.
   * **Resource ID** - Enter `https://cognitiveservices.azure.com/` for Azure OpenAI Service.
 
 ### Test backend 

articles/api-management/migrate-stv1-to-stv2-no-vnet.md

@@ -16,7 +16,7 @@ ms.author: danlep
 
 This article provides steps to migrate an API Management instance hosted on the `stv1` compute platform in-place to the `stv2` platform when the instance *is not* injected (deployed) in an external or internal VNet. For this scenario, migrate your instance using the Azure portal or the [Migrate to stv2](/rest/api/apimanagement/current-ga/api-management-service/migratetostv2) REST API. [Find out if you need to do this](compute-infrastructure.md#how-do-i-know-which-platform-hosts-my-api-management-instance).  
 
-If you need to migrate a *VNnet-injected* API Management hosted on the `stv1` platform, see [Migrate a VNet-injected API Management instance to the stv2 platform](migrate-stv1-to-stv2-vnet.md).
+If you need to migrate a *VNet-injected* API Management hosted on the `stv1` platform, see [Migrate a VNet-injected API Management instance to the stv2 platform](migrate-stv1-to-stv2-vnet.md).
 
 [!INCLUDE [api-management-migration-alert](../../includes/api-management-migration-alert.md)]
 

articles/api-management/migrate-stv1-to-stv2-vnet.md

@@ -27,7 +27,7 @@ For a VNet-inject instance, you have the following migration options:
 
 Under certain, less frequent conditions, migration in the same subnet may not be possible or behaves differently. For more information, see [Special conditions and scenarios](#special-conditions-and-scenarios).
 
-If you need to migrate a *non-VNnet-injected* API Management hosted on the `stv1` platform, see [Migrate a non-VNet-injected API Management instance to the stv2 platform](migrate-stv1-to-stv2-no-vnet.md).
+If you need to migrate a *non-VNet-injected* API Management hosted on the `stv1` platform, see [Migrate a non-VNet-injected API Management instance to the stv2 platform](migrate-stv1-to-stv2-no-vnet.md).
 
 [!INCLUDE [api-management-migration-alert](../../includes/api-management-migration-alert.md)]
 

articles/app-service/tutorial-java-jboss-mysql-app.md

@@ -727,7 +727,7 @@ A few considerations:
 
 #### How do I get a valid access token for the MySQL connection using Microsoft Entra authentication?
 
-For a Microsoft Entra user, a system-assigned managed identity, or a user-asssigned managed identity that's authorized to access the MySQL database, Azure CLI can help you generate an access token. In case of a managed identity, the identity must be configured on the App Service app or VM where you run Azure CLI. 
+For a Microsoft Entra user, a system-assigned managed identity, or a user-assigned managed identity that's authorized to access the MySQL database, Azure CLI can help you generate an access token. In case of a managed identity, the identity must be configured on the App Service app or VM where you run Azure CLI. 
 
 ```azurecli-interactive
 # Sign in as a Microsoft Entra user

articles/application-gateway/configure-application-gateway-with-private-frontend-ip.md

@@ -67,7 +67,7 @@ In this example, you create a new virtual network. You can create a virtual netw
 13. Select **Add**.
 14. Select **Next:Configuration**.
 15. Under **Routing rules**, select **Add a routing rule**.
-16. For **Rule name**, type *Rrule-01*.
+16. For **Rule name**, type *Rule-01*.
 17. For **Listener name**, type *Listener-01*.
 18. For **Frontend IP**, select **Private**.
 19. Accept the remaining defaults and select the **Backend targets** tab.

articles/application-gateway/for-containers/how-to-cert-manager-lets-encrypt-gateway-api.md

@@ -15,7 +15,7 @@ This guide demonstrates how to use cert-manager to automatically issue and renew
 
 For the purposes of this example, we have cert-manager configure certificates issued from Let's Encrypt to demonstrate an end-to-end deployment, where Application Gateway for Containers is providing TLS offloading.
 
-![A figure showing cert-manager retrieving a certificate from Let's Encrypt and storing it into Kubernete's secret store for TLS with Application Gateway for Containers.](./media/how-to-cert-manager-lets-encrypt-gateway-api/how-to-cert-manager-lets-encrypt-gateway-api.svg)
+![A figure showing cert-manager retrieving a certificate from Let's Encrypt and storing it into Kubernetes' secret store for TLS with Application Gateway for Containers.](./media/how-to-cert-manager-lets-encrypt-gateway-api/how-to-cert-manager-lets-encrypt-gateway-api.svg)
 
 For certificates to be issued by Let's Encrypt, a challenge is required by the authority to validate domain ownership. This validation happens by allowing cert-manager to create a pod and HTTPRoute resource that exposes an endpoint during certificate issuance, proving your ownership of the domain name.
 

articles/automanage/how-to-disable-automanage.md

@@ -17,7 +17,7 @@ You may decide one day to disable Automanage on certain VMs. For instance, your
 
 ## How to disable Automanage through the Azure portal
 
-To do that in the Azure portal, go to the **Automanage – Azure machine best practices** page that lists all of your auto-managed VMs. Select the checkbox next to the virtual machine you want to disable from Automanage, then click on the **Disable automanagment** button.
+To do that in the Azure portal, go to the **Automanage – Azure machine best practices** page that lists all of your auto-managed VMs. Select the checkbox next to the virtual machine you want to disable from Automanage, then click on the **Disable automanagement** button.
 
 [ ![Screenshot of disabling Automanage on a virtual machine.](./media/automanage-virtual-machines/disable-step-1.png) ](./media/automanage-virtual-machines/disable-step-1.png#lightbox)
 

articles/automanage/quick-create-virtual-machines-portal.md

@@ -71,7 +71,7 @@ Quickly stop using Azure Automanage for virtual machines by disabling automanage
 
 1. Go to the **Automanage – Azure virtual machine best practices** page that lists all of your auto-managed VMs.
 1. Select the checkbox next to the virtual machine you want to disable.
-1. Click on the **Disable automanagent** button.
+1. Click on the **Disable automanagement** button.
 1. Read carefully through the messaging in the resulting pop-up before agreeing to **Disable**.
 
 

articles/azure-functions/functions-bindings-azure-sql.md

@@ -258,7 +258,7 @@ Azure SQL bindings for Azure Functions have a required property for the connecti
 - This binding requires connectivity to an Azure SQL or SQL Server database.
 - Output bindings against tables with columns of data types `NTEXT`, `TEXT`, or `IMAGE` aren't supported and data upserts will fail. These types [will be removed](/sql/t-sql/data-types/ntext-text-and-image-transact-sql) in a future version of SQL Server and aren't compatible with the `OPENJSON` function used by this Azure Functions binding.
 - Use [managed identities](/azure/azure-sql/database/authentication-azure-ad-user-assigned-managed-identity) instead of usernames and passwords.
-- Concider using an [Azure Key Value](/azure/app-service/app-service-key-vault-references) to store application settings.
+- Consider using an [Azure Key Value](/azure/app-service/app-service-key-vault-references) to store application settings.
 
 ## Samples