Merge pull request #307361 from MicrosoftDocs/main

Auto Publish – main to live - 2025-10-24 22:00 UTC

Author: learn-build-service-prod[bot]

articles/api-center/TOC.yml

@@ -33,6 +33,8 @@
       href: ./tutorials/register-apis.md
     - name: 3 - Add environments and deployments
       href: ./tutorials/configure-environments-deployments.md
+    - name: 4 - Link an API Management instance
+      href: ../api-management/tutorials/link-api-center.md
   expanded: true
 - name: API inventory
   items:
@@ -121,4 +123,4 @@
   - name: Azure updates
     href: https://aka.ms/apic/updates
   - name: MCP Center
-    href: https://mcp.azure.com
+    href: https://mcp.azure.com

articles/api-management/TOC.yml

@@ -63,6 +63,8 @@
       href: api-management-howto-developer-portal-customize.md
     - name: 10 - Manage APIs in Visual Studio Code
       href: visual-studio-code-tutorial.md
+    - name: 11 - Link to an API Center
+      href: tutorials/link-api-center.md
   expanded: true
 - name: Deployment and operations
   items:

articles/api-management/api-management-authenticate-authorize-azure-openai.md

@@ -23,7 +23,7 @@ In this article, you learn about ways to authenticate and authorize to Azure Ope
 
 For background, see:
 
-* [Azure OpenAI Service REST API reference](/azure/ai-services/openai/reference)
+* [Azure OpenAI Service REST API reference](/azure/ai-foundry/openai/reference)
 
 * [Authentication and authorization to APIs in API Management](authentication-authorization-overview.md).
 
@@ -80,13 +80,13 @@ In this example, the named value in API Management is *openai-api-key*.
 ## Authenticate with managed identity
 
 An alternative and recommended way to authenticate to an Azure OpenAI API is by using a managed identity in Microsoft Entra ID. For background, see
-[How to configure Azure OpenAI Service with managed identity](/azure/ai-services/openai/how-to/managed-identity).
+[How to configure Azure OpenAI Service with managed identity](/azure/api-management/api-management-authenticate-authorize-azure-openai).
 
 Following are steps to configure your API Management instance to use a managed identity to authenticate requests to an Azure OpenAI API. 
 
 1. [Enable](api-management-howto-use-managed-service-identity.md) a system-assigned or user-assigned managed identity for your API Management instance. The following example assumes that you've enabled the instance's system-assigned managed identity.
 
-1. Assign the managed identity the **Cognitive Services OpenAI User** role, scoped to the appropriate resource. For example, assign the system-assigned managed identity the **Cognitive Services OpenAI User** role on the Azure OpenAI resource. For detailed steps, see [Role-based access control for Azure OpenAI service](/azure/ai-services/openai/how-to/role-based-access-control).
+1. Assign the managed identity the **Cognitive Services OpenAI User** role, scoped to the appropriate resource. For example, assign the system-assigned managed identity the **Cognitive Services OpenAI User** role on the Azure OpenAI resource. For detailed steps, see [Role-based access control for Azure OpenAI service](/azure/ai-foundry/openai/how-to/role-based-access-control).
 
 1. Add the following policy snippet in the `inbound` policy section to authenticate requests to the Azure OpenAI API using the managed identity. 
 
@@ -163,5 +163,5 @@ Following are high level steps to restrict API access to users or apps that are
 
 ## Related content
 
-* Learn more about [Microsoft Entra ID and OAuth2.0](../active-directory/develop/authentication-vs-authorization.md).  
+* Learn more about [Microsoft Entra ID and OAuth2.0](/entra/architecture/auth-oauth2).  
 * [Authenticate requests to Azure AI services](/azure/ai-services/authentication)

articles/api-management/azure-openai-enable-semantic-caching.md

@@ -19,7 +19,7 @@ ms.collection: ce-skilling-ai-copilot
 Enable semantic caching of responses to Azure OpenAI API requests to reduce bandwidth and processing requirements imposed on the backend APIs and lower latency perceived by API consumers. With semantic caching, you can return cached responses for identical prompts and also for prompts that are similar in meaning, even if the text isn't the same. For background, see [Tutorial: Use Azure Cache for Redis as a semantic cache](../redis/tutorial-semantic-cache.md).
 
 > [!NOTE]
