Merge branch 'release-microsoft-discovery' into release-microsoft-discovery

Author: anzaman

.openpublishing.redirection.json

@@ -1,5 +1,144 @@
 {
   "redirections": [
+    {
+      "source_path": "articles/web-application-firewall/ag/web-application-firewall-troubleshoot.md",
+      "redirect_url": "/troubleshoot/azure/web-application-firewall/web-application-firewall-troubleshoot",
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/concepts-machine-learning.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/concepts-machine-learning",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/concepts-power-bi.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/concepts-power-bi",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/concepts-teams.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/concepts-teams",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/configure-metrics.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/configure-metrics",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/deploy-arm-template.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/deploy-arm-template",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/deploy-bicep-powershell-cli.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/deploy-bicep-powershell-cli",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/deploy-choose-method.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/deploy-choose-method",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/deploy-json-powershell-cli.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/deploy-json-powershell-cli",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/deploy-manual-portal.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/deploy-manual-portal",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/device-messages-through-iot-hub.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/device-messages-through-iot-hub",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/frequently-asked-questions.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/frequently-asked-questions",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/get-started.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/get-started",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/git-projects.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/git-projects",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/how-to-enable-diagnostic-settings.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/how-to-enable-diagnostic-settings",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/how-to-use-calculatedcontent-templates.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/how-to-use-calculatedcontent-templates",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/how-to-use-custom-functions.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/how-to-use-custom-functions",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/how-to-use-iotjsonpathcontent-templates.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/how-to-use-iotjsonpathcontent-templates",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/how-to-use-mapping-debugger.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/how-to-use-mapping-debugger",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/how-to-use-monitoring-and-health-checks-tabs.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/how-to-use-monitoring-and-health-checks-tabs",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/index.yml",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/index",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/overview-of-device-data-processing-stages.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/overview-of-device-data-processing-stages",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/overview-of-device-mapping.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/overview-of-device-mapping",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/overview-of-fhir-destination-mapping.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/overview-of-fhir-destination-mapping",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/overview-of-samples.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/overview-of-samples",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/overview.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/overview",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/troubleshoot-errors-deployment.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/troubleshoot-errors-deployment",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/troubleshoot-errors-logs.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/troubleshoot-errors-logs",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/sentinel/datalake/sentinel-mcp-chatgpt-connector.md",
       "redirect_url": "/azure/sentinel/datalake/sentinel-mcp-chatgpt-claude-connector",

articles/active-directory-b2c/add-api-connector.md

@@ -25,7 +25,7 @@ ms.custom:
 
 [!INCLUDE [active-directory-b2c-choose-user-flow-or-custom-policy](../../includes/active-directory-b2c-choose-user-flow-or-custom-policy.md)]
 
-As a developer or IT administrator, you can use API connectors to integrate your sign-up user flows with REST APIs to customize the sign-up experience and integrate with external systems. At the end of this walkthrough, you'll be able to create an Azure AD B2C user flow that interacts with [REST API services](api-connectors-overview.md) to modify your sign-up experiences. 
+As a developer or IT administrator, you can use API connectors to integrate sign-up user flows with REST APIs, enabling customization of the sign-up experience and integration with external systems. At the end of this walkthrough, you'll be able to create an Azure AD B2C user flow that interacts with [REST API services](api-connectors-overview.md) to modify your sign-up experiences. 
 
 ::: zone pivot="b2c-user-flow"
 You can create an API endpoint using one of our [samples](api-connector-samples.md#api-connector-rest-api-samples).
@@ -515,7 +515,7 @@ Add the validation technical profile reference to the sign-up technical profile,
             <OutputClaim ClaimTypeReferenceId="reenterPassword" Required="true"/>
             <OutputClaim ClaimTypeReferenceId="displayName"/>
             <OutputClaim ClaimTypeReferenceId="givenName"/>
-            <OutputClaim ClaimTypeReferenceId="surName"/>
+            <OutputClaim ClaimTypeReferenceId="surname"/>
             <!-- Required to present the text box to collect the data from the user -->
             <OutputClaim ClaimTypeReferenceId="loyaltyId"/>
             <!-- Required to pass the promoCode returned from "REST-ValidateProfile" 

articles/api-center/TOC.yml

@@ -63,7 +63,7 @@
     - name: Agents
       items:
       - name: Overview
-        href: agent-to-agent-overview.md
+        href: agent-to-agent-overview.md 
       - name: Register and manage agents 
         href: register-manage-agents.md
     - name: MCP servers
@@ -100,6 +100,8 @@
     href: self-host-api-center-portal.md
   - name: Discover and consume APIs - VS Code extension
     href: discover-apis-vscode-extension.md
+  - name: Enable plugin marketplace
+    href: enable-api-center-plugin-marketplace.md
 - name: API center management and operations
   items:
   - name: Reliability

articles/api-center/enable-api-center-plugin-marketplace.md

@@ -0,0 +1,113 @@
+---
+title: Enable API Center Plugin Marketplace
+description: Enable a plugin marketplace endpoint (preview) for your Azure API center. Developers can configure it in GitHub Copilot or Claude Code to discover and install plugins from your inventory.
+
+ms.service: azure-api-center
+ms.topic: how-to
+ms.date: 04/15/2026
+ 
+ms.custom: 
+# Customer intent: As an API program manager, I want to create a plugin marketplace from my API center so AI developers can find and install plugins from my inventory.
+---
+
+# Enable discovery of API center plugins from a plugin marketplace (preview)
+
+
+This article shows how to enable a plugin marketplace endpoint in [Azure API Center](overview.md). The plugin marketplace endpoint uses the API Center data plane API to catalog the AI plugins such as MCP servers and skills available in the API center inventory. 
+
+After you enable the plugin marketplace, developers can add it to their GitHub Copilot CLI or Claude Code development environment to discover and install plugins from your API center.
+
+## Prerequisites
+
+- An API center in your Azure subscription. If you don't have one, see [Quickstart: Create your API center](set-up-api-center.md).
+
+- One or more plugins registered in your API center inventory, such as [MCP servers](register-discover-mcp-server.md) or [skills](register-discover-skills.md).
+
+- The API center portal enabled and set up for your API center. For details, see [Set up and customize your API Center portal](set-up-api-center-portal.md). The access method you choose for the portal determines how developers will authenticate when they access the plugin marketplace. 
+
+- [GitHub Copilot CLI](https://github.com/github/copilot-cli) or [Claude Code](https://www.anthropic.com/claude) installed in your development environment.
+
+
+## Confirm plugin marketplace endpoint is enabled for your API center
+
+After setting up the API Center portal, confirm that the plugin marketplace endpoint is enabled for your API center by cloning it locally. 
+
+> [!NOTE]
+> After setting up the API center portal, it can take several minutes for the plugin marketplace endpoint to be available. 
+
+The marketplace endpoint is of the following form:
+
+```
+https://<service name>.data.<region>.azure-apicenter.ms/workspaces/default/plugins/marketplace.git
+```
+
+To clone it, use a command similar to the following in your terminal, replacing the service name and region with the values from your API center:
+
+```bash
+git clone https://myapicenter.data.eastus.azure-apicenter.ms/workspaces/default/plugins/marketplace.git
+```
+
+The `marketplace` folder of the cloned repository contains folders for marketplace configuration in Claude Code and GitHub Copilot CLI, and folders for each plugin in your API center inventory. For example:
+
+```
+marketplace/
+    .claude-plugin/
+    .github/
+    plugins/
+        plugin1/
+        plugin2/
+        ...
+```
+
+Each plugin folder contains JSON files with the plugin metadata and configuration.
+
+## Add plugin marketplace to GitHub Copilot CLI 
+
+Developers can add the plugin marketplace from your API center's marketplace endpoint to GitHub Copilot CLI by using the `plugin marketplace add` command. For example, add it in a GitHub Copilot CLI session with a command similar to the following. Replace the service name and region with the values from your API center:
+
+```bash
+/plugin marketplace add https://myapicenter.data.eastus.azure-apicenter.ms/workspaces/default/plugins/marketplace.git
+```
+
+Follow the prompts to add the plugin marketplace to your GitHub Copilot CLI. 
+
+After adding the marketplace, use the `/plugin marketplace browse` command to see the plugins from your API center inventory. 
+
+```bash
+/plugin marketplace browse myapicenter
+```
+
+Add a plugin from the marketplace to a GitHub Copilot CLI session with the `/plugin install` command. For example:
+
+```bash
+/plugin install plugin-name@myapicenter
+```
+
+For more information about installing plugins from the marketplace in GitHub Copilot CLI, see [GitHub Copilot CLI documentation](https://docs.github.com/copilot/how-tos/copilot-cli/customize-copilot/plugins-finding-installing).
+
+## Add plugin marketplace to Claude Code
+
+Developers can add the plugin marketplace from their API center's marketplace endpoint by using the `/plugin marketplace add` command. For example, add it in a Claude Code session with a command similar to the following command. Replace the service name and region with the values from your API center:
+
+```bash
+/plugin marketplace add https://myapicenter.data.eastus.azure-apicenter.ms/workspaces/default/plugins/marketplace.git
+```
+
+Follow the prompts to add the plugin marketplace.
+
+After you add the marketplace, use the `/plugin` command to see the plugins from your API center inventory. 
+
+Add a plugin from the marketplace to a Claude Code session with the `/plugin install` command. For example:
+
+```bash
+/plugin install plugin-name@myapicenter
+```
+
+For more information about installing plugins from the marketplace in Claude Code, see [Claude Code documentation](https://code.claude.com/docs/en/discover-plugins).
+
+## Related content
+
+* [Set up and customize your API Center portal](set-up-api-center-portal.md)
+* [Discover and consume APIs - VS Code extension](discover-apis-vscode-extension.md)
+
+

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