Merge pull request #257310 from MicrosoftDocs/main

11/3 11:00 AM IST Publishing

Author: Saisang

articles/ai-services/openai/how-to/embeddings.md

@@ -6,9 +6,9 @@ services: cognitive-services
 manager: nitinme
 ms.service: azure-ai-openai
 ms.topic: how-to
-ms.date: 9/12/2023
-author: ChrisHMSFT
-ms.author: chrhoder
+ms.date: 11/02/2023
+author: mrbullwinkle
+ms.author: mbullwin
 recommendations: false
 keywords: 
 
@@ -75,15 +75,7 @@ foreach (float item in returnValue.Value.Data[0].Embedding)
 
 ### Verify inputs don't exceed the maximum length
 
-The maximum length of input text for our embedding models is 2048 tokens (equivalent to around 2-3 pages of text). You should verify that your inputs don't exceed this limit before making a request.
-
-### Choose the best model for your task
-
-For the search models, you can obtain embeddings in two ways. The `<search_model>-doc` model is used for longer pieces of text (to be searched over) and the `<search_model>-query` model is used for shorter pieces of text, typically queries or class labels in zero shot classification. You can read more about all of the Embeddings models in our [Models](../concepts/models.md) guide.
-
-### Replace newlines with a single space
-
-Unless you're embedding code, we suggest replacing newlines (\n) in your input with a single space, as we have observed inferior results when newlines are present.
+The maximum length of input text for our latest embedding models is 8192 tokens. You should verify that your inputs don't exceed this limit before making a request.
 
 ## Limitations & risks
 

articles/azure-monitor/essentials/activity-log.md

@@ -33,26 +33,26 @@ Activity log events are retained in Azure for *90 days* and then deleted. There'
 ## View the activity log
 
 You can access the activity log from most menus in the Azure portal. The menu that you open it from determines its initial filter. If you open it from the **Monitor** menu, the only filter is on the subscription. If you open it from a resource's menu, the filter is set to that resource. You can always change the filter to view all other entries. Select **Add Filter** to add more properties to the filter.