-> The configuration steps in this article enable semantic caching for Azure OpenAI APIs. These steps can be generalized to enable semantic caching for corresponding large language model (LLM) APIs available through the [Azure AI Model Inference API](/azure/ai-studio/reference/reference-model-inference-api) or with OpenAI-compatible models served through third-party inference providers. 
+> The configuration steps in this article enable semantic caching for Azure OpenAI APIs. These steps can be generalized to enable semantic caching for corresponding large language model (LLM) APIs available through the [Azure AI Model Inference API](/rest/api/aifoundry/modelinference/) or with OpenAI-compatible models served through third-party inference providers. 
 
 ## Prerequisites
 

articles/api-management/genai-gateway-capabilities.md

@@ -67,7 +67,7 @@ More information:
 
 * [Import an AI Foundry API](azure-ai-foundry-api.md)
 * [Import a language model API](openai-compatible-llm-api.md)
-* [Export a REST API as an MCP server](export-rest-mcp-server.md)
+* [Expose a REST API as an MCP server](export-rest-mcp-server.md)
 * [Expose and govern an existing MCP server](expose-existing-mcp-server.md)
 
 ## Scalability and performance

articles/api-management/tutorials/link-api-center.md

@@ -0,0 +1,95 @@
+---
+title: Create or link an API Center from the Azure portal
+description: "How to create a new API Center or link an existing API Center to an API Management service from the Azure portal."
+author: ProfessorKendrick
+ms.author: kkendrick
+ms.service: azure-api-management
+ms.topic: tutorial  
+ms.date: 10/20/2025
+
+#customer intent: As an API Management administrator, I want to create or link an API Center so that I can discover, reuse, and govern APIs across linked services.
+
+---
+
+# Tutorial: Create or link an API Center to API Management
+
+This tutorial shows how to integrate an Azure API Management instance with an Azure API Center. When linked, the API Management instance's APIs — and optional API definitions — are continuously synchronized into the API Center inventory. API Center is a central catalog and governance hub for APIs and related artifacts, and API Management customers use it to discover and reuse APIs, share definitions across teams, and apply consistent governance and lifecycle policies.
+
+> [!NOTE]
+> 
+> Only one API Center can be linked to a single API Management instance.
+
+In this tutorial, you:
+
+> [!div class="checklist"]
+> * Create a new API Center and link it to an API Management instance
+> * Link an existing API Center and synchronize APIs
+> * View synchronized APIs and remove the link if needed
+
+## Prerequisites
+
+Before you start, make sure you meet the following requirements.
+
+- An Azure account with an active subscription is required. If you don't already have one, you can [create an account for free](https://azure.microsoft.com/pricing/purchase-options/azure-account).
+- An existing API Management service in the subscription where you want to manage APIs
+- Contributor (or Owner) permissions on the API Management resource and permission to create resources in a resource group
+
+## Create a new API Center and link your APIs
+
+These steps show how to create a new API Center and link it to an API Management instance so APIs are synchronized.
+
+1. From the [Azure portal](https://portal.azure.com), open your API Management service.
+1. In the left-hand menu, go to **APIs** > **API Center**.
+    :::image type="content" source="media/link-api-center/api-management-menu.png" alt-text="The API Management instance in Azure portal with API Center emphasized in the left-hand menu.":::
+1. In the center pane, under *Use API Center for API discovery, reuse, and governance*, select **Create new**.
+1. On the **Create API Center** page, select **Create new link**.
+1. Provide values for the following fields:
+
+    | Field | Details |
+    |---|---|
+    | Resource group | Select an existing resource group or create a new one. |
+    | Location | Choose a region. Regions available for API Center may differ from the region of your API Management instance. |
+    | Name | Provide a unique name for the API Center instance. |
+    | Pricing plan | Select a plan. |
+    | Lifecycle | Select the lifecycle state to associate with APIs when they're synchronized. This metadata can be changed later. |
+
+1. Select Create. 
+
+    - When the operation finishes, you should see a *Request succeeded* message and a confirmation that your API Management service and API Center are synchronized.
+
+## Use an existing API Center
+
+These steps show how to link an API Management instance to an API Center that already exists.
+
+1. From the API Center section of your API Management service, select **Use existing API Center**.
+1. From the dropdown, choose the API Center you want to link.
+1. Select **Synchronize APIs** to start synchronization between the API Management service and the selected API Center.
+
+## View linked API Center and synchronized APIs
+
+Use this section to verify the integration state and to view APIs that synchronized from API Management.
+
+1. In the [Azure portal](https://portal.azure.com), open the API Center resource.
+2. In the API Center left-hand menu, go to **Platforms** > **Integrations**. 
+    The state for the integration with API Management should say *Linked and syncing*. 
+1. To view synchronized APIs, go to **Assets** > **APIs**.<br />
+    An icon appears indicating that the APIs are linked.
+    :::image type="content" source="media/link-api-center/api-center-menu.png" alt-text="An API Center instance in Azure portal with APIs emphasized in the left-hand menu and link icons emphasized in the main panel":::
+
+## Remove link to API Center
+
+Follow these steps to remove the link between API Management and the API Center or to delete the API Center resource.
+
+1. In the API Center resource, find the linked API Management instance.
+1. In the left-hand menu, go to **Platforms** > **Integrations**.
+2. Select the trash can icon to delete the link.
+
+## Clean up resources
+
+Delete any resources you created for this tutorial to avoid incurring charges.
+
+If you created an API Center for this tutorial and no longer need it, delete the API Center resource and any resource group you created to avoid charges.
+
+## Related content
+
+[Synchronize APIs from an API Management instance](../../api-center/synchronize-api-management-apis.md)

articles/api-management/tutorials/media/link-api-center/api-center-menu.png

@@ -3,7 +3,7 @@ title: Configure App Service Environments and Isolated v2 App Service Plans for
 description: Learn how to configure zone redundancy for App Service Environments and Isolated v2 App Service plans to boost reliability and minimize service disruption.
 ms.topic: conceptual
 ms.service: azure-app-service
-ms.date: 07/16/2025
+ms.date: 10/24/2025
 author: anaharris
 ms.author: anaharris
 
@@ -67,7 +67,7 @@ For more information about zone redundancy, see [Reliability in an App Service E
     ---
     
     > [!NOTE]
-    > A zone redundancy status change in an App Service Environment takes 12 to 24 hours to complete. During the upgrade process, no downtime or performance problems occur.
+    > A zone redundancy status change in an App Service Environment takes 12 to 24 hours to complete. During the upgrade process, no downtime or performance problems occur. However, all App Service plans with fewer than 3 instances are scaled to 3 instances. Any plan with 3 or more instances remains unchanged. Once the operation to enable zone redundancy completes, you can scale your App Service plans as needed, including to fewer than 3 instances.
 
 ### Check for zone redundancy support for an App Service Environment
 

articles/api-management/tutorials/media/link-api-center/api-management-menu.png

@@ -0,0 +1,74 @@
+---
+title: Copilot Credit P3
+description: Learn about Copilot Credit P3 in Azure reservations.
+author: pri-mittal
+ms.reviewer: primittal
+ms.service: cost-management-billing
+ms.subservice: reservations
+ms.topic: conceptual
+ms.date: 10/08/2025
+ms.author: primittal
+---
+
+# Optimize Copilot Credit costs with a pre-purchase plan
+
+Save on your Copilot Credit costs when you buy a pre-purchase plan. Pre-purchase plans are commit units (CUs) bought at discounted tiers in your purchasing currency for a specific product. The more you buy, the greater the discount. Purchased CUs pay down qualifying costs in US dollars (USD). So, if Microsoft Copilot Studio generates a retail cost of $100 based on Copilot Credit usage, then 100 Copilot Credit CUs (CCCUs) are consumed.
+
+Your Copilot Credit pre-purchase plan automatically uses your CCCUs to pay for eligible Copilot Credit usage during its one-year term or until Copilot Credit CUs run out. Your pre-purchase plan Copilot Credit CUs start paying for your Copilot usage without having to redeploy or reassign the plan. By default, plans are configured to renew at the end of the one-year term.
+
+## Prerequisites
+
+To buy a pre-purchase plan, you must have one of the following Azure subscriptions and roles:
+- For an Azure subscription, the owner role or reservation purchaser role is required.
+- For an Enterprise Agreement (EA) subscription, the [**Reserved Instances** policy option](../manage/direct-ea-administration.md#view-and-manage-enrollment-policies) must be enabled. To enable that policy option, you must be an EA administrator of the subscription.
+- For a Cloud Solution Provider (CSP) subscription, follow one of these articles:
+   - [Buy Azure reservations on behalf of a customer](/partner-center/customers/azure-reservations-buying)
+   - [Allow the customer to buy their own reservations](/partner-center/customers/give-customers-permission)
+
+## Determine the right size to buy
+
+To get started, estimate your expected Copilot Credit usage. This helps you determine the appropriate size for your pre-purchase plan. Each pre-purchase plan has a one-year term.
+
+For example, suppose you expect to consume 1,500,000 Copilot Credit with custom agents created in Microsoft Copilot Studio. Assuming the pay-as-you-go rate for Copilot Credit to be $0.01, then at the pay-as-you-go rate, this will cost $15,000. By purchasing Tier 2 (15,000 CU) pre-purchase plan, let's say the cost of that tier is $14,100, it will give a 6% saving compared to the pay-as-you-go rate for the same usage.
+
+## Purchase Copilot Credit commit units
+
+Purchase Copilot Credit pre-purchase plans in the [Azure portal reservations](https://portal.azure.com/#view/Microsoft_Azure_Reservations/ReservationsBrowseBlade/productType/Reservations). 
+
+1. Go to the [Azure portal](https://portal.azure.com)
+2. Navigate to the **Reservations** service.
+3. On the **Purchase reservations page**, select **Copilot Credit Pre-Purchase Plan**.  
+   :::image type="content" source="./media/copilot-credit/copilot-credit.png" alt-text="Screenshot showing Copilot Credit pre-purchase plan." lightbox="./media/copilot-credit/copilot-credit.png":::
+4. On the **Select the product you want to purchase** page, select a subscription. Use the **Subscription** list to select the subscription used to pay for the reserved capacity. The payment method of the subscription is charged the upfront costs for the reserved capacity. Charges **not** are deducted from the enrollment's Azure Prepayment (previously called monetary commitment) balance or charged as overage.
+5. Select a scope.
+   - **Single resource group scope** - Applies the reservation discount to the matching resources in the selected resource group only.
+   - **Single subscription scope** - Applies the reservation discount to the matching resources in the selected subscription.
+   - **Shared scope** - Applies the reservation discount to matching resources in eligible subscriptions that are in the billing context. For Enterprise Agreement customers, the billing context is the enrollment.
+   - **Management group** - Applies the reservation discount to the matching resource in the list of subscriptions that are a part of both the management group and billing scope.
+6. Select how many Copilot Credit commit units you want to purchase.
+
+   :::image type="content" source="./media/copilot-credit/copilot-credit-discount.png" alt-text="Screenshot showing Copilot Credit pre-purchase plan discount tiers and their term lengths." lightbox="./media/copilot-credit/copilot-credit-discount.png":::
+
+7. Choose to automatically renew the pre-purchase reservation. *The setting is configured to renew automatically by default*. For more information, see [Renew a reservation](reservation-renew.md).
+
+## Change scope and ownership
+
+You can make the following types of changes to a reservation after purchase:
+
+- Update reservation scope
+- Update who can view or manage the reservation. For more information, see [Who can manage a reservation by default](manage-reserved-vm-instance.md#who-can-manage-a-reservation-by-default).
+
+You can't split or merge a **Copilot Credit Pre-Purchase Plan**. For more information about managing reservations, see [Manage reservations after purchase](manage-reserved-vm-instance.md).
+
+## Cancellations and exchanges
+
+Cancel and exchange operations aren't supported for **Copilot Credit Pre-Purchase Plans**. All purchases are final.
+
+## Related content
+
+To learn more about Azure Reservations, see the following articles:
+- [What are Azure Reservations?](save-compute-costs-reservations.md)
+- [Manage Reservations for Azure resources](manage-reserved-vm-instance.md)
+
+To learn more about Copilot Credit costs, see [Plan costs and understand Copilot Credit pricing and billing](https://learn.microsoft.com/microsoft-copilot-studio/requirements-messages-management).
+