PR review

Author: gitName

.openpublishing.redirection.json

@@ -6875,9 +6875,14 @@
       "redirect_document_id": false
     },
     {
-      "source_path": "articles/storage/files/storage-files-enable-soft-delete.md",
+         "source_path": "articles/storage/files/storage-files-enable-soft-delete.md",
       "redirect_url": "/azure/storage/files/storage-files-prevent-file-share-deletion",
       "redirect_document_id": false
+     },
+     {
+      "source_path": "articles/defender-for-iot/organizations/release-notes-archive.md",
+      "redirect_url": "/azure/defender-for-iot/organizations/release-notes-ot-monitoring-sensor-archive",
+       "redirect_document_id": false
     }
   ]
 }

articles/api-center/TOC.yml

@@ -52,6 +52,8 @@
         href: register-apis-github-actions.md
       - name: Register and discover MCP servers
         href: register-discover-mcp-server.md
+      - name: Export API from API Center to Copilot Studio
+        href: export-to-copilot-studio.yml
 - name: API governance
   items:
       - name: Use metadata for governance

articles/api-center/export-to-copilot-studio.yml

@@ -0,0 +1,79 @@
+### YamlMime:HowTo
+
+metadata:
+  title: Export API from API Center as Copilot Studio connector
+  description: Learn how to export an API definition from your Azure API center as a custom connector in Microsoft Copilot Studio.
+  author: dlepow
+  ms.author: danlep
+  ms.service: azure-api-management
+  ms.topic: how-to 
+  ms.date: 04/28/2025
+  ms.custom: template-how-to
+
+  #customer intent: As an API program manager, I want to export an API from my API center inventory as a connector in Microsoft Copilot Studio for use in agents.
+title: |
+  Export API definition from API Center to Copilot Studio as a connector
+
+introduction: |
+  You can export an API definition from your Azure API center as a [connector in Microsoft Copilot Studio](/connectors/overview) (preview). Copilot Studio is a graphical, low-code tool for building agents and agent flows and is part of the Microsoft Power Platform family.
+  
+  In Microsoft Copilot Studio, citizen developers can use the exported connector as a custom connector to [extend the capabilities of AI agents](/microsoft-copilot-studio/copilot-connectors-in-copilot-studio).
+
+  In this article, you create a custom connector from an OpenAPI definition associated with an API in an API center.  
+
+prerequisites:
+  summary: |
+
+  dependencies:
+    - An API center instance. You can [create one](set-up-api-center.md) in the Azure portal.
+    - An API registered in the API center inventory. The API must have a version associated with a [deployment](configure-environments-deployments.md), and it must have an API definition in OpenAPI 2.0 format.
+    - A Power Platform [environment](/power-apps/powerapps-overview#power-apps-for-admins).
+    - A Microsoft Copilot Studio [license](/microsoft-copilot-studio/requirements-licensing-subscriptions).
+
+procedureSection:
+  - title: | 
+        Export API definition from API Center
+    summary: |
+      Follow these steps to export an API definition from your Azure API center as a custom connector in Microsoft Copilot Studio. 
+       
+    steps:
+      - |
+        Navigate to your API center in the Azure portal.
+      - |
+        In the left menu, select **Copilot Studio (preview)**.
+      - |
+        Select **Create a connector**. The **Create a connector** window opens.
+      - |
+        Select a **Power Platform environment** to export the API to. 
+      - |
+        Enter a **Connector display name**.
+      - |
+        Select the **API**, **API version**, and **Deployment** for the connector. The **Host** URL is populated with the deployment's runtime URL.
+      - |
+        Select the **API definition** to use for the connector.
+      - |
+        Optionally, if you configured [API access settings](https://aka.ms/apicenter/docs/access) for the API version in your API center, select an available **Security requirement** type to use for the connector.
+      - |
+        Select **Create**. 
+
+        :::image type="content" source="media/export-to-copilot-studio/copilot-studio-menu-item.png" alt-text="Screenshot of creating a Copilot Studio connector in the portal.":::
+
+        
+        The connector is now available for use in Microsoft Copilot Studio.
+    
+        After creating the connector:
+        
+        - You can [test the connector](/connectors/custom-connectors/define-openapi-definition#test-the-connector) in Power Automate or Power Apps. 
+        
+        - After testing, use the connector in [Microsoft Copilot Studio](/microsoft-copilot-studio/) to create applications and workflows.
+
+relatedContent:
+  
+    - text: Create a custom connector from an OpenAPI definition
+      url: /connectors/custom-connectors/define-openapi-definition
+
+    - text: Learn more about building AI-driven agents with Microsoft Copilot Studio
+      url: /microsoft-copilot-studio/nlu-gpt-overview
+
+    - text: Get started with Microsoft Copilot Studio 
+      url: /training/modules/power-virtual-agents-bots

articles/api-center/media/export-to-copilot-studio/copilot-studio-menu-item.png

@@ -47,7 +47,7 @@ MCP utilizes a client-host-server architecture built on [JSON-RPC 2.0 for messag
 
 ## MCP servers in your API inventory
 
-The following sections describe how to inventory and discover an MCP server in your API Center. You can register remote or local MCP servers.
+The following sections describe how to inventory and discover a remote MCP server in your API Center. 
 
 ### MCP API type
 
@@ -88,7 +88,7 @@ You can use the following lightweight OpenAPI 3.0 API definition for your MCP se
 
 ###  Discover MCP servers using API Center portal
 
-Set up the [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. Users can browse and filter MCP servers in the inventory and view details such as a the URL endpoint of the MCP server, if available in the MCP server's API definition. 
+Set up the [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. Users can browse and filter MCP servers in the inventory and view details such as the URL endpoint of the MCP server, if available in the MCP server's API definition. 
 
 :::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-architecture.png

@@ -6,7 +6,7 @@ author: dlepow
 
 ms.service: azure-api-management
 ms.topic: tutorial
-ms.date: 03/29/2024
+ms.date: 04/28/2025
 ms.author: danlep
 ms.custom: engagement-fy23
 ---
@@ -28,7 +28,7 @@ In this tutorial, you learn how to:
 
 For more information about developer portal features and options, see [Azure API Management developer portal overview](developer-portal-overview.md).
 
-:::image type="content" source="media/api-management-howto-developer-portal-customize/cover.png" alt-text="Screenshot of the API Management developer portal - administrator mode." border="false":::
+:::image type="content" source="media/api-management-howto-developer-portal-customize/cover.png" alt-text="Screenshot of the API Management developer portal - administrator mode." :::
 
 ## Prerequisites
 
@@ -49,6 +49,8 @@ Follow these steps to access the managed version of the developer portal.
     It might take a few minutes to enable the developer portal.
 1. In the left menu, under **Developer portal**, select **Portal overview**. Then select the **Developer portal** button in the top navigation bar. A new browser tab with an administrative version of the portal will open.
 
+[!INCLUDE [developer-portal-editor-refresh](../../includes/developer-portal-editor-refresh.md)] 
+
 ## Understand the portal's administrative interface
 
 [!INCLUDE [api-management-developer-portal-editor](../../includes/api-management-developer-portal-editor.md)]
@@ -70,7 +72,7 @@ You'll want to use your own images and other media content in the developer port
 
 A placeholder logo is provided in the top left corner of the navigation bar. You can replace it with your own logo to match your organization's branding.
 
-1. In the developer portal, select the default **Contoso** logo in the top left of the navigation bar. 
+1. In the developer portal, select the default logo in the top left of the navigation bar. 
 1. Select **Edit**. 
 1. In the **Picture** pop-up, under **Main**, select **Source**.
 1. In the **Media** pop-up, select one of the following:

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

@@ -6,7 +6,7 @@ author: dlepow
 
 ms.service: azure-api-management
 ms.topic: concept-article
-ms.date: 11/20/2024
+ms.date: 04/29/2025
 ms.author: danlep
 ms.custom: references_regions
 ---
@@ -47,10 +47,11 @@ Information in the following table is updated regularly. Capacity availability i
 | Switzerland North | ✅ |✅ |  | |
 | UK South | ✅  | ✅ | ✅ | ✅ |
 | UK West | ✅  | ✅ | | |
-| West Europe  | ✅ | ✅ | |  |
+| West Europe  | ✅ | ✅ | | ✅<sup>1</sup> |
 | West US | ✅ | ✅ |  | ✅ |
 | West US 2 | ✅ | ✅ |  | |
 
+<sup>1</sup> Request access to this region by emailing `[email protected]` 
 
 ## Related content
 

articles/api-management/api-management-howto-developer-portal-customize.md

@@ -7,7 +7,7 @@ author: dlepow
 
 ms.service: azure-api-management
 ms.topic: concept-article
-ms.date: 03/29/2024
+ms.date: 04/28/2025
 ms.author: danlep 
 ---
 
@@ -76,21 +76,18 @@ The developer portal's administrative interface provides a visual editor for pub
 
 [!INCLUDE [api-management-developer-portal-add](../../includes/api-management-developer-portal-add.md)]
 
-[!INCLUDE [api-management-developer-portal-wordpress](../../includes/api-management-developer-portal-wordpress.md)]
+### Pages and layouts
 
+The pre-provisioned content in the developer portal showcases pages with commonly used features. Find them on the **Pages** panel. You can modify the content of these pages or add new ones to suit your needs.
 
-### Layouts and pages
-
-Layouts define how pages are displayed. For example, in the default content, there are two layouts: one applies to the home page, and the other to all remaining pages. You can modify these layouts and add more layouts to suit your needs.
+Select **Layouts** on the **Pages** panel to define how pages are displayed. The developer portal comes with a default layout that's applied to the pages. You can modify this layout and add more layouts to suit your needs.
 
 A layout gets applied to a page by matching its URL template to the page's URL. For example, a layout with a URL template of `/wiki/*` is applied to every page with the `/wiki/` segment in the URL: `/wiki/getting-started`, `/wiki/styles`, etc.
 
 In the following image, content belonging to the layout is outlined in blue, while the page-specific content is outlined in red. 
 
 :::image type="content" source="media/developer-portal-overview/pages-layouts.png" alt-text="Screenshot of layout content in the developer portal." :::
 
-The pre-provisioned content in the developer portal showcases pages with commonly used features. You can modify the content of these pages or add new ones to suit your needs.
-
 > [!NOTE]
 > Due to integration considerations, the following pages can't be removed or moved under a different URL: `/404`, `/500`, `/captcha`, `/change-password`, `/config.json`, `/confirm/invitation`, `/confirm-v2/identities/basic/signup`, `/confirm-v2/password`, `/internal-status-0123456789abcdef`, `/publish`, `/signin`, `/signin-sso`, `/signup`.
 
@@ -248,7 +245,8 @@ To restore a previous portal revision:
 If you want to discard all changes you've made to the developer portal, you can reset the website to its starting state. Resetting the portal deletes any changes you've made to the developer portal pages, layouts, customizations, and uploaded media.
 
 > [!NOTE]
-> Resetting the developer portal doesn't delete the published version of the developer portal.
+> * Resetting the developer portal doesn't delete the published version of the developer portal.
+> * Resetting the portal could update the portal to a newer version of the developer portal codebase with updated components. The placeholder content that appears might also be changed. Developer portal features and customization options remain consistent. 
 
 To reset the developer portal: