Merge pull request #262136 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: Taojunshen

articles/ai-services/language-service/custom-text-classification/includes/roles-for-resource-and-storage.md

@@ -38,5 +38,5 @@ Use the following steps to set the required roles for your Language resource and
 5. Select **Select members**
 6. Select your subscription, and **Language** as the managed identity. You can search for user names in the **Select** field. 
 
-> ![IMPORTANT]
+> [!IMPORTANT]
 > If you have a virtual network or private endpoint, be sure to select **Allow Azure services on the trusted services list to access this storage account** in the Azure portal.

articles/ai-services/openai/concepts/use-your-data.md

@@ -161,7 +161,7 @@ Mapping these fields correctly helps ensure the model has better response and ci
 After ingesting your data, you can start chatting with the model on your data using the chat playground in Azure OpenAI studio, or the following methods:
 * [Web app](#using-the-web-app)
 * [REST API](../reference.md#azure-ai-search)
-* [C#](https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/openai/Azure.AI.OpenAI/tests/Samples/Sample08_UseYourOwnData.cs)
+* [C#](https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/openai/Azure.AI.OpenAI/tests/Samples/AzureOnYourData.cs)
 * [Java](https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/openai/azure-ai-openai/src/samples/java/com/azure/ai/openai/ChatCompletionsWithYourData.java)
 * [JavaScript](https://github.com/Azure/azure-sdk-for-js/blob/main/sdk/openai/openai/samples/v1-beta/javascript/bringYourOwnData.js)
 * [PowerShell](../use-your-data-quickstart.md?tabs=command-line%2Cpowershell&pivots=programming-language-powershell#example-powershell-commands)

articles/azure-monitor/logs/tutorial-logs-ingestion-portal.md

@@ -209,6 +209,9 @@ The final step is to give the application permission to use the DCR. Any applica
 
 The following PowerShell script generates sample data to configure the custom table and sends sample data to the logs ingestion API to test the configuration.
 
+> [!NOTE]
+> This sample script requires PowerShell v7.2 or later.
+
 1. Run the following PowerShell command, which adds a required assembly for the script:
 
     ```powershell

articles/copilot/work-smarter-edge.md

@@ -32,11 +32,11 @@ Here are a few examples of the kinds of prompts you can use to work with your Az
 
 ## Examples
 
-In this example, Microsoft Copilot for Azure responds to the prompt "summarize my HCI clusters" with details about the number of clusters, their status, and any alerts that affect them.
+In this example, Microsoft Copilot for Azure responds to the prompt "**summarize my HCI clusters**" with details about the number of clusters, their status, and any alerts that affect them.
 
 :::image type="content" source="media/work-smarter-edge/azure-stack-hci-clusters-summarize.png" alt-text="Screenshot showing Microsoft Copilot for Azure (preview) summarizing Azure Stack HCI clusters.":::
 
-If you follow up by asking "tell me more about the alerts", Microsoft Copilot for Azure (preview) provides more details about the current alerts.
+If you follow up by asking "**tell me more about the alerts**", Microsoft Copilot for Azure (preview) provides more details about the current alerts.
 
 :::image type="content" source="media/work-smarter-edge/azure-stack-hci-clusters-alerts.png" alt-text="Screenshot showing Microsoft Copilot for Azure (preview) providing information about alerts affecting Azure Stack HCI clusters.":::
 

articles/iot-hub/quickstart-bicep-route-messages.md

@@ -131,7 +131,7 @@ This section provides the steps to deploy the Bicep file, create a virtual devic
    ![View the sent messages](./media/horizontal-arm-route-messages/08-messages.png)
 
    > [!NOTE]
-   > These messages are encoded in UTF-32 and base64. If you read the message back, you have to decode it from base64 and utf-32 in order to read it as ASCII. If you're interested, you can use the method ReadOneRowFromFile in the Routing Tutorial to read one for from one of these message files and decode it into ASCII. ReadOneRowFromFile is in the IoT C# SDK repository that you unzipped for this quickstart. Here is the path from the top of that folder: *./iothub/device/samples/getting started/RoutingTutorial/SimulatedDevice/Program.cs* Set the boolean `readTheFile` to true, and hardcode the path to the file on disk, and it will open and translate the first row in the file.
+   > These messages are encoded in UTF-8 and base64. If you read the message back, you have to decode it from base64 and utf-8 in order to read it as ASCII. If you're interested, you can use the method ReadOneRowFromFile in the Routing Tutorial to read one for from one of these message files and decode it into ASCII. ReadOneRowFromFile is in the IoT C# SDK repository that you unzipped for this quickstart. Here is the path from the top of that folder: *./iothub/device/samples/getting started/RoutingTutorial/SimulatedDevice/Program.cs* Set the boolean `readTheFile` to true, and hardcode the path to the file on disk, and it will open and translate the first row in the file.
 
 You have deployed a Bicep file to create an IoT hub and a storage account, and run a program to send messages to the hub. The messages are then automatically stored in the storage account where they can be viewed.
 

articles/storage/blobs/lifecycle-management-overview.md

@@ -21,7 +21,7 @@ Data sets have unique lifecycles. Early in the lifecycle, people access some dat
 
 With the lifecycle management policy, you can:
 
-- Transition blobs from cool, or cold to hot immediately when they're accessed, to optimize for performance.
+- Transition blobs from cool to hot immediately when they're accessed, to optimize for performance.
 - Transition current versions of a blob, previous versions of a blob, or blob snapshots to a cooler storage tier if these objects haven't been accessed or modified for a period of time, to optimize for cost. 
 - Delete current versions of a blob, previous versions of a blob, or blob snapshots at the end of their lifecycles.
 - Define rules to be run once per day at the storage account level.