changes updated

Author: mmkiran21-git

articles/api-center/TOC.yml

@@ -56,6 +56,8 @@
     href: register-discover-mcp-server.md
   - name: Export API from API Center to Copilot Studio
     href: export-to-copilot-studio.yml
+  - name: Track API dependencies
+    href: track-resource-dependencies.md
 - name: API governance
   items:
   - name: Use metadata for governance

articles/api-center/configure-environments-deployments.md

@@ -101,4 +101,4 @@ In this tutorial, you learned how to use the portal to:
 ## Related content
 
  * [Learn more about Azure API Center](key-concepts.md)
-
+* [Track API resource dependencies](track-resource-dependencies.md)

articles/api-center/includes/api-center-service-limits.md

@@ -7,26 +7,27 @@ author: dlepow
 
 ms.service: azure-api-center
 ms.topic: include
-ms.date: 05/19/2025
+ms.date: 08/22/2025
 ms.author: danlep
 ms.custom: Include file
 ---
 
 | Resource | Free plan<sup>1</sup> | Standard plan<sup>2</sup> |
 | ---------------------------------------------------------------------- | -------------------------- |-------------|
-| Maximum number of APIs | 200 |  10,000 |
-| Maximum number of versions per API | 5 | 100 |
-| Maximum number of definitions per version | 5  | 5 |
-| Maximum number of deployments per API | 10 | 10 |
-| Maximum number of environments | 20 | 20 |
-| Maximum number of workspaces  | 1 (Default) | 1 (Default) |
-| Maximum number of custom metadata properties per entity<sup>3</sup> | 10 | 20 |
-| Maximum number of child properties in custom metadata property of type "object" | 10 |10 | 
-| Maximum requests per minute (data plane) | 3,000 | 6,000  |
-| Maximum number of API definitions [analyzed](../enable-managed-api-analysis-linting.md) | 10 | 2,000<sup>4</sup>  |
-| Maximum number of analysis profiles | 1 | 3 |
-| Maximum number of linked API sources<sup>5</sup> | 1  |  5 |
-| Maximum number of APIs synchronized from a linked API source | 200 | 2,000<sup>4</sup>  |
+| APIs | 200 |  10,000 |
+| Versions per API | 5 | 100 |
+| Definitions per version | 5  | 5 |
+| Deployments per API | 10 | 10 |
+| Environments | 20 | 20 |
+| Workspaces  | 1 (Default) | 1 (Default) |
+| Custom metadata properties per entity<sup>3</sup> | 10 | 20 |
+| Child properties in custom metadata property of type "object" | 10 |10 | 
+| Requests per minute (data plane) | 3,000 | 6,000  |
+| API definitions [analyzed](../enable-managed-api-analysis-linting.md) | 10 | 2,000<sup>4</sup>  |
+| Analysis profiles | 1 | 3 |
+| Linked (integrated) API sources<sup>5</sup> | 1  |  5 |
+| APIs synchronized from a linked API source | 200 | 2,000<sup>4</sup>  |
+| Dependencies | 200 | 200 |
 | Semantic search in API Center portal | No | Yes |
 
 <sup>1</sup> Use of full service features including API analysis is limited.<br/>

articles/api-center/media/track-resource-dependencies/create-dependency.png

