Merge branch 'main' into UUF-march-2026

Author: ggailey777

.openpublishing.redirection.json

@@ -1,5 +1,9 @@
 {
   "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",

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-skills/linked-skills.png

@@ -50,7 +50,7 @@ Information in the following table is updated regularly. Capacity availability i
 | South Africa North | ✅ | ✅ | |  |
 | South Central US | ✅ | ✅ |  |  |
 | South India | ✅ | ✅ |  |  |
-| Sweden Central | ✅ | ✅ | | |
+| Sweden Central | ✅ | ✅ | ✅ | |
 | South India | ✅ | ✅ |  |  |
 | Switzerland North | ✅ |✅ |  | |
 | UAE North | ✅ | ✅ | |  |
@@ -59,6 +59,7 @@ Information in the following table is updated regularly. Capacity availability i
 | West Europe  | ✅ | ✅ | | ✅ |
 | West US | ✅ | ✅ |  | ✅ |
 | West US 2 | ✅ | ✅ |  | |
+| West US 3 | | ✅ |  | |
 
 ¹ New instance creation temporarily unavailable. See the capacity limitation note above.
 

articles/api-management/api-management-region-availability.md

@@ -34,7 +34,9 @@ To configure any of the supported providers in API Management, first configure a
 
 * Depending on the provider and your scenario, you might need to retrieve other settings, like authorization endpoint URLs or scopes.
 
-* The provider's authorization endpoints must be reachable over the internet from your API Management instance. If your API Management instance is secured in a virtual network, configure network or firewall rules to allow access to the provider's endpoints.
+* The provider's authorization endpoints must be reachable over the internet from your API Management instance. If your API Management instance is secured in a virtual network, configure network or firewall rules to allow access to the provider's endpoints. 
+
+    Additionally, requests for tokens need to go out of the customer's network to the credential manager endpoint, which remains in a Microsoft network. To reach the credential manager endpoint, allow outbound access from the virtual network to the **AzureConnections** service tag on port 443.
 
 ## Microsoft Entra provider
 

articles/api-management/credentials-configure-common-providers.md

@@ -4,7 +4,7 @@ description: Learn about using credential manager in Azure API Management to cre
 author: dlepow
 ms.service: azure-api-management
 ms.topic: concept-article
-ms.date: 09/25/2025
+ms.date: 04/10/2026
 ms.author: danlep
 ms.custom: references_regions
 ---
@@ -129,9 +129,9 @@ At runtime, API Management can't fetch new tokens, and an error occurs.
 
 * If the connection is of type *client credentials*, the client secret needs to be updated on the connection level.
 
-### Is this feature supported using API Management running inside a VNet?
+### Is this feature supported using API Management running inside a virtual network?
 
-Yes, as long as outbound connectivity on port 443 is enabled to the **AzureConnectors** service tag. For more information, see [Virtual network configuration reference](virtual-network-reference.md#required-ports).
+Requests for tokens need to go out of the customer's network to the credential manager endpoint, which remains in a Microsoft network. If the API Management instance is running inside a virtual network, credential manager is supported as long as outbound connectivity on port 443 is enabled to the **AzureConnectors** service tag. For more information, see [Virtual network configuration reference](virtual-network-reference.md#required-ports).
 
 ### What happens when a credential provider is deleted?
 

articles/api-management/credentials-overview.md

@@ -233,6 +233,7 @@ More information:
 * [Enable AI gateway in Microsoft Foundry](/azure/ai-foundry/configuration/enable-ai-api-management-gateway-portal)
 * [Register custom agents in Foundry](/azure/ai-foundry/control-plane/register-custom-agent)
 * [Govern tools with AI gateway](/azure/ai-foundry/agents/how-to/tools/governance)
+* [Connect an AI gateway to Foundry Agent Service](/azure/foundry/agents/how-to/ai-gateway)
 
 ## Early access to AI gateway features    
 

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

@@ -6,7 +6,7 @@ author: dlepow
 
 ms.service: azure-api-management
 ms.topic: reference
-ms.date: 06/17/2025
+ms.date: 04/10/2026
 ms.author: danlep
 ms.custom: references_regions
 ---
@@ -45,7 +45,7 @@ When an API Management service instance is hosted in a VNet, the ports in the fo
 | Outbound | VirtualNetwork | * | Internet | 80                  |  TCP | Allow  | **Validation and management of Microsoft-managed and customer-managed certificates**      | External & Internal  |
 | Outbound | VirtualNetwork | * | Storage | 443                  |  TCP                | Allow             | **Dependency on Azure Storage**                             | External & Internal  |
 | Outbound | VirtualNetwork |  * | AzureActiveDirectory | 443                             | TCP                | Allow | [Microsoft Entra ID, Microsoft Graph,](api-management-howto-aad.md) and Azure Key Vault dependency (optional)              | External & Internal  |
-| Outbound | VirtualNetwork | * | AzureConnectors | 443                  |  TCP                | Allow | [managed connections](credentials-overview.md) dependency (optional)              | External & Internal  |
+| Outbound | VirtualNetwork | * | AzureConnectors | 443                  |  TCP                | Allow | [API Management credential manager endpoint](credentials-overview.md) dependency (optional)              | External & Internal  |
 | Outbound | VirtualNetwork | * | Sql | 1433                     |  TCP                | Allow          | **Access to Azure SQL endpoints**                           | External & Internal  |
 | Outbound | VirtualNetwork | * | AzureKeyVault | 443                     |  TCP                | Allow                | **Access to Azure Key Vault**                         | External & Internal  |
 | Outbound | VirtualNetwork | * | EventHub | 5671, 5672, 443          |  TCP                | Allow            | Dependency for [Log to Azure Event Hubs policy](api-management-howto-log-event-hubs.md) and [Azure Monitor](api-management-howto-use-azure-monitor.md) (optional) | External & Internal  |