Merge pull request #265141 from MicrosoftDocs/main

2/2/2024 PM Publish

Author: Taojunshen

.openpublishing.redirection.azure-monitor.json

@@ -2287,17 +2287,17 @@
         },
         {
             "source_path_from_root": "/articles/azure-monitor/insights/solutions-inventory.md",
-            "redirect_url": "/azure/azure-monitor/monitor-reference",
+            "redirect_url": "/azure/azure-monitor/overview",
             "redirect_document_id": false
         },
         {
             "source_path_from_root": "/articles/monitoring/monitoring-solutions-inventory.md",
-            "redirect_url": "/azure/azure-monitor/monitor-reference",
+            "redirect_url": "/azure/azure-monitor/overview",
             "redirect_document_id": false
         },
         {
             "source_path_from_root": "/articles/azure-monitor/platform/data-locations.md",
-            "redirect_url": "/azure/azure-monitor/monitor-reference/",
+            "redirect_url": "/azure/azure-monitor/overview/",
             "redirect_document_id": false
         },
         {
@@ -6598,6 +6598,11 @@
             "source_path_from_root": "/articles/azure-monitor/app/java-standalone-arguments.md",
             "redirect_url": "/azure/azure-monitor/app/java-get-started-supplemental",
             "redirect_document_id": true
+        },
+        {
+            "source_path_from_root": "/articles/azure-monitor/monitor-reference.md",
+            "redirect_url": "/azure/azure-monitor/overview",
+            "redirect_document_id": false
         }
     ]
 }

articles/ai-services/.openpublishing.redirection.cognitive-services.json

@@ -5125,7 +5125,7 @@
         },
         {
             "source_path_from_root": "/articles/cognitive-services/text-analytics/migration-guide.md",
-            "redirect_url": "/azure/ai-services/language-service/concepts/migrate-from-text-analytics-v2",
+            "redirect_url": "/azure/ai-services/language-service/concepts/migrate",
             "redirect_document_id": false
         },
         {

articles/aks/egress-outboundtype.md

@@ -6,7 +6,7 @@ ms.subservice: aks-networking
 ms.custom: devx-track-azurecli
 ms.author: allensu
 ms.topic: how-to
-ms.date: 11/06/2023
+ms.date: 02/02/2024
 #Customer intent: As a cluster operator, I want to define my own egress paths with user-defined routes. Since I define this up front I do not want AKS provided load balancer configurations.
 ---
 
@@ -99,41 +99,11 @@ Migration is only supported between `loadBalancer`, `managedNATGateway` (if usin
 
 [!INCLUDE [preview features callout](includes/preview/preview-callout.md)]
 
-### Install the `aks-preview` Azure CLI extension
-
-`aks-preview` version 0.5.113 is required.
-
-* Install and update the `aks-preview` extension.
-
-```azurecli
-# Install aks-preview extension
-az extension add --name aks-preview
-# Update aks-preview extension
-az extension update --name aks-preview
-```
-
-### Register the `AKS-OutBoundTypeMigrationPreview` feature flag
-
-1. Register the `AKS-OutBoundTypeMigrationPreview` feature flag using the [`az feature register`][az-feature-register] command. It takes a few minutes for the status to show *Registered*.
-
-```azurecli-interactive
-az feature register --namespace "Microsoft.ContainerService" --name "AKS-OutBoundTypeMigrationPreview"
-```
-
-2. Verify the registration status using the [`az feature show`][az-feature-show] command.
-
-```azurecli-interactive
-az feature show --namespace "Microsoft.ContainerService" --name "AKS-OutBoundTypeMigrationPreview"
-```
-
-3. When the status reflects *Registered*, refresh the registration of the *Microsoft.ContainerService* resource provider using the [`az provider register`][az-provider-register] command.
-
-```azurecli-interactive
-az provider register --namespace Microsoft.ContainerService
-```
-
 ### Update cluster to use a new outbound type
 
+> [!NOTE]
+> You must use a version >= 2.56 of Azure CLI to migrate outbound type. Use `az upgrade` to update to the latest version of Azure CLI. 
+
 * Update the outbound configuration of your cluster using the [`az aks update`][az-aks-update] command.
 
 ### Update cluster from loadbalancer to managedNATGateway  

articles/app-service/deploy-azure-pipelines.md

@@ -105,7 +105,7 @@ To get started:
 
     * **azureSubscription**: Name of the authorized service connection to your Azure subscription.
     * **appName**: Name of your existing app.
-    * **package**: Fike path to the package or a folder containing your app service contents. Wildcards are supported.
+    * **package**: File path to the package or a folder containing your app service contents. Wildcards are supported.
 
 # [Classic](#tab/classic/)
 

articles/app-service/environment/how-to-migrate.md

@@ -46,7 +46,7 @@ The following are limitations when using the migration feature:
 
 - Your new App Service Environment v3 is in the existing subnet that was used for your old environment.
 - You can't change the region your App Service Environment is located in.
-- ELB App Service Environment can’t be migrated to ILB App Service Environment v3 and vice versa.
+- ELB App Service Environment can't be migrated to ILB App Service Environment v3 and vice versa.
 - If your existing App Service Environment uses a custom domain suffix, you have to configure custom domain suffix for your App Service Environment v3 during the migration process.
   - If you no longer want to use a custom domain suffix, you can remove it once the migration is complete.
 
@@ -139,7 +139,7 @@ Migration requires a three to six hour service window for App Service Environmen
 - The existing App Service Environment is shut down and replaced by the new App Service Environment v3.
 - All App Service plans in the App Service Environment are converted from the Isolated to Isolated v2 SKU.
 - All of the apps that are on your App Service Environment are temporarily down. **You should expect about one hour of downtime during this period**.
-  - If you can't support downtime, see [migration-alternatives](migration-alternatives.md#guidance-for-manual-migration).
+  - If you can't support downtime, see [migration-alternatives](migration-alternatives.md#migrate-manually).
 - The public addresses that are used by the App Service Environment change to the IPs generated during the IP generation step.
 
 The following statuses are available during the migration process: