Merge pull request #196672 from MicrosoftDocs/main

4/29 PM Publish

Author: huypub

.openpublishing.redirection.json

@@ -24203,6 +24203,21 @@
       "redirect_url": "/azure/sql-database/sql-database-threat-detection-overview",
       "redirect_document_id": false
     },
+    {
+      "source_path_from_root": "/articles/sql-database/sql-database-managed-instance-create-manage",
+      "redirect_url": "/azure/azure-sql/managed-instance/instance-create-quickstart",
+      "redirect_document_id": false
+    },          
+    {
+      "source_path_from_root": "/articles/sql-database/sql-database-single-database.md",
+      "redirect_url": "/azure/azure-sql/database/sql-database-paas-overview",
+      "redirect_document_id": false
+    },  
+    {
+      "source_path_from_root": "/articles/sql-database/sql-database-managed-instance.md",
+      "redirect_url": "/azure/azure-sql/managed-instance/sql-managed-instance-paas-overview",
+      "redirect_document_id": false
+    },
     {
       "source_path_from_root": "/articles/sql-data-warehouse/sql-data-warehouse-backups.md",
       "redirect_url": "/azure/sql-data-warehouse/backup-and-restore",
@@ -42977,6 +42992,16 @@
       "source_path_from_root": "/articles/cognitive-services/video-indexer/video-indexer-view-edit.md",
       "redirect_url": "/azure/azure-video-analyzer/video-analyzer-for-media-docs/video-indexer-view-edit",
       "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/cognitive-services/translator/translator-how-to-signup.md",
+      "redirect_url": "/azure/cognitive-services/translator/how-to-create-translator-resource",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/cognitive-services/translator/custom-translator/terminology.md",
+      "redirect_url": "/azure/cognitive-services/translator/custom-translator/key-terms",
+      "redirect_document_id": false
     }
   ]
 }

articles/active-directory/develop/msal-v1-app-scopes.md

@@ -62,7 +62,7 @@ The logic used by Azure AD is the following:
 
 - For ADAL (Azure AD v1.0) endpoint with a v1.0 access token (the only possible), aud=resource
 - For MSAL (Microsoft identity platform) asking an access token for a resource accepting v2.0 tokens, `aud=resource.AppId`
-- For MSAL (v2.0 endpoint) asking an access token for a resource that accepts a v1.0 access token (which is the case above), Azure AD parses the desired audience from the requested scope by taking everything before the last slash and using it as the resource identifier. Therefore, if `https://database.windows.net` expects an audience of `https://database.windows.net`, you'll need to request a scope of `https://database.windows.net//.default`. See also GitHub issue [#747: `Resource url's trailing slash is omitted, which caused sql auth failure`](https://github.com/AzureAD/microsoft-authentication-library-for-dotnet/issues/747).
+- For MSAL (v2.0 endpoint) asking an access token for a resource that accepts a v1.0 access token (which is the case above), Azure AD parses the desired audience from the requested scope by taking everything before the last slash and using it as the resource identifier. Therefore, if `https://database.windows.net` expects an audience of `https://database.windows.net/`, you'll need to request a scope of `https://database.windows.net//.default`. See also GitHub issue [#747: `Resource url's trailing slash is omitted, which caused sql auth failure`](https://github.com/AzureAD/microsoft-authentication-library-for-dotnet/issues/747).
 
 ## Scopes to request access to all the permissions of a v1.0 application
 

articles/active-directory/standards/media/memo-22-09/azure-active-directory-pr-methods.png

@@ -43,7 +43,7 @@ If AKS finds multiple unhealthy nodes during a health check, each node is repair
 
 
 ## Node Autodrain
