Merge pull request #314375 from MicrosoftDocs/main

Auto Publish – main to live - 2026-04-07 06:00 UTC

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

articles/api-center/media/register-discover-mcp-server/mcp-server-portal-small.png

@@ -4,7 +4,7 @@ description: Learn about how Azure API Center can be a centralized registry for
 
 ms.service: azure-api-center
 ms.topic: concept-article
-ms.date: 02/20/2026
+ms.date: 04/02/2026
 
 ms.collection: ce-skilling-ai-copilot
 ms.update-cycle: 180-days
@@ -126,6 +126,7 @@ To build MCP servers by using Azure compute services and register them in your A
 Set up your [API Center portal](set-up-api-center-portal.md) so that developers and other stakeholders in your organization can discover MCP servers in your API inventory. From the API Center portal, users can do the following:
 - Browse and filter MCP servers in the inventory.
 - For remote MCP servers, view details such as the URL endpoint of the MCP server and API definition, and install the MCP server in their Visual Studio Code environment.
+- A built-in MCP Inspector tool allows users to test MCP server endpoints and view the responses directly in the portal. On the **Options** tab of an MCP server details page, select **View documentation** to access the MCP Inspector.
 
 :::image type="content" source="media/register-discover-mcp-server/mcp-server-portal-small.png" lightbox="media/register-discover-mcp-server/mcp-server-portal.png" alt-text="Screenshot of MCP server in API Center portal.":::
 

articles/api-center/media/register-discover-mcp-server/mcp-server-portal.png

@@ -4,7 +4,7 @@ description: How to set up the API Center portal, a managed website that enables
 
 ms.service: azure-api-center
 ms.topic: how-to
-ms.date: 02/25/2026
+ms.date: 04/02/2026
 ms.update-cycle: 180-days
 
 ms.custom: 
