Merge pull request #314800 from MicrosoftDocs/main

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

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

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/azure-resource-manager/management/tag-support.md

@@ -2257,7 +2257,6 @@ To get the same data as a file of comma-separated values, download [tag-support.
 > | services / privateEndpointConnectionProxies | No | No |
 > | services / privateEndpointConnections | No | No |
 > | services / privateLinkResources | No | No |
-> | validateMedtechMappings | No | No |
 > | workspaces | Yes | Yes |
 > | workspaces / analyticsconnectors | Yes | Yes |
 > | workspaces / dicomservices | Yes | Yes |

articles/azure-resource-manager/templates/deployment-complete-mode-deletion.md

@@ -1665,7 +1665,6 @@ The resources are listed by resource provider namespace. To match a resource pro
 > | services / privateEndpointConnectionProxies | No |
 > | services / privateEndpointConnections | No |
 > | services / privateLinkResources | No |
-> | validateMedtechMappings | No |
 > | workspaces | Yes |
 > | workspaces / analyticsconnectors | Yes |
 > | workspaces / dicomservices | Yes |

articles/healthcare-apis/breadcrumb/toc.yml

@@ -13,9 +13,6 @@ items:
         - name: DICOM service
           tocHref: /azure/healthcare-apis/dicom/
           topicHref: /azure/healthcare-apis/dicom/index
-        - name: MedTech service
-          tocHref: /azure/healthcare-apis/iot/
-          topicHref: /azure/healthcare-apis/iot/index
         - name: De-identification service
           tocHref: /azure/healthcare-apis/deidentification/
           topicHref: /azure/healthcare-apis/deidentification/index

articles/healthcare-apis/includes/iot-deprecation.md

@@ -93,25 +93,6 @@ conceptualContent:
               itemType: how-to-guide
               text: Use image data for digital pathology  
 
-        # Card
-        - title: Device data
-          links:
-            - url: ./iot/overview.md
-              itemType: overview
-              text: MedTech service overview
-            - url: ./iot/deploy-choose-method.md          
-              itemType: how-to-guide
-              text: Choose a deployment method
-            - url: ./iot/how-to-use-monitoring-and-health-checks-tabs.md
-              itemType: how-to-guide
-              text: Monitor service health in Azure portal 
-            - url: ./iot/how-to-use-mapping-debugger.md
-              itemType: how-to-guide
-              text: Troubleshoot with the Mapping debugger 
-            - url: ./iot/troubleshoot-errors-logs.md
-              itemType: how-to-guide
-              text: Troubleshoot service log errors   
-
         # Card
         - title: Automate and optimize data workflows
           links:

articles/healthcare-apis/index.yml

@@ -24,7 +24,7 @@ Refer to the table for details about resolution dates or possible workarounds.
 | Due to an issue with the Event Grid service, the FHIR instance was unable to publish events, which primarily affected its ability to send requests successfully.|May 28, 2025 2:52 PM PST|--|May 29, 2025 8:28 AM PST|
 | Customers are unable to select storage account in the FHIR instance export configuration. The issue is caused by throttling due to a large number of resource groups and storage accounts, leading to errors like "Storage account doesn't exist" on the Export blade. | May 15, 2025 2:05 pm PST | PowerShell commands to configure the storage account for export manually:<br><br>Run this command to install the Az Module: <br>```Install-Module -Name Az```<br><br> If Az module is already installed:<br>```Update-Module -Name Az```<br><br> Connect to Azure Account:<br>```Connect-AzAccount```<br><br>Initialize the variable resourceGroupName, fhirServiceName, and storageAccountName:<br>```$resourceGroupName = "YOUR_RESOURCEGROUP_NAME"```<br>```$fhirServiceName = "YOUR_FHIRSERVICE_NAME"```<br>```$exportConfig = @{ "storageAccountName" = "YOUR_STORAGEACCOUNT_NAME" }```<br><br>Run this command to set the storage account for export:<br>```Set-AzResource -ResourceGroupName $resourceGroupName -ResourceType "Microsoft.HealthcareApis/services" -ResourceName $fhirServiceName -ApiVersion "2021-11-01" -Properties @{ "exportConfiguration" = $exportConfig }```<br><br>Running this command confirms  if the setting was successful: <br>```Get-AzResource -ResourceGroupName $resourceGroupName -ResourceType "Microsoft.HealthcareApis/services" -ResourceName $fhirServiceName \| Select-Object -ExpandProperty Properties \| Select-Object -ExpandProperty exportConfiguration```| -- |
 | Patient-everything operation returns a 500 error when run using a SMART patient fhirUser token. |  April 9, 2025 | A fix is being released in the upcoming FHIR release. | |
-|Customers can't access FHIR, DICOM, or Medtech through the portal. | October 31, 2024 1:00 pm PST | ARM calls are still operational, and there's no disruption to existing services. | November 1, 2024  |
+|Customers can't access FHIR or DICOM through the portal. | October 31, 2024 1:00 pm PST | ARM calls are still operational, and there's no disruption to existing services. | November 1, 2024  |
 |For FHIR instances created after August 19, 2024, diagnostic logs aren't available in log analytics workspace. |September 19, 2024 9:00 am PST| -- | October 17, 2024  |
 |For FHIR instances created after August 19, 2024, in metrics blade - Total requests, Total latency, and Total errors metrics are not being populated. |September 19, 2024 9:00 am PST| -- | October 28, 2024 |
 |For FHIR instances created after August 19, 2024, changes in private link configuration at the workspace level causes FHIR service to be stuck in 'Updating' state. |September 24, 2024 9:00 am PST| Accounts deployed prior to September 27, 2024 and facing this issue can follow the steps: <br> 1. Remove private endpoint from the Azure Health Data Services workspace having this issue. On Azure blade, go to Workspace and then click on Networking blade. In networking blade, select existing private link connection and click on 'Remove' <br> 2. Create new private connection to link to the workspace.| September 27, 2024 |