Merge branch 'MicrosoftDocs:main' into patch-2

Author: julia-yin

.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/ai-studio/how-to/model-catalog.md

@@ -47,6 +47,9 @@ The model benchmarks help you make informed decisions about the suitability of m
 | Metric       | Description |
 |--------------|-------|
 | Accuracy     |Accuracy scores are available at the dataset and the model levels. At the dataset level, the score is the average value of an accuracy metric computed over all examples in the dataset. The accuracy metric used is exact-match in all cases except for the *HumanEval* dataset that uses a `pass@1` metric. Exact match simply compares model generated text with the correct answer according to the dataset, reporting one if the generated text matches the answer exactly and zero otherwise. `Pass@1` measures the proportion of model solutions that pass a set of unit tests in a code generation task. At the model level, the accuracy score is the average of the dataset-level accuracies for each model.|
+| Coherence    |Coherence evaluates how well the language model can produce output that flows smoothly, reads naturally, and resembles human-like language.|
+| Fluency      |Fluency evaluates the language proficiency of a generative AI's predicted answer. It assesses how well the generated text adheres to grammatical rules, syntactic structures, and appropriate usage of vocabulary, resulting in linguistically correct and natural-sounding responses.|
+| GPTSimilarity|GPTSimilarity is a measure that quantifies the similarity between a ground truth sentence (or document) and the prediction sentence generated by an AI model. It is calculated by first computing sentence-level embeddings using the embeddings API for both the ground truth and the model's prediction. These embeddings represent high-dimensional vector representations of the sentences, capturing their semantic meaning and context.|
 
 The benchmarks are updated regularly as new metrics and datasets are added to existing models, and as new models are added to the model catalog.
 

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