Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into us508796-03

Author: TimShererWithAquent

.openpublishing.redirection.json

@@ -31,7 +31,7 @@ With this integration, organizations can extend their Azure AD B2C capabilities
 
 To get started, you'll need:
 
-- An Azure subscription. If you don't have one, get a [free account](https://azure.microsoft.com/free).
+- An Azure subscription. If you don't have one, get a [free account](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn).
 
 - An [Azure AD B2C tenant](tutorial-create-tenant.md) that is linked to your Azure subscription.
 

articles/active-directory-b2c/partner-deduce.md

@@ -37,7 +37,7 @@ To get started, you need:
 * A Relying Party account with eID-Me
   * Go to bluink.ca to [learn more](https://bluink.ca/eid-me/solutions/id-verification#contact-form) and request a demo
 * An Azure subscription
-  * If you don't have one, get an [Azure free account](https://azure.microsoft.com/free)
+  * If you don't have one, get an [Azure free account](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn)
 * An Azure AD B2C tenant linked to the Azure subscription
   * See, [Tutorial: Create an Azure AD B2C tenant](tutorial-create-tenant.md)
 * A trial or production version of the eID-Me Digital ID App

articles/active-directory-b2c/partner-eid-me.md

@@ -58,6 +58,12 @@
     href: export-to-copilot-studio.yml
   - name: Track API dependencies
     href: track-resource-dependencies.md
+- name: Agent-to-Agent
+  items:
+  - name: Overview
+    href: agent-to-agent-overview.md
+  - name: Register and manage agents 
+    href: register-manage-agents.md
 - name: MCP servers
   items:
   - name: Register and discover MCP servers

articles/api-center/TOC.yml

@@ -0,0 +1,48 @@
+---
+title: Agent registry in Azure API Center
+description: "Overview of the agent registry for discovering, registering, and managing A2A agents in API Center."
+author: ProfessorKendrick
+ms.author: kkendrick
+ms.service: azure-api-center
+ms.topic: overview
+ms.date: 11/03/2025
+ms.update-cycle: 180-days
+ms.collection: ce-skilling-ai-copilot
+
+#customer intent: As an API platform owner, I want to understand how to use the agent registry to discover, register, and manage AI agents.
+
+---
+
+# Agent registry in Azure API Center
+
+Azure API Center provides a centralized platform for discovering, registering, and managing AI agents. It supports first-party and third-party agents, integrates with API Management for private endpoints, and stores customizable metadata to improve discoverability and governance.
+
+## Key features
+
+**Centralized Discovery and Management**: A single location to register and manage both first-party and third-party AI agents, including those exposed in API Management or hosted externally.
+
+**Enhanced Discoverability**: Enables developers and other stakeholders to easily find and access approved AI agents through a curated catalog, either via the built-in API Center portal or a custom UI.
+
+**Governance and Security**: Addresses shadow IT and uncontrolled AI tool adoption by providing a governed channel for accessing AI agents, improving security and compliance.
+
+**Integration with API Management**: AI agents can be placed behind an API Management gateway for private endpoints, enhanced security, and controlled access.
+
+**Customizable Metadata**: Organizations can define and store relevant metadata for each registered AI agent, facilitating filtering and searching.
+
+## Register an AI agent
+
+You can register AI agents in API Center similar to how you register other APIs. During registration, specify the API type as **A2A** and fill in details for **Agent Card**, **Agent Skills**, and **Agent Capabilities**.  
+
+For detailed steps, see [Register agent](register-manage-agents.md#register-agent).
+
+## Manage your AI agent
+
+After registering an A2A agent, you can update its metadata, add skills, configure capabilities, and manage provider information. Skills define the specific actions your agent can perform, making it discoverable and invokable by other agents.
+
+For step-by-step instructions, see [Manage agents in Azure API Center](register-manage-agents.md).
+
+## View dependency maps for A2A agents (preview)
+
+API platform administrators can now create relationships feature using the dependency tracker feature. This capability allows API Center to identify the right agent to call and enable communication across agents in an enterprise. 
+
+For detailed steps, see [Track API resource dependencies in your API center](track-resource-dependencies.md).

articles/api-center/agent-to-agent-overview.md

@@ -7,6 +7,7 @@ ms.topic: concept-article
 ms.date: 09/08/2025
 ms.author: danlep 
 ms.collection: ce-skilling-ai-copilot
+ms.update-cycle: 180-days
 # Customer intent: As an API program manager, I want to register and discover  MCP servers as APIs in my API Center inventory.
 ms.custom:
   - build-2025

articles/api-center/media/register-manage-agents/edit-agent.png

@@ -0,0 +1,128 @@
+---
+title: Register and Manage Agents in Azure API Center
+description: "Learn how to update agent metadata, add skills, configure capabilities, and manage provider information for A2A agents."
+author: ProfessorKendrick
+ms.author: kkendrick
+ms.service: azure-api-center
+ms.topic: how-to
+ms.date: 11/11/2025
+ms.update-cycle: 180-days
+ms.collection: ce-skilling-ai-copilot
+---
+
+# Register and manage agents in Azure API Center
+
+This article shows you how to register A2A agents in API Center, and how to update and manage them after registration. You can add skills, configure capabilities, and update provider information.
+
+## Prerequisites
+
+- An Azure API Center instance 
+- An A2A agent described by an agent card
+- Appropriate permissions to edit APIs in your API Center
+
+## Register agent
+
+Enter required values from the agent's agent card. Optionally add skills and other metadata that define the capabilities and actions your A2A agent can perform.
+
+> [!TIP]
+> For detailed skill schema information, see the [Agent2Agent (A2A) Protocol Official Specification](https://a2a-protocol.org/latest/specification/).
+
+1. Sign in to the [Azure portal](https://portal.azure.com), then navigate to your API center.
+
+1. In the sidebar menu, under **Assets**, select **APIs** > **+ Register an API**.
+
+1. In the **Register an API** page, fill in the [standard properties](tutorials/register-apis.md) to register an API and choose **A2A** as the agent type.
+
+    - The form updates to display other fields specific to the **A2A** API type.
+
+1. In the **Agent Card** section, enter the following details:
+
+    |Field                |Description                                                |
+    |---------------------|-----------------------------------------------------------|
+    |Protocol Version     |The version of the A2A protocol this agent supports.       |
+    |Agent URL            |The preferred endpoint URL for interacting with the agent. |
+    |Preferred Transport  |The transport protocol for the preferred endpoint.         |
+    |Agent Version        |The agent's own version number.                            |
+
+1. Locate the **Agent Skills** section.
+
+1. Select **+ Add**.
+
+1. On the **Agent Skills** page, define the skill by providing information for the required fields.
+
+1. Select **Add** to add the skill.
+
+1. In the **Agent Provider** section, enter the following details:
+
+    |Field                 |Description                                                              |
+    |----------------------|-------------------------------------------------------------------------|
+    |Organization name     |The name of the agent provider's organization                            |
+    |Organization URL      |A URL for the agent provider's website or relevant documentation         |
+
+1. Enable or disable the **Agent Capabilities** as needed:
+
+    |Field                    |Description                                                                             |
+    |-------------------------|----------------------------------------------------------------------------------------|
+    |Streaming Support        |Indicates if the agent supports Server-Sent Events (SSE) for streaming responses        |
+    |Push Notifications       |Indicates if the agent supports sending push notifications for asynchronous task updates|
+    |State Transition History | Indicates if the agent provides a history of state transitions for a task              |
+
+1. Select **Create** to register the API.
+
+## Update agent
+
+1. In the [Azure portal](https://azure.microsoft.com), go to your API center.
+1. In the sidebar menu, under **Assets**, select **APIs**.
+1. From the table, select your A2A agent by selecting the agent name in the **Title** column.
+1. Select the **Edit** button to open the **Edit** page in the working pane.
+
+    :::image type="content" source="media/register-manage-agents/edit-agent.png" alt-text="Screenshot of the AI agent overview in Azure portal with the edit button highlighted.":::
+
+### Add skills to your agent
+
+Skills define the capabilities and actions your A2A agent can perform.
+
+> [!TIP]
+> For detailed skill schema information, see the [Agent2Agent (A2A) Protocol Official Specification](https://a2a-protocol.org/latest/specification/).
+
+1. On the **Edit** page, locate the **Agent Skills** section.
+1. Select **+ Add**.
+1. On the **Agent Skills** page, define the skill by providing information for the required fields.
+1. Select **Add** to add the skill.
+
+### Add provider information
+
+Provider information helps other teams identify who maintains the agent.
+
+1. On the agent **Edit** page, locate the **Agent Provider** section.
+1. Enter the following details:
+
+    |Field                 |Description                                                              |
+    |----------------------|-------------------------------------------------------------------------|
+    |Organization name     |The name of the agent provider's organization                            |
+    |Organization URL      |A URL for the agent provider's website or relevant documentation         |
+
+1. Select **Save**.
+
+### Configure agent capabilities
+
+Agent capabilities describe what features your A2A agent supports.
+
+1. On the **Edit** page, locate the **Agent Capabilities** section.
+1. Enable or disable the following capabilities as needed:
+
+    |Field                    |Description                                                                             |
+    |-------------------------|----------------------------------------------------------------------------------------|
+    |Streaming Support        |Indicates if the agent supports Server-Sent Events (SSE) for streaming responses        |
+    |Push Notifications       |Indicates if the agent supports sending push notifications for asynchronous task updates|
+    |State Transition History | Indicates if the agent provides a history of state transitions for a task              |
+
+1. Select **Save**.
+
+## Limitations
+
+Agent-to-Agent APIs in API Management don't synchronize with API Center.
+
+## Related content
+
+[Agent registry in Azure API Center](agent-to-agent-overview.md)

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

@@ -248,7 +248,7 @@
     href: genai-gateway-capabilities.md
   - name: Manage LLM APIs
     items:
-    - name: Import Azure AI Foundry API
+    - name: Import Microsoft Foundry API
       href: azure-ai-foundry-api.md
     - name: Import Azure OpenAI API
       href: azure-openai-api-from-specification.md
@@ -714,6 +714,8 @@
       href: breaking-changes/identity-provider-adal-retirement-sep-2025.md
     - name: CAPTCHA endpoint update (September 2025)
       href: breaking-changes/captcha-endpoint-change-sep-2025.md
+    - name: Trusted service connectivity retirement (March 2026)
+      href: breaking-changes/trusted-service-connectivity-retirement-march-2026.md
     - name: Built-in analytics dashboard retirement (March 2027)
       href: breaking-changes/analytics-dashboard-retirement-march-2027.md
   - name: Regional availability