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

Author: dlepow

articles/ai-services/language-service/media/prompt-flow/prompt-flow-wizard.png

@@ -801,6 +801,8 @@ items:
     href: tutorials/use-kubernetes-service.md
   - name: Use language in power automate flows
     href: tutorials/power-automate.md
+  - name: Use language in prompt flow
+    href: tutorials/prompt-flow.md
   - name: 🆕 Native document support
     items:
     - name: 🆕 Use native documents for language processing

articles/ai-services/language-service/toc.yml

@@ -0,0 +1,73 @@
+---
+title: Use Language in Azure prompt flow
+description: Learn how to use Azure AI Language in prompt flow.
+author: jboback
+ms.author: jboback
+ms.service: azure-ai-language
+ms.topic: how-to
+ms.date: 07/09/2024
+---
+
+# Use Language in Azure prompt flow
+
+> [!IMPORTANT]
+> Some of the features described in this article might only be available in preview. This preview is provided without a service-level agreement, and we don't recommend it for production workloads. Certain features might not be supported or might have constrained capabilities. For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
+
+[Prompt flow in Azure AI Studio](../../../ai-studio/how-to/prompt-flow.md) is a development tool designed to streamline the entire development cycle of AI applications powered by Large Language Models (LLMs). You can explore and quickly start to use and fine-tune various natural language processing capabilities from Azure AI Language, reducing your time to value and deploying solutions with reliable evaluation.
+
+This tutorial teaches you how to use Language in prompt flow utilizing [Azure AI Studio](https://ai.azure.com).                            
+
+## Prerequisites
+
+- An Azure subscription - <a href="https://azure.microsoft.com/free/cognitive-services" target="_blank">Create one for free</a>.
+
+- Access granted to Azure OpenAI in the desired Azure subscription.
+
+     Currently, access to this service is granted only by application. You can apply for access to Azure OpenAI by completing the form at <a href="https://aka.ms/oai/access" target="_blank">https://aka.ms/oai/access</a>. Open an issue on this repo to contact us if you have an issue.
+
+- You need an Azure AI Studio hub or permissions to create one. Your user role must be **Azure AI Developer**, **Contributor**, or **Owner** on the hub. For more information, see [hubs](../../../ai-studio/concepts/ai-resources.md) and [Azure AI roles](../../../ai-studio/concepts/rbac-ai-studio.md).
+     - If your role is **Contributor** or **Owner**, you can [create a hub in this tutorial](#create-a-project-in-azure-ai-studio). 
+     - If your role is **Azure AI Developer**, the hub must already be created. 
+
+- Your subscription needs to be below your [quota limit](../../../ai-studio/how-to/quota.md) to deploy a new flow in this tutorial.
+
+## Create a project in Azure AI Studio
+
+Your project is used to organize your work and save state. 
+
+[!INCLUDE [Create project](../../../ai-studio/includes/create-projects.md)]
+
+## Using Azure AI Language via the prompt flow gallery
+
+You can create an Azure AI Language flow by either cloning the samples available in the gallery or creating a flow from scratch. If you already have flow files in local or file share, you can also import the files to create a flow. For the purposes of this tutorial we'll be using the prebuilt **Analyze Conversations** flow.
+
+To create a prompt flow from the gallery in Azure AI Studio:
+
+1. Sign in to Azure AI Studio and select your project.
+
+1. From the collapsible left menu, select Prompt flow.
+
+1. Select + Create.
+
+1. Find the **Analyze Conversations** tile in the gallery and select *Clone*.
+
+1. In the right sidebar, name the folder and click the **Clone** button.
+
+1. After the process is complete, you'll be taken to the prompt flow wizard. Click **Start Compute Session** in the upper right hand corner to begin. The various parts of the wizard are out lined below:
+
+    :::image type="content" source="../media/prompt-flow/prompt-flow-wizard.png" alt-text="Screenshot of the prompt flow wizard page with each part of the tool numbered." lightbox="../media/prompt-flow/prompt-flow-wizard.png":::
+
+    1. A graph view of your flow.
+    1. Files in your flow. Click the arrow to expand this section.
+    1. Azure AI Language tools in the "More tools" dropdown menu, which you can add capabilities that you need for your flow. There are more tools that you can add from LLM, Prompt, and Python menu. This menu is only accessible after the compute session has started.
+    1. Configure your output.
+    1. Configure steps (or tools) in the flow.
+    1. Run, evaluate, and deploy your flow.
+
+1. Once you've configured everything to your liking, press the run button in the upper right hand corner.
+
+## Related content
+
+* [Azure AI Language homepage](https://aka.ms/azure-language)
+* [Azure AI Language product demo videos](https://aka.ms/language-videos)
+* [Explore Azure AI Language in Azure AI Studio](https://aka.ms/AzureAiLanguage)

articles/ai-services/language-service/tutorials/prompt-flow.md

@@ -22,7 +22,7 @@ This article shows two options for using the Azure CLI to add APIs to your API c
     * Run [az apic api register](/cli/azure/apic/api#az-apic-api-register) to register a new API in your API center.
     * Run [az apic api definition import-specification](/cli/azure/apic/api/definition#az-apic-api-definition-import-specification) to import the API definition to an existing API.
 
-* **Option 2** - Import APIs directly from API Management to your API center using the [az apic import-from-apim](/cli/azure/apic/az-apic-import-from-apim) command.
+* **Option 2** - Import APIs directly from API Management to your API center using the [az apic import-from-apim](/cli/azure/apic#az-apic-import-from-apim) command.
 
 After importing API definitions or APIs from API Management, you can add metadata and documentation in your API center to help stakeholders discover, understand, and consume the API.
 

articles/api-center/import-api-management-apis.md

@@ -133,6 +133,6 @@ To delete individual API versions and definitions, use [az apic api version dele
 
 ## Related content
 
-* See the [Azure CLI reference for Azure API Center](/cli/azure/apic) for a complete command list, including commands to manage [environments](/cli/azure/apic/environment), [deployments](/cli/azure/apic/api/deployment), [metadata schemas](/cli/azure/apic/metadata), and [services](/cli/azure/apic/service).
+* See the [Azure CLI reference for Azure API Center](/cli/azure/apic) for a complete command list, including commands to manage [environments](/cli/azure/apic/environment), [deployments](/cli/azure/apic/api/deployment), [metadata schemas](/cli/azure/apic/metadata), and [services](/cli/azure/apic).
 * [Import APIs to your API center from API Management](import-api-management-apis.md)
 * [Use the Visual Studio extension for API Center](use-vscode-extension.md) to build and register APIs from Visual Studio Code.

articles/api-center/manage-apis-azure-cli.md

@@ -76,7 +76,7 @@ An Azure Automation account in supported public region (except Central India, Ge
 
     > [!NOTE]
     > - When you import a package, it might take several minutes. 100MB is the maximum total size of the files that you can import.
-    > - Use *.zip* files for PowerShell runbook types as mentioned [here](https://learn.microsoft.com/powershell/scripting/developer/module/understanding-a-windows-powershell-module?view=powershell-7.4)
+    > - Use *.zip* files for PowerShell runbook types as mentioned [here](/powershell/scripting/developer/module/understanding-a-windows-powershell-module)
      > - For Python 3.8 packages, use .tar.gz or .whl files targeting cp38-amd64.
      > - For Python 3.10 (preview) packages, use .whl files targeting cp310 Linux OS.
   

articles/automation/manage-runtime-environment.md

@@ -113,10 +113,10 @@ This table shows the language stack versions that are currently supported for Fl
 
 Currently in preview each region in a given subscription has a memory limit of `512,000 MB` for all instances of apps running on Flex Consumption plans. This means that, in a given subscription and region, you could have any combination of instance memory sizes and counts, as long as they stay under the quota limit. For example, each the following examples would mean the quota has been reached and the apps would stop scaling:
 
-+ You have one 2048GB app scaled to 100 and a second 2048GB app scaled to 150 instances
-+ You have one 2048GB app that scaled out to 250 instances
-+ You have one 4096GB app that scaled out to 125 instances
-+ You have one 4096GB app scaled to 100 and one 2048GB app scaled to 50 instances
++ You have one 2,048 MB app scaled to 100 and a second 2,048 MB app scaled to 150 instances
++ You have one 2,048 MB app that scaled out to 250 instances
++ You have one 4,096 MB app that scaled out to 125 instances
++ You have one 4,096 MB app scaled to 100 and one 2,048 MB app scaled to 50 instances
 
 This quota can be increased to allow your Flex Consumption apps to scale further, depending on your requirements. If your apps require a larger quota please create a support ticket.
 

articles/azure-functions/flex-consumption-plan.md

@@ -226,7 +226,7 @@ This is a known issue that occurs on the first upload of Linux data into a Log A
 
 ### Probable causes
 
-A regression in nss-pem package [v1.0.3-5.el7](https://centos.pkgs.org/7/centos-x86_64/nss-pem-1.0.3-7.el7.x86_64.rpm.html) caused a severe performance issue. We've been seeing this issue come up a lot in Redhat/CentOS 7.x distributions. To learn more about this issue, see [1667121 Performance regression in libcurl](https://bugzilla.redhat.com/show_bug.cgi?id=1667121).
+A regression in nss-pem package [v1.0.3-5.el7](https://pkgs.org/download/nss-pem) caused a severe performance issue. We've been seeing this issue come up a lot in Redhat/CentOS 7.x distributions. To learn more about this issue, see [1667121 Performance regression in libcurl](https://bugzilla.redhat.com/show_bug.cgi?id=1667121).
 
 Performance-related bugs don't happen all the time, and they're difficult to reproduce. If you experience such an issue with omiagent, use the script `omiHighCPUDiagnostics.sh`, which will collect the stack trace of the omiagent when it exceeds a certain threshold.
 
@@ -240,7 +240,7 @@ Performance-related bugs don't happen all the time, and they're difficult to rep
 
 ### Resolution
 
-1. Upgrade the nss-pem package to [v1.0.3-5.el7_6.1](https://centos.pkgs.org/7/centos-x86_64/nss-pem-1.0.3-7.el7.x86_64.rpm.html): <br/>
+1. Upgrade the nss-pem package to [v1.0.3-5.el7_6.1](https://pkgs.org/download/nss-pem): <br/>
 `sudo yum upgrade nss-pem`
 
 1. If nss-pem isn't available for upgrade, which mostly happens on CentOS, downgrade curl to 7.29.0-46. If you run "yum update" by mistake, curl will be upgraded to 7.29.0-51 and the issue will happen again: <br/>

articles/azure-monitor/agents/agent-linux-troubleshoot.md

@@ -2532,7 +2532,7 @@ It's not possible to filter telemetry in Java native.
 
 ## Get the trace ID or span ID
 
-You might want to get the trace ID or span ID. If you have logs sent to a destination other than Application Insights, consider adding the trace ID or span ID. Doing so enables better correlation when debugging and diagnosing issues.
+You can obtain the `Trace ID` and `Span ID` of the currently active Span using following steps.
 
 ### [ASP.NET Core](#tab/aspnetcore)
 

articles/azure-monitor/app/opentelemetry-add-modify.md

@@ -14,9 +14,9 @@ Get an authentication token using any of the following methods:
 When requesting a token, you must provide a `resource` parameter. The `resource` parameter is the URL of the resource you want to access. 
 
 Resources include:
-- https://management.azure.com
-- https://api.loganalytics.io
-- https://monitoring.azure.com 
+- `https://management.azure.com`
+- `https://api.loganalytics.io`
+- `https://monitoring.azure.com` 
 
 
 ## [REST](#tab/rest)
@@ -56,7 +56,7 @@ To get a token using CLI, you can use the following command
 az account get-access-token 
 ```
 
-For more information, see [az account get-access-token](/cli/azure/account?view=azure-cli-latest#az-account-get-access-token)
+For more information, see [az account get-access-token](/cli/azure/account#az-account-get-access-token)
 
 ## [SDK](#tab/SDK)
 ### Get a token using the SDKs