-
-![Screenshot that shows the activity log.](./media/activity-log/view-activity-log.png)
+<!-- convertborder later -->
+:::image type="content" source="./media/activity-log/view-activity-log.png" lightbox="./media/activity-log/view-activity-log.png" alt-text="Screenshot that shows the activity log." border="false":::
 
 For a description of activity log categories, see [Azure activity log event schema](activity-log-schema.md#categories).
 
 ## Download the activity log
 
 Select **Download as CSV** to download the events in the current view.
-
-![Screenshot that shows downloading the activity log.](media/activity-log/download-activity-log.png)
+<!-- convertborder later -->
+:::image type="content" source="media/activity-log/download-activity-log.png" lightbox="media/activity-log/download-activity-log.png" alt-text="Screenshot that shows downloading the activity log." border="false":::
 
 ### View change history
 
 For some events, you can view the change history, which shows what changes happened during that event time. Select an event from the activity log you want to look at more deeply. Select the **Change history** tab to view any changes on the resource up to 30 minutes before and after the time of the operation.
 
-![Screenshot that shows the Change history list for an event.](media/activity-log/change-history-event.png)
+:::image type="content" source="media/activity-log/change-history-event.png" lightbox="media/activity-log/change-history-event.png" alt-text="Screenshot that shows the Change history list for an event.":::
 
 If any changes are associated with the event, you'll see a list of changes that you can select. Selecting a change opens the **Change history** page. This page displays the changes to the resource. In the following example, you can see that the VM changed sizes. The page displays the VM size before the change and after the change. To learn more about change history, see [Get resource changes](../../governance/resource-graph/how-to/get-resource-changes.md).
 
-![Screenshot that shows the Change history page showing differences.](media/activity-log/change-history-event-details.png)
+:::image type="content" source="media/activity-log/change-history-event-details.png" lightbox="media/activity-log/change-history-event-details.png" alt-text="Screenshot that shows the Change history page showing differences.":::
 
 ### Other methods to retrieve activity log events
 
@@ -76,7 +76,7 @@ You can also access activity log events by using the following methods:
 
  Select **Export Activity Logs** to send the activity log to a Log Analytics workspace.
 
-   ![Screenshot that shows exporting activity logs.](media/activity-log/diagnostic-settings-export.png)
+   :::image type="content" source="media/activity-log/diagnostic-settings-export.png" lightbox="media/activity-log/diagnostic-settings-export.png" alt-text="Screenshot that shows exporting activity logs.":::
 
 You can send the activity log from any single subscription to up to five workspaces.
 

articles/azure-monitor/essentials/collect-custom-metrics-guestos-resource-manager-vm.md

@@ -263,7 +263,7 @@ To deploy the ARM template, we use Azure PowerShell.
 
 1. On the **Monitor** page, select **Metrics**.
 
-   ![Screenshot that shows the Metrics page.](media/collect-custom-metrics-guestos-resource-manager-vm/metrics.png)
+   :::image type="content" source="media/collect-custom-metrics-guestos-resource-manager-vm/metrics.png" lightbox="media/collect-custom-metrics-guestos-resource-manager-vm/metrics.png" alt-text="Screenshot that shows the Metrics page.":::
 
 1. Change the aggregation period to **Last 30 minutes**.
 

articles/azure-monitor/essentials/collect-custom-metrics-guestos-vm-classic.md

@@ -32,12 +32,12 @@ The process that's outlined in this article only works on classic virtual machin
 ## Create a classic virtual machine and storage account
 
 1. Create a classic VM by using the Azure portal.
-   ![Create Classic VM](./media/collect-custom-metrics-guestos-vm-classic/create-classic-vm.png)
+   :::image type="content" source="./media/collect-custom-metrics-guestos-vm-classic/create-classic-vm.png" lightbox="./media/collect-custom-metrics-guestos-vm-classic/create-classic-vm.png" alt-text="Create Classic VM":::
 
 1. When you're creating this VM, choose the option to create a new classic storage account. We use this storage account in later steps.
 
 1. In the Azure portal, go to the **Storage accounts** resource pane. Select **Keys**, and take note of the storage account name and storage account key. You need this information in later steps.
-   ![Storage access keys](./media/collect-custom-metrics-guestos-vm-classic/storage-access-keys.png)
+   :::image type="content" source="./media/collect-custom-metrics-guestos-vm-classic/storage-access-keys.png" lightbox="./media/collect-custom-metrics-guestos-vm-classic/storage-access-keys.png" alt-text="Storage access keys":::
 
 ## Create a service principal
 
@@ -185,14 +185,14 @@ Give this app “Monitoring Metrics Publisher” permissions to the resource tha
 
 1.	On the **Monitor** pane on the left, select **Metrics**.
 
-    ![Navigate metrics](./media/collect-custom-metrics-guestos-vm-classic/navigate-metrics.png)
+    :::image type="content" source="./media/collect-custom-metrics-guestos-vm-classic/navigate-metrics.png" lightbox="./media/collect-custom-metrics-guestos-vm-classic/navigate-metrics.png" alt-text="Navigate metrics":::
 
 1. In the resources drop-down menu, select your classic VM.
 
 1. In the namespaces drop-down menu, select **azure.vm.windows.guest**.
 
 1. In the metrics drop-down menu, select **Memory\Committed Bytes in Use**.
-   ![Plot metrics](./media/collect-custom-metrics-guestos-vm-classic/plot-metrics.png)
+   :::image type="content" source="./media/collect-custom-metrics-guestos-vm-classic/plot-metrics.png" lightbox="./media/collect-custom-metrics-guestos-vm-classic/plot-metrics.png" alt-text="Plot metrics":::
 
 
 ## Next steps

articles/azure-monitor/essentials/collect-custom-metrics-guestos-vm-cloud-service-classic.md

@@ -32,8 +32,8 @@ The process that's outlined in this article works only for performance counters
 1. Create and deploy a classic cloud service. A sample classic Cloud Services application and deployment can be found at [Get started with Azure Cloud Services and ASP.NET](../../cloud-services/cloud-services-dotnet-get-started.md). 
 
 2. You can use an existing storage account or deploy a new storage account. It's best if the storage account is in the same region as the classic cloud service that you created. In the Azure portal, go to the **Storage accounts** resource pane, and then select **Keys**. Take note of the storage account name and the storage account key. You'll need this information in later steps.
-
-   ![Storage account keys](./media/collect-custom-metrics-guestos-vm-cloud-service-classic/storage-keys.png)
+   <!-- convertborder later -->
+   :::image type="content" source="./media/collect-custom-metrics-guestos-vm-cloud-service-classic/storage-keys.png" lightbox="./media/collect-custom-metrics-guestos-vm-cloud-service-classic/storage-keys.png" alt-text="Storage account keys" border="false":::
 
 ## Create a service principal 
 
@@ -164,7 +164,7 @@ Set-AzureServiceDiagnosticsExtension -ServiceName <classicCloudServiceName> -Sto
 
 1. Go to the Azure portal. 
 
-   ![Screenshot shows the Azure portal with Monitor, then Metrics selected.](./media/collect-custom-metrics-guestos-vm-cloud-service-classic/navigate-metrics.png)
+   :::image type="content" source="./media/collect-custom-metrics-guestos-vm-cloud-service-classic/navigate-metrics.png" lightbox="./media/collect-custom-metrics-guestos-vm-cloud-service-classic/navigate-metrics.png" alt-text="Screenshot shows the Azure portal with Monitor, then Metrics selected.":::
 
 2. On the left menu, select **Monitor.**
 
@@ -177,8 +177,8 @@ Set-AzureServiceDiagnosticsExtension -ServiceName <classicCloudServiceName> -Sto
 6. In the metrics drop-down menu, select **Memory\Committed Bytes in Use**. 
 
 You use the dimension filtering and splitting capabilities to view the total memory that's used by a specific role or role instance. 
-
- ![Screenshot shows Metrics data.](./media/collect-custom-metrics-guestos-vm-cloud-service-classic/metrics-graph.png)
+ <!-- convertborder later -->
+ :::image type="content" source="./media/collect-custom-metrics-guestos-vm-cloud-service-classic/metrics-graph.png" lightbox="./media/collect-custom-metrics-guestos-vm-cloud-service-classic/metrics-graph.png" alt-text="Screenshot shows Metrics data." border="false":::
 
 ## Next steps
 

articles/azure-monitor/essentials/data-collection-endpoint-overview.md

@@ -61,12 +61,12 @@ This table describes the components of a data collection endpoint, related regio
 # [Azure portal](#tab/portal)
 
 1. On the **Azure Monitor** menu in the Azure portal, select **Data Collection Endpoints** under the **Settings** section. Select **Create** to create a new DCR and assignment.
-
-   [![Screenshot that shows data collection endpoints.](media/data-collection-endpoint-overview/data-collection-endpoint-overview.png)](media/data-collection-endpoint-overview/data-collection-endpoint-overview.png#lightbox)
+   <!-- convertborder later -->
+   :::image type="content" source="media/data-collection-endpoint-overview/data-collection-endpoint-overview.png" lightbox="media/data-collection-endpoint-overview/data-collection-endpoint-overview.png" alt-text="Screenshot that shows data collection endpoints." border="false":::
 
 1. Select **Create** to create a new endpoint. Provide a **Rule name** and specify a **Subscription**, **Resource Group**, and **Region**. This information specifies where the DCE will be created.
-
-   [![Screenshot that shows data collection rule basics.](media/data-collection-endpoint-overview/data-collection-endpoint-basics.png)](media/data-collection-endpoint-overview/data-collection-endpoint-basics.png#lightbox)
+   <!-- convertborder later -->
+   :::image type="content" source="media/data-collection-endpoint-overview/data-collection-endpoint-basics.png" lightbox="media/data-collection-endpoint-overview/data-collection-endpoint-basics.png" alt-text="Screenshot that shows data collection rule basics." border="false":::
 
 1. Select **Review + create** to review the details of the DCE. Select **Create** to create it.
 

articles/azure-monitor/essentials/data-platform-metrics.md

@@ -28,7 +28,7 @@ There are multiple types of metrics supported by Azure Monitor Metrics:
   - Custom metrics are collected from different sources that you configure including applications and agents running on virtual machines.
 - Prometheus metrics are collected from Kubernetes clusters including Azure Kubernetes service (AKS) and use industry standard tools for analyzing and alerting such as PromQL and Grafana.
 
-![Diagram that shows sources and uses of metrics.](media/data-platform-metrics/metrics-overview.png)
+:::image type="content" source="media/data-platform-metrics/metrics-overview.png" lightbox="media/data-platform-metrics/metrics-overview.png" alt-text="Diagram that shows sources and uses of metrics.":::
 
 The differences between each of the metrics are summarized in the following table.
 
@@ -62,7 +62,7 @@ For a complete list of data sources that can send data to Azure Monitor Metrics,
 Azure Monitor provides REST APIs that allow you to get data in and out of Azure Monitor Metrics.
 - **Custom metrics API** - [Custom metrics](./metrics-custom-overview.md) allow you to load your own metrics into the Azure Monitor Metrics database. Those metrics can then be used by the same analysis tools that process Azure Monitor platform metrics. 
 - **Azure Monitor Metrics REST API** - Allows you to access Azure Monitor platform metrics definitions and values. For more information, see [Azure Monitor REST API](/rest/api/monitor/).  For information on how to use the API, see the [Azure monitoring REST API walkthrough](./rest-api-walkthrough.md).
-- **Azure Monitor Metrics Data plane REST API**  - [Azure Monitor Metrics data plane API](/rest/api/monitor/metrics-data-plane/) is a high-volume API designed for customers with large volume metrics queries. It's similar to the existing standard Azure Monitor Metrics REST API, but provides the capability to retrieve metric data for up to 50 resource IDs in the same subscription and region in a single batch API call. This improves query throughput and reduces the risk of throttling.   
+- **Azure Monitor Metrics Batch REST API**  - [Azure Monitor Metrics Batch API](/rest/api/monitor/metrics-batch/) is a high-volume API designed for customers with large volume metrics queries. It's similar to the existing standard Azure Monitor Metrics REST API, but provides the capability to retrieve metric data for up to 50 resource IDs in the same subscription and region in a single batch API call. This improves query throughput and reduces the risk of throttling.   
 
 ## Security
 
@@ -73,8 +73,8 @@ Secure connection is established between the agent and the Azure Monitor service
 ## Metrics Explorer
 
 Use [Metrics Explorer](metrics-charts.md) to interactively analyze the data in your metric database and chart the values of multiple metrics over time. You can pin the charts to a dashboard to view them with other visualizations. You can also retrieve metrics by using the [Azure monitoring REST API](./rest-api-walkthrough.md).
-
-![Screenshot that shows an example graph in Metrics Explorer that displays server requests, server response time, and failed requests.](media/data-platform-metrics/metrics-explorer.png)
+<!-- convertborder later -->
+:::image type="content" source="media/data-platform-metrics/metrics-explorer.png" lightbox="media/data-platform-metrics/metrics-explorer.png" alt-text="Screenshot that shows an example graph in Metrics Explorer that displays server requests, server response time, and failed requests." border="false":::
 
 For more information, see [Analyze metrics with Azure Monitor metrics explorer](./analyze-metrics.md).
 

articles/azure-monitor/essentials/diagnostic-settings-policy.md

@@ -80,24 +80,24 @@ For details on creating an initiative, see [Create and assign an initiative defi
 
 - Set **Category** to **Monitoring** to group it with related built-in and custom policy definitions.
 - Instead of specifying the details for the Log Analytics workspace and the event hub for policy definitions included in the initiative, use a common initiative parameter. This parameter allows you to easily specify a common value for all policy definitions and change that value if necessary.
-
-![Screenshot that shows settings for initiative definition.](media/diagnostic-settings-policy/initiative-definition.png)
+<!-- convertborder later -->
+:::image type="content" source="media/diagnostic-settings-policy/initiative-definition.png" lightbox="media/diagnostic-settings-policy/initiative-definition.png" alt-text="Screenshot that shows settings for initiative definition." border="false":::
 
 ## Assignment 
 Assign the initiative to an Azure management group, subscription, or resource group, depending on the scope of your resources to monitor. A [management group](../../governance/management-groups/overview.md) is useful for scoping policy, especially if your organization has multiple subscriptions.
-
-![Screenshot of the settings for the Basics tab in the Assign initiative section of the Diagnostic settings to Log Analytics workspace in the Azure portal.](media/diagnostic-settings-policy/initiative-assignment.png)
+<!-- convertborder later -->
+:::image type="content" source="media/diagnostic-settings-policy/initiative-assignment.png" lightbox="media/diagnostic-settings-policy/initiative-assignment.png" alt-text="Screenshot of the settings for the Basics tab in the Assign initiative section of the Diagnostic settings to Log Analytics workspace in the Azure portal." border="false":::
 
 By using initiative parameters, you can specify the workspace or any other details once for all of the policy definitions in the initiative. 
-
-![Screenshot that shows initiative parameters on the Parameters tab.](media/diagnostic-settings-policy/initiative-parameters.png)
+<!-- convertborder later -->
+:::image type="content" source="media/diagnostic-settings-policy/initiative-parameters.png" lightbox="media/diagnostic-settings-policy/initiative-parameters.png" alt-text="Screenshot that shows initiative parameters on the Parameters tab." border="false":::
 
 ## Remediation
 The initiative will be applied to each virtual machine as it's created. A [remediation task](../../governance/policy/how-to/remediate-resources.md) deploys the policy definitions in the initiative to existing resources, so you can create diagnostic settings for any resources that were already created.
 
 When you create the assignment by using the Azure portal, you have the option of creating a remediation task at the same time. See [Remediate non-compliant resources with Azure Policy](../../governance/policy/how-to/remediate-resources.md) for details on the remediation.
-
-![Screenshot that shows initiative remediation for a Log Analytics workspace.](media/diagnostic-settings-policy/initiative-remediation.png)
+<!-- convertborder later -->
+:::image type="content" source="media/diagnostic-settings-policy/initiative-remediation.png" lightbox="media/diagnostic-settings-policy/initiative-remediation.png" alt-text="Screenshot that shows initiative remediation for a Log Analytics workspace." border="false":::
 
 ## Troubleshooting