@@ -19,7 +19,7 @@ This article shows you how to set up and customize the *API Center portal* (prev
 The API Center portal supports and streamlines the work of developers who use and create APIs within your organization. Users with access can:
 
 * **Search for APIs** by name or use AI-assisted semantic search.
-* **Filter APIs** by type or lifecycle stage.
+* **Filter APIs** by type, lifecycle stage, and other properties.
 * **View API details and definitions** including endpoints, methods, parameters, and response formats.
 * **Download API definitions** to their computer or open in Visual Studio Code.
 * **Try out APIs** with API key or OAuth 2.0 authentication.
@@ -66,6 +66,9 @@ After configuring access, open the API Center portal by selecting **View API Cen
 
 By default, the portal home page is publicly reachable. If Microsoft Entra ID is configured for access, users must select **Sign-in** to access APIs. See [Enable sign-in to portal by Microsoft Entra users and groups](#enable-sign-in) for details on configuring user access.
 
+* Add filters on the home page to display assets of certain types or that match certain metadata values.
+* Select an API or other registered asset to view its details, such as endpoints, methods, parameters, and response formats. You can also download API definitions or open them in Visual Studio Code.
+
 <a id="enable-sign-in"></a>
 ## Enable sign-in to portal by Microsoft Entra users and groups 
 

articles/api-center/media/self-host-api-center-portal/api-center-portal-signed-in.png

@@ -130,7 +130,7 @@ For the complete code example, see the [Azure Functions MCP Extension repo](http
 ::: zone pivot="programming-language-java"
 
 > [!IMPORTANT]
-> The MCP extension in Java doesn't_ support resource today.
+> The MCP extension in Java supports resource today. Documentation coming soon.
 
 ::: zone-end
 
@@ -216,15 +216,7 @@ app.mcpTool("getWeather", {
 For the complete code example, see [weatherMcpApp.ts](https://github.com/Azure-Samples/remote-mcp-functions-typescript/blob/McpAppDemo/src/functions/weatherMcpApp.ts).
 
 > [!IMPORTANT]
-> The MCP resource trigger for TypeScript currently requires version `4.12.0-preview.2` or later of the [`@azure/functions`](https://www.npmjs.com/package/@azure/functions/v/4.12.0-preview.2) package.
-> It also requires version `[4.32.0, 5.0.0)` of the preview exetnsion bundle. Make sure to update your `host.json` to use this preview bundle and version:
->
-> ```json
-> "extensionBundle": {
->   "id": "Microsoft.Azure.Functions.ExtensionBundle.Preview",
->   "version": "[4.32.0, 5.0.0)"
-> }
-> ```
+> The MCP resource trigger for TypeScript requires version `4.12.0` or later of the [`@azure/functions`](https://www.npmjs.com/package/@azure/functions/v/4.12.0) package.
 
 ::: zone-end  
 
@@ -290,17 +282,7 @@ def get_weather(location: str) -> Dict[str, Any]:
 For the complete code example, see [function_app.py](https://github.com/Azure-Samples/remote-mcp-functions-python/blob/main/src).
 
 > [!NOTE]
-> The MCP resource trigger for Python requires version `1.25.0b3` or later of the [`azure-functions`](https://pypi.org/project/azure-functions/1.25.0b3/) package. 
-> It also requires version `[4.32.0, 5.0.0)` of the preview exetnsion bundle. Make sure to update your `host.json` to use this preview bundle and version:
->
-> ```json
-> "extensionBundle": {
->   "id": "Microsoft.Azure.Functions.ExtensionBundle.Preview"
->   "version": "[4.32.0, 5.0.0)"
-> }
-> ```
->
-> If the app is using Python 3.9-3.12, add the `PYTHON_ISOLATE_WORKER_DEPENDENCIES: 1` app setting to `local.settings.json` and to app settings when running in Azure.
+> The MCP resource trigger for Python requires version `2.0.0` or later of the [`azure-functions`](https://pypi.org/project/azure-functions/) package and using **Python 3.13** or above. 
 
 ::: zone-end
 

articles/api-center/register-discover-mcp-server.md

@@ -198,9 +198,9 @@ You can view the complete project template in the [Azure Functions Java MCP Serv
 ::: zone pivot="programming-language-python"
 The function code for the MCP server tools is defined in the `src/function_app.py` file. The MCP function annotations expose these functions as MCP Server tools:
 
-<!- >:::code language="python" source="~/functions-scenarios-custom-mcp-python/src/function_app.py" range="30-33" ::: >
+<!-- :::code language="python" source="~/functions-scenarios-custom-mcp-python/src/function_app.py" range="30-33" ::: -->
 
-<!- >:::code language="python" source="~/functions-scenarios-custom-mcp-python/src/function_app.py" range="36-60" ::: >
+<!-- :::code language="python" source="~/functions-scenarios-custom-mcp-python/src/function_app.py" range="36-60" ::: -->
 
 You can view the complete project template in the [Azure Functions Python MCP Server](https://github.com/Azure-Samples/remote-mcp-functions-python) GitHub repository.
 ::: zone-end   

articles/api-center/set-up-api-center-portal.md

@@ -250,15 +250,15 @@ You can view the complete project template in the [Azure Functions .NET MCP Serv
 ::: zone pivot="programming-language-python"
 The function code for the MCP Apps weather tool is defined in the `src/function_app.py` file. In this function, the `metadata` parameter on `@app.mcp_tool()` adds UI metadata to the `get_weather` tool.
 
-<!- >:::code language="python" source="~/functions-scenarios-custom-mcp-python/src/function_app.py" range="109-130" ::: >
+<!-- :::code language="python" source="~/functions-scenarios-custom-mcp-python/src/function_app.py" range="109-130" ::: -->
 
 The `@app.mcp_resource_trigger()` decorator is applied to the `get_weather_widget` function, which serves the HTML widget.
 
-<!- >:::code language="python" source="~/functions-scenarios-custom-mcp-python/src/function_app.py" range="64-105" ::: >
+<!-- :::code language="python" source="~/functions-scenarios-custom-mcp-python/src/function_app.py" range="64-105" ::: -->
 
 The `TOOL_METADATA` constant declares a `ui.resourceUri` that tells the MCP host to fetch the interactive UI from `ui://weather/index.html` after the tool runs.
 
-<!- >:::code language="python" source="~/functions-scenarios-custom-mcp-python/src/function_app.py" range="20-21" ::: >
+<!-- :::code language="python" source="~/functions-scenarios-custom-mcp-python/src/function_app.py" range="20-21" ::: -->
 
 The `get_weather_widget` function serves the bundled HTML file at that URI using `@app.mcp_resource_trigger()`.
 

articles/azure-functions/functions-bindings-mcp-resource-trigger.md

@@ -22,9 +22,6 @@ You typically need to write code to collect, store, and refresh tokens in your a
 
 When token store is enabled, the Container Apps authentication system caches ID tokens, access tokens, and refresh tokens the authenticated session, and they're accessible only by the associated user.
 
-> [!NOTE]
-> The token store feature is in preview.
-
 ## Generate a SAS URL
 
 Before you can create a token store for your container app, you first need an Azure Storage account with a private blob container.
@@ -79,7 +76,7 @@ az containerapp auth update \
   --token-store true
 ```
 
-Additionally, you can create your token store with the `sasUrlSettingName` property using an [ARM template](/azure/templates/microsoft.app/2023-11-02-preview/containerapps/authconfigs?pivots=deployment-language-arm-template#blobstoragetokenstore-1).
+Additionally, you can create your token store with the `sasUrlSettingName` property using an [ARM template](/azure/templates/microsoft.app/containerapps/authconfigs?pivots=deployment-language-arm-template#blobstoragetokenstore-1).
 
 ## Next steps
 

articles/azure-functions/scenario-custom-remote-mcp-server.md

@@ -29,15 +29,15 @@ In addition to TLS, when you interact with Azure Data Manager for Energy, all tr
 
 ## Set up Customer Managed Keys (CMK) for Azure Data Manager for Energy instance
 > [!IMPORTANT]
-> You can't edit CMK settings once the Azure Data Manager for Energy instance is created.
+> The key vault and the user assigned identity must be in the same region as that of the Azure Data Manager for Energy instance. CMK can only be enabled only at the time of instance creation. 
 
 ### Prerequisites
 
 **Step 1: Configure the key vault**
 
 1. You can use a new or existing key vault to store customer-managed keys. To learn more about Azure Key Vault, see [Azure Key Vault Overview](/azure/key-vault/general/overview) and [What is Azure Key Vault](/azure/key-vault/general/basic-concepts)?
 2. Using customer-managed keys with Azure Data Manager for Energy requires that both soft delete and purge protection are enabled for the key vault. Soft delete is enabled by default when you create a new key vault and can't be disabled. You can enable purge protection when you create the key vault or afterwards.
-3. To learn how to create a key vault with the Azure portal, see [Quickstart: Create a key vault using the Azure portal](/azure/key-vault/general/quick-create-portal). When you create the key vault, select Enable purge protection.
+3. To learn how to create a key vault with the Azure portal, see [Quickstart: Create a key vault using the Azure portal](/azure/key-vault/general/quick-create-portal). The key vault must be in the same region as that of the Azure Data Manager for Energy instance. When you create the key vault, select Enable purge protection.
 
    [![Screenshot of enabling purge protection and soft delete while creating key vault](media/how-to-manage-data-security-and-encryption/customer-managed-key-1-create-key-vault.png)](media/how-to-manage-data-security-and-encryption/customer-managed-key-1-create-key-vault.png#lightbox)
 
@@ -71,7 +71,7 @@ In addition to TLS, when you interact with Azure Data Manager for Energy, all tr
     [![Screenshot showing selection of subscription, key vault, and key in the right pane that opens after choosing 'select a key vault and key'](media/how-to-manage-data-security-and-encryption/customer-managed-key-3aa-enable-cmk.png)](media/how-to-manage-data-security-and-encryption/customer-managed-key-3aa-enable-cmk.png#lightbox)
 
 8.	Next, select the user-assigned managed identity that is used to authorize access to the key vault that contains the key. 
-9.	Select "**Select a user identity**" Select the user-assigned managed identity that you created in the prerequisites. 
+9.	Select "**Select a user identity**" Select the user-assigned managed identity that you created in the prerequisites. The user-assigned managed identity must be created in the same region as the Azure Data Manager for Energy instance. 
     [![Screenshot of key vault, key, user assigned identity, and CMK on encryption tab.](media/how-to-manage-data-security-and-encryption/customer-managed-key-3bb-select-managed-identity.png)](media/how-to-manage-data-security-and-encryption/customer-managed-key-3bb-select-managed-identity.png#lightbox)
 
 10.	This user assigned identity must have _get key_, _list key_, _wrap key_, and _unwrap key_ permissions on the key vault. For more information on assigning Azure Key Vault access policies, see [Assign a Key Vault Access Policy](/azure/key-vault/general/assign-access-policy).