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

Author: duongau

articles/active-directory/multi-tenant-organizations/cross-tenant-synchronization-configure-graph.md

@@ -27,15 +27,15 @@ This article describes the key steps to configure cross-tenant synchronization u
 
 ## Prerequisites
 
-### Source tenant
+![Icon for the source tenant.](./media/common/icon-tenant-source.png)<br/>**Source tenant**
 
 - Azure AD Premium P1 or P2 license
 - [Security Administrator](../roles/permissions-reference.md#security-administrator) role to configure cross-tenant access settings
 - [Hybrid Identity Administrator](../roles/permissions-reference.md#hybrid-identity-administrator) role to configure cross-tenant synchronization
 - [Cloud Application Administrator](../roles/permissions-reference.md#cloud-application-administrator) or [Application Administrator](../roles/permissions-reference.md#application-administrator) role to assign users to a configuration and to delete a configuration
 - [Global Administrator](../roles/permissions-reference.md#global-administrator) role to consent to required permissions
 
-### Target tenant
+![Icon for the target tenant.](./media/common/icon-tenant-target.png)<br/>**Target tenant**
 
 - Azure AD Premium P1 or P2 license
 - [Security Administrator](../roles/permissions-reference.md#security-administrator) role to configure cross-tenant access settings

articles/active-directory/multi-tenant-organizations/cross-tenant-synchronization-configure.md

@@ -35,14 +35,14 @@ By the end of this article, you'll be able to:
 
 ## Prerequisites
 
-### Source tenant
+![Icon for the source tenant.](./media/common/icon-tenant-source.png)<br/>**Source tenant**
 
 - Azure AD Premium P1 or P2 license
 - [Security Administrator](../roles/permissions-reference.md#security-administrator) role to configure cross-tenant access settings
 - [Hybrid Identity Administrator](../roles/permissions-reference.md#hybrid-identity-administrator) role to configure cross-tenant synchronization
 - [Cloud Application Administrator](../roles/permissions-reference.md#cloud-application-administrator) or [Application Administrator](../roles/permissions-reference.md#application-administrator) role to assign users to a configuration and to delete a configuration
 
-### Target tenant
+![Icon for the target tenant.](./media/common/icon-tenant-target.png)<br/>**Target tenant**
 
 - Azure AD Premium P1 or P2 license
 - [Security Administrator](../roles/permissions-reference.md#security-administrator) role to configure cross-tenant access settings

articles/azure-monitor/essentials/media/metrics-charts/031.png

@@ -45,7 +45,17 @@ Your storage account resource is experiencing an excess volume of failed transac
 
 In the metric picker, select your storage account and the **Transactions** metric. Switch chart type to **Bar chart**. Click **Apply splitting** and select dimension **API name**. Then click on the **Add filter** and pick the **API name** dimension once again. In the filter dialog, select the APIs that you want to plot on the chart.
 
+## Total requests of Cosmos DB by Database Names and Collection Names
+
+You want to identify which collection in which database of your Cosmos DB instance is having maximum requests to adjust your costs for Cosmos DB.
+
+![Segmented line chart of Total Requests](./media/metrics-charts/multiple-split-example.png)
+
+### How to configure this chart?
+
+In the metric picker, select your Cosmos DB resource and the **Total Requests** metric. Click **Apply splitting** and select dimensions **DatabaseName** and **CollectionName**.
+
 ## Next steps
 
 * Learn about Azure Monitor [Workbooks](../visualize/workbooks-overview.md)
-* Learn more about [Metric Explorer](metrics-charts.md)
+* Learn more about [Metric Explorer](metrics-charts.md)

articles/azure-monitor/essentials/media/metrics-charts/multiple-split-example.png

@@ -172,11 +172,8 @@ You can split a metric by dimension to visualize how different segments of the m
 ### Apply splitting
 
 1. Above the chart, select **Apply splitting**.
-
-   > [!NOTE]
-   > Charts that have multiple metrics can't use the splitting functionality. Also, although a chart can have multiple filters, it can have only one splitting dimension.
-
-1. Choose a dimension on which to segment your chart:
+   
+1. Choose dimension(s) on which to segment your chart:
 
    ![Screenshot that shows the selected dimension on which to segment the chart.](./media/metrics-charts/031.png)
 
@@ -192,7 +189,11 @@ You can split a metric by dimension to visualize how different segments of the m
 
    ![Screenshot that shows sort order on split values.](./media/metrics-charts/segment-dimension-sort.png)
 
-1. Click away from the grouping selector to close it.
+1. If you like to segment by multiple segments select multiple dimensions from the values dropdown. The legends will show a comma-separated list of dimension values for each segment
+
+   ![Screenshot that shows multiple segments selected, and the corresponding chart below.](./media/metrics-charts/segment-dimension-multiple.png)
+   
+3. Click away from the grouping selector to close it.
 
    > [!NOTE]
    > To hide segments that are irrelevant for your scenario and to make your charts easier to read, use both filtering and splitting on the same dimension.

articles/azure-monitor/essentials/media/metrics-charts/segment-dimension-multiple.png

@@ -171,6 +171,16 @@ Similarly,
 * The *false Negative* of the model is the sum of *false negatives* for all intents or entities.
 
 
+## Guidance
+
+After you trained your model, you will see some guidance and recommendations on how to improve the model. It's recommended to have a model covering every point in the guidance section.
+
+* Training set has enough data: When an intent or entity has fewer than 15 labeled instances in the training data, it can lead to lower accuracy due to the model not being adequately trained on that intent. In this case, consider adding more labeled data in the training set. You should only consider adding more labeled data to your entity if your entity has a learned component. If your entity is defined only by list, prebuilt, and regex components, then this recommendation is not applicable.
+
+* All intents or entities are present in test set: When the testing data lacks labeled instances for an intent or entity, the model evaluation is less comprehensive due to untested scenarios. Consider having test data for every intent and entity in your model to ensure everything is being tested.
+
+* Unclear distinction between intents or entities: When data is similar for different intents or entities, it can lead to lower accuracy because they may be frequently misclassified as each other. Review the following intents and entities and consider merging them if they’re similar. Otherwise, add more examples to better distinguish them from each other. You can check the *confusion matrix* tab for more guidance. If you are seeing two entities constantly being predicted for the same spans because they share the same list, prebuilt, or regex components, then make sure to add a **learned** component for each entity and make it **required**. Learn more about [entity components](./entity-components.md).
+
 ## Next steps
 
 [Train a model in Language Studio](../how-to/train-model.md)

articles/azure-monitor/essentials/metric-chart-samples.md

@@ -33,11 +33,6 @@ See the [project development lifecycle](../overview.md#project-development-lifec
 
 ### [Language studio](#tab/Language-studio)
 
-> [!Note]
-> The results here are for the machine learning entity component only.
-
-In the **view model details** page, you'll be able to see all your models, with their current training status, and the date they were last trained.
-
 [!INCLUDE [Model performance](../includes/language-studio/model-performance.md)]
 
 ### [REST APIs](#tab/REST-APIs)

articles/azure-monitor/essentials/metrics-charts.md

@@ -13,14 +13,55 @@ ms.author: aahi
 
 2. Select **Model performance** from the menu on the left side of the screen.
 
-3. In this page you can only view the successfully trained models, F1 score of each model and [model expiration date](../../../concepts/model-lifecycle.md#expiration-timeline). You can click on the model name for more details about its performance.
+3. In this page you can only view the successfully trained models, F1 score of each model and [model expiration date](../../../concepts/model-lifecycle.md#expiration-timeline). You can click on the model name for more details about its performance. Models only include evaluation details if there was test data selected while training the model.
 
-4. You can find the *model-level evaluation metrics* under **Overview**, and the *intent-level* and *entity-level* evaluation metrics. See [Evaluation metrics](../../concepts/evaluation-metrics.md#) for more information.
+### [Overview](#tab/overview)
 
-    :::image type="content" source="../../media/model-details.png" alt-text="A screenshot of the model performance metrics in Language Studio" lightbox="../../media/model-details.png":::
-    
-5. The [confusion matrix](../../concepts/evaluation-metrics.md#confusion-matrix) for the model is located under **Test set confusion matrix**. You can see the confusion matrix for intents and entities.
-    
-    > [!NOTE] 
-    > If you don't see any of the intents or entities you have in your model displayed here, it is because they weren't in any of the utterances that were used for the test set.
-    
+* In this tab you can view the model's details such as: F1 score, precision, recall, date and time for the training job, total training time and number of training and testing utterances included in this training job.  You can view details between intents or entities by selecting Model Type at the top.
+
+    :::image type="content" source="../../media/overview.png" alt-text="A screenshot that shows the overview page for model evaluation." lightbox="../../media/overview.png":::
+
+* You will also see [guidance](../../concepts/evaluation-metrics.md#guidance) on how to improve the model. When clicking on *view details* a side panel will open to give more guidance on how to improve the model.
+
+    :::image type="content" source="../../media/overview-guidance.png" alt-text="A screenshot that shows the guidance page for model evaluation." lightbox="../../media/overview-guidance.png":::
+
+### [Model type performance](#tab/model-performance)
+
+* This is a snapshot of how your model performed during testing. The metrics here are static and tied to your model, so they won’t update until you train again.
+
+* You can see for each intent or entity the precision, recall, F1 score, number of training and testing labels. Entities that do not include a learned component will show no training labels. A learned component is added only by adding labels in your training set.
+
+
+    :::image type="content" source="../../media/model-type-performance.png" alt-text="A screenshot of model performance." lightbox="../../media/model-type-performance.png":::
+
+### [Test set details](#tab/test-set)
+
+* Here you will see the utterances included in the **test set** and their intent or entity predictions. You can use the *Show errors only* toggle to show only the utterances where there are different predictions from their labels, or unselect the toggle to view all utterances in the test set. You can also toggle the view between **Showing entity labels** as the view for each utterance, or **Showing entity predictions**. Entity predictions show as dotted lines and labels show as solid lines.
+
+* You can expand each row to view its intent or entity predictions, specified by the **Model Type** column. The **Text** column shows the text of the entity that was predicted or labeled. Each row has a **Labeled as** column to indicate the label in the test set, and **Predicted as** column to indicate the actual prediction. Also, you will see whether it is a [true positive](../../concepts/evaluation-metrics.md), [false positive](../../concepts/evaluation-metrics.md) or [false negative](../../concepts/evaluation-metrics.md) in the **Result Type** column. 
+
+    :::image type="content" source="../../media/test-set.png" alt-text="A screenshot of test set details." lightbox="../../media/test-set.png":::    
+
+### [Dataset distribution](#tab/dataset-distribution) 
+
+This snapshot shows how intents or entities are distributed across your training and testing sets. This data is static and tied to your model, so it won’t update until you train again. Entities that do not include a learned component will show no training labels. A learned component is added only by adding labels in your training set.
+
+  :::image type="content" source="../../media/dataset-table.png" alt-text="A screenshot showing distribution in table view." lightbox="../../media/dataset-table.png":::
+
+### [Confusion matrix](#tab/confusion-matrix) 
+
+A [confusion matrix](../../concepts/evaluation-metrics.md#confusion-matrix) is an N x N matrix used for evaluating the performance of your model, where N is the number of target intents or entities. The matrix compares the expected labels with those predicted by the model to identify which intents or entities are being misclassified as other intents and entities. You can click into any cell of the confusion matrix to identify exactly which utterances contributed to the values in that cell.
+
+You can view the intent confusion matrix in *raw count* or *normalized* view. Raw count is the actual number of utterances that have been predicted and labeled for a set of intents. Normalized value is the ratio, between 0 and 1, of the predicted and labeled utterances for a set of intents.
+
+You can view the entity confusion matrix in *character overlap count* or *normalized character overlap* view. Character overlap count is the actual number of spans that have been predicted and labeled for a set of entities. Normalized character overlap is the ratio, between 0 and 1, of the predicted and labeled spans for a set of entities. Sometimes entities can be predicted or labeled partially, leading to decimal values in the confusion matrix.
+
+  :::image type="content" source="../../media/confusion.png" alt-text="A screenshot of a confusion matrix in Language Studio." lightbox="../../media/confusion.png":::
+
+* All values: Will show the confusion matrix for all intents or entities.
+
+* Only errors: Will show the confusion matrix for intents or entities with errors only.
+
+* Only matches: Will show the confusion matrix for intents or entities with correct predictions only.
+
+---