-[Scheduled Events][scheduled-events] can occur on the underlying virtual machines (VMs) in any of your node pools. For [spot node pools][spot-node-pools], scheduled events may cause a *preempt* node event for the node. Certain node events, such as  *preempt*, cause AKS node autodrain to attempt a cordon and drain of the affected node, which allows for a graceful reschedule of any affected workloads on that node.
+[Scheduled Events][scheduled-events] can occur on the underlying virtual machines (VMs) in any of your node pools. For [spot node pools][spot-node-pools], scheduled events may cause a *preempt* node event for the node. Certain node events, such as  *preempt*, cause AKS node autodrain to attempt a cordon and drain of the affected node, which allows for a graceful reschedule of any affected workloads on that node. When this happens, you might notice the node to receive a taint with *"remediator.aks.microsoft.com/unschedulable"*, because of *"kubernetes.azure.com/scalesetpriority: spot"*.
 
 
 The following table shows the node events, and the actions they cause for AKS node autodrain.

articles/active-directory/standards/memo-22-09-multi-factor-authentication.md

@@ -116,7 +116,7 @@ These code snippets show you how to do the following tasks with the Form Recogni
 
 ## Authenticate the client
 
-Below **Main**, create a new method named `AuthenticateClient`. You'll use this method in other tasks to authenticate your requests to the Form Recognizer service. This method uses the `AzureKeyCredential` object, so that if needed, you can update the API key without creating new client objects.
+Below **Main**, create a new method named `AuthenticateClient`. You'll use this method in other tasks to authenticate your requests to the Form Recognizer service. This method uses the `AzureKeyCredential` object, so that if needed, you can update the key without creating new client objects.
 
 > [!IMPORTANT]
 > Get your key and endpoint from the Azure portal. If the Form Recognizer resource you created in the **Prerequisites** section deployed successfully, click the **Go to Resource** button under **Next Steps**. You can find your key and endpoint in the resource's **key and endpoint** page, under **resource management**.

articles/aks/node-auto-repair.md

@@ -145,7 +145,7 @@ These code snippets show you how to do the following tasks with the Form Recogni
 
 ## Authenticate the client
 
-At the top of your **main** method, add the following code. Here, you'll authenticate two client objects using the subscription variables you defined above. You'll use an **AzureKeyCredential** object, so that if needed, you can update the API key without creating new client objects.
+At the top of your **main** method, add the following code. Here, you'll authenticate two client objects using the subscription variables you defined above. You'll use an **AzureKeyCredential** object, so that if needed, you can update the key without creating new client objects.
 
 [!code-java[](~/cognitive-services-quickstart-code/java/FormRecognizer/FormRecognizer.java?name=snippet_auth)]
 

articles/applied-ai-services/form-recognizer/api-v2-0/includes/csharp-v3-0-0.md

@@ -105,7 +105,7 @@ These code snippets show you how to do the following tasks with the Form Recogni
 
 ## Authenticate the client
 
-Authenticate a client object using the subscription variables you defined. You'll use an `AzureKeyCredential` object, so that if needed, you can update the API key without creating new client objects. You'll also create a training client object.
+Authenticate a client object using the subscription variables you defined. You'll use an `AzureKeyCredential` object, so that if needed, you can update the key without creating new client objects. You'll also create a training client object.
 
 [!code-javascript[](~/cognitive-services-quickstart-code/javascript/FormRecognizer/FormRecognizerQuickstart.js?name=snippet_auth)]
 

articles/applied-ai-services/form-recognizer/api-v2-0/includes/java-v3-0-0.md

@@ -91,7 +91,7 @@ These code snippets show you how to do the following tasks with the Form Recogni
 
 ## Authenticate the client
 
-Here, you'll authenticate two client objects using the subscription variables you defined above. You'll use an **AzureKeyCredential** object, so that if needed, you can update the API key without creating new client objects.
+Here, you'll authenticate two client objects using the subscription variables you defined above. You'll use an **AzureKeyCredential** object, so that if needed, you can update the key without creating new client objects.
 
 [!code-python[](~/cognitive-services-quickstart-code/python/FormRecognizer/FormRecognizerQuickstart.py?name=snippet_auth)]