@@ -0,0 +1,88 @@
+---
+title: Track API Resource Dependencies - Azure API Center
+description: Learn how to track dependencies between APIs and related resources in your Azure API center.
+ms.service: azure-api-center
+ms.topic: how-to
+ms.date: 08/28/2025
+ms.author: danlep
+author: dlepow
+ms.custom: 
+# Customer intent: As an API developer or API program manager, I want to understand the dependencies between API resources in my organization's API center.
+---
+
+# Track API resource dependencies in your API center 
+
+This article explains how to track the dependencies between APIs and associated resources in your [Azure API center](overview.md). Use the dependency tracker (preview) to map dependencies across APIs, environments, and deployments in your catalog. Also track dependencies on external components including GitHub repositories and other resources in Azure and other cloud platforms.
+
+Each dependency identifies a *source* resource and a related *target* resource that depends on it. By tracking dependencies between source and target resources, you can:
+
+* **Troubleshoot and resolve issues** more effectively by providing visibility into the relationships between components
+
+* **Improve the reliability of systems** by identifying risks such as circular dependencies or over-reliance on single points of failure
+
+* **Improve effectiveness of AI agents** by using mapped dependencies for automatic discovery of valid endpoints for tasks and validating toolchain compatibility
+
+> [!NOTE]
+> This is a preview feature and is subject to change. [Limits](/azure/azure-resource-manager/management/azure-subscription-service-limits?toc=/azure/api-center/toc.json&bc=/azure/api-center/breadcrumb/toc.json#azure-api-center-limits) apply.
+
+## Prerequisites
+
+* An [Azure API center](overview.md) resource in your Azure subscription.
+* Register one or more APIs in your API center. For instructions, see [Register APIs in your API inventory](register-apis.md).
+
+## Add a dependency
+
+Use the dependency tracker in the Azure portal to add a dependency. 
+
+To add a dependency:
+
+1. In the [Azure portal](https://portal.azure.com), navigate to your API center.
+1. In the left menu, under **Assets**, select **Dependency tracker (preview)**.
+1. Select **+ Add Dependency**.
+1. In the **Dependency Manager** window, enter a **Title** and optionally a **Description** of the dependency.
+1. In **Source details**, select a **Source Type** (for example, an API or a related resource). Depending on the type, enter or select identifying information such as a name or ID.
+1. In **Target details**, select a **Target Type** (for example, an API or a related resource). Depending on the type, enter or select identifying information such as a name or ID.
+1. **Save** the dependency.
+
+:::image type="content" source="media/track-resource-dependencies/create-dependency.png" alt-text="Screenshot of adding a dependency in the portal.":::
+
+The dependency is added. 
+
+## View dependencies 
+
+API Center provides a default table view that lists dependencies, and a graphical view with a holistic representation. Use these views to explore the relationships between your resources.
+
+To see a graphical view:
+
+1. In the left menu, under **Assets**, select **Dependency tracker (preview)**.
+1. Select the **Graph View** tab.
+
+In the graphical view, select the box representing any API center resource to see its details.
+
+:::image type="content" source="media/track-resource-dependencies/view-dependency-graph.png" alt-text="Screenshot of the dependency graph in the portal.":::
+
+## Manage dependencies
+
+You can edit or delete dependencies as needed using the table view.
+
+To view or edit dependency details:
+
+1. In the left menu, under **Assets**, select **Dependency tracker (preview)**.
+1. Select **Table View**, and find the dependency you want to edit.
+1. Select **See details**.
+1. To make changes, select **Edit**, and update details.
+1. **Save** your changes.
+
+To delete a dependency:
+
+1. In the **Dependency tracker (preview)** table view, find the dependency that you want to delete.
+1. Select **Delete dependency** (trash can icon).
+1. Confirm the deletion.
+
+> [!NOTE]
+> If you delete an API Center resource that is a source or target in a dependency, the dependency isn't automatically deleted. You must delete it yourself.
+
+## Related content
+
+* [Overview of Azure API center](overview.md)
+* [Register APIs in your API inventory](register-apis.md)

articles/api-center/media/track-resource-dependencies/view-dependency-graph.png

@@ -252,6 +252,8 @@
       href: azure-openai-enable-semantic-caching.md
     - name: Authenticate and authorize to Azure OpenAI
       href: api-management-authenticate-authorize-azure-openai.md
+    - name: Log LLM tokens, requests, and responses
+      href: api-management-howto-llm-logs.md
   - name: Manage MCP servers
     items:
     - name: MCP server capabilities

articles/api-center/track-resource-dependencies.md

@@ -0,0 +1,124 @@
+---
+title: Set Up Logging for LLM APIs in Azure API Management
+titleSuffix: Azure API Management
+description: Enable logging for LLM APIs in Azure API Management to track token usage, prompts, and completions for billing and auditing.
+#customer intent: As a system administrator, I want to enable logging of LLM request and response messages so that I can track API interactions for billing or auditing purposes.
+author: dlepow
+ms.service: azure-api-management
+ms.topic: how-to
+ms.date: 08/22/2025
+ms.author: danlep
+ai-usage: ai-assisted
+ms.collection: ce-skilling-ai-copilot
+ms.custom:
+---
+
+# Log token usage, prompts, and completions for LLM APIs
+
+In this article, you learn how to set up Azure Monitor logging for LLM API requests and responses in Azure API Management. 
+
+The API Management administrator can use LLM API request and response logs along with API Management gateway logs for scenarios such as the following:
+
+* **Calculate usage for billing** - Calculate usage metrics for billing based on the number of tokens consumed by each application or API consumer (for example, segmented by subscription ID or IP address).
+
+* **Inspect messages** - Inspect and analyze prompts and completions to help with debugging, auditing, and model evaluation.
+
+Learn more about:
+
+* [AI gateway capabilities in API Management](genai-gateway-capabilities.md)
+* [Monitoring API Management](monitor-api-management.md)
+
+## Prerequisites
+- An Azure API Management instance.
+- A managed LLM chat completions API integrated with Azure API Management. For example, [Import an Azure AI Foundry API](azure-ai-foundry-api.md).
+- Access to an Azure Log Analytics workspace.
+- Appropriate permissions to configure diagnostic settings and access logs in API Management.
+
+## Enable diagnostic setting for LLM API logs
+
+Enable a diagnostic setting to log requests that the gateway processes for large language model REST APIs. For each request, Azure Monitor receives data about token usage (prompt tokens, completion tokens, and total tokens), the name of the model used, and optionally the request and response messages (prompt and completion). Large requests and responses are split into multiple log entries with sequence numbers for later reconstruction if needed.
+
+The following are brief steps to enable a diagnostic setting that directs LLM API logs to a Log Analytics workspace. For more information, see [Enable diagnostic setting for Azure Monitor logs](monitor-api-management.md#enable-diagnostic-setting-for-azure-monitor-logs).
+
+1. In the [Azure portal](https://portal.azure.com), navigate to your Azure API Management instance.
+1. In the left menu, under **Monitoring**, select **Diagnostic settings** > **+ Add diagnostic setting**.
+1. Configure the setting to send AI gateway logs to a Log Analytics workspace:
+   - Under **Logs**, select **Logs related to generative AI gateway**.
+   - Under **Destination details**, select **Send to Log Analytics workspace**.
+1. Review or configure other settings and make changes if needed.
+1. Select **Save**.
+
+:::image type="content" source="media/api-management-howto-llm-logs/diagnostic-setting.png" alt-text="Screenshot of diagnostic setting for AI gateway logs in the portal.":::
+
+## Enable logging of requests or responses for LLM API
+
+You can enable diagnostic settings for all APIs or customize logging for specific APIs. The following are brief steps to log both LLM requests and response messages for an API. For more information, see [Modify API logging settings](monitor-api-management.md#modify-api-logging-settings).
+
+1. In the left menu of your API Management instance, select **APIs > APIs** and then select the name of the API.
+1. Select the **Settings** tab from the top bar.
+1. Scroll down to the **Diagnostic Logs** section, and select the **Azure Monitor** tab.
+1. In **Log LLM messages**, select **Enabled**.
+1. Select **Log prompts** and enter a size in bytes, such as *32768*.
+1. Select **Log completions** and enter a size in bytes, such as *32768*.
+1. Review other settings and make changes if needed. Select **Save**.
+
+:::image type="content" source="media/api-management-howto-llm-logs/enable-llm-api-logging.png" alt-text="Screenshot of enabling LLM logging for an API in the portal.":::
+
+> [!NOTE]
+> If you enable collection, LLM request or response messages up to 32 KB in size are sent in a single entry. Messages larger than 32 KB are split and logged in 32 KB chunks with sequence numbers for later reconstruction. Request messages and response messages can't exceed 2 MB each.
+
+
+## Review analytics workbook for LLM APIs
+
+The Azure Monitor-based **Analytics** dashboard provides insights into LLM API usage and token consumption using data aggregated in a Log Analytics workspace. [Learn more](monitor-api-management.md#get-api-analytics-in-azure-api-management) about Analytics in API Management.
+
+1. In the left menu of your API Management instance, select **Monitoring** > **Analytics**.
+1. Select the **Language models** tab.
+1. Review metrics and visualizations for LLM API token consumption and requests in a selected **Time range**. 
+
+:::image type="content" source="media/api-management-howto-llm-logs/analytics-workbook-small.png" alt-text="Screenshot of analytics for language model APIs in the portal." lightbox="media/api-management-howto-llm-logs/analytics-workbook.png":::
+
+## Review Azure Monitor logs for requests and responses
+
+Review the [ApiManagementGatewayLlmLog](/azure/azure-monitor/reference/tables/apimanagementgatewayllmlog) log for details about LLM requests and responses, including token consumption, model deployment used, and other details over specific time ranges.
+
+Requests and responses (including chunked messages for large requests and responses) appear in separate log entries that you can correlate by using the `CorrelationId` field. 
+
+For auditing purposes, use a Kusto query similar to the following query to join each request and response in a single record. Adjust the query to include the fields that you want to track.
+
+```Kusto
+ApiManagementGatewayLlmLog
+| extend RequestArray = parse_json(RequestMessages)
+| extend ResponseArray = parse_json(ResponseMessages)
+| mv-expand RequestArray
+| mv-expand ResponseArray
+| project
+    CorrelationId,
+    RequestContent = tostring(RequestArray.content),
+    ResponseContent = tostring(ResponseArray.content)
+| summarize
+    Input = strcat_aray(make_list(RequestContent), " . "),
+    Output = strcat_array(make_list(ResponseContent), " . ")
+    by CorrelationId
+| where isnotempty(Input) and isnotempty(Output)
+```
+
+:::image type="content" source="media/api-management-howto-llm-logs/llm-log-query-small.png" alt-text="Screenshot of query results for LLM logs in the portal." lightbox="media/api-management-howto-llm-logs/llm-log-query.png":::
+
+## Upload data to Azure AI Foundry for model evaluation
+
+You can export LLM logging data as a dataset for [model evaluation](/azure/ai-foundry/concepts/observability) in Azure AI Foundry. With model evaluation, you can assess the performance of your generative AI models and applications against a test model or dataset using built-in or custom evaluation metrics. 
+
+To use LLM logs as a dataset for model evaluation:
+
+1. Join LLM request and response messages into a single record for each interaction, as shown in the [previous section](#review-azure-monitor-logs-for-requests-and-responses). Include the fields you want to use for model evaluation.
+1. Export the dataset to CSV format, which is compatible with Azure AI Foundry.
+1. In the Azure AI Foundry portal, create a new evaluation to upload and evaluate the dataset.
+
+For details to create and run a model evaluation in Azure AI Foundry, see [Evaluate generative AI models and applications by using Azure AI Foundry](/azure/ai-foundry/how-to/evaluate-generative-ai-app).
+
+## Related content
+
+* [Learn more about monitoring API Management](monitor-api-management.md)
+* [Azure Monitor reference for API Management](monitor-api-management-reference.md)
+* [Tutorial: Monitor published APIs](api-management-howto-use-azure-monitor.md)

articles/api-management/TOC.yml

@@ -109,14 +109,14 @@ In API Management, enable semantic caching by using Azure Redis Enterprise, Azur
 
 ## Logging token usage, prompts, and completions
 
-Enable a [diagnostic setting](monitor-api-management.md#enable-diagnostic-setting-for-azure-monitor-logs) in your API Management instance to log requests processed by the gateway for large language model REST APIs. For each request, data is sent to Azure Monitor including token usage (prompt tokens, completion tokens, and total tokens), name of the model used, and optionally the request and response messages (prompt and completion). Large requests and responses are split into multiple log entries that are sequentially numbered for later reconstruction if needed.
+You can enable logging for requests processed by the gateway for large language model REST APIs. For each request, data is sent to Azure Monitor including token usage (prompt tokens, completion tokens, and total tokens), name of the model used, and optionally the request and response messages (prompt and completion). Large requests and responses are split into multiple log entries that are sequentially numbered for later reconstruction if needed.
 
 The API Management administrator can use LLM gateway logs along with API Management gateway logs for scenarios such as the following:
 
 * **Calculate usage for billing** - Calculate usage metrics for billing based on the number of tokens consumed by each application or API consumer (for example, segmented by subscription ID or IP address).
 * **Inspect messages** - To help with debugging or auditing, inspect and analyze prompts and completions.
 
-Learn more about [monitoring API Management with Azure Monitor](monitor-api-management.md).
+Learn more: [Log token usage, prompts, and completions for LLM APIs](api-management-howto-llm-logs.md)
 
 ## Content safety policy
 
@@ -135,7 +135,7 @@ To help safeguard users from harmful, offensive, or misleading content, you can
 
 * [AI gateway reference architecture using API Management](/ai/playbook/technology-guidance/generative-ai/dev-starters/genai-gateway/reference-architectures/apim-based)
 * [AI hub gateway landing zone accelerator](https://github.com/Azure-Samples/ai-hub-gateway-solution-accelerator)
-* [Designing and implementing a gateway solution with Azure OpenAI resources](/ai/playbook/technology-guidance/generative-ai/dev-starters/genai-gateway/)
+* [Designing and implementing a gateway solution with Azure OpenAI resources](/ai/playbook/technology-guidance/generative-ai/dev-starters/gemonitoring API Management with Azurenai-gateway/)
 * [Use a gateway in front of multiple Azure OpenAI deployments or instances](/azure/architecture/ai-ml/guide/azure-openai-gateway-multi-backend)
 
 ## Related content