Skip to content

Commit 9d9e5d3

Browse files
author
gitName
committed
[APIC] Export to Copilot Studio
1 parent 53ad670 commit 9d9e5d3

File tree

2 files changed

+81
-0
lines changed

2 files changed

+81
-0
lines changed

articles/api-center/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -50,6 +50,8 @@
5050
href: design-api-github-copilot-azure.md
5151
- name: Register APIs - GitHub Actions
5252
href: register-apis-github-actions.md
53+
- name: Export API from API Center to Copilot Studio
54+
href: export-to-copilot-studio.yml
5355
- name: API governance
5456
items:
5557
- name: Use metadata for governance
Lines changed: 79 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,79 @@
1+
### YamlMime:HowTo
2+
3+
metadata:
4+
title: "Export API from API Center to Copilot Studio"
5+
description: "Learn how to export an API from your Azure API center to a connector in Microsoft Copilot Studio."
6+
author: dlepow
7+
ms.author: danlep
8+
ms.service: azure-api-management
9+
ms.topic: how-to
10+
ms.date: 04/22/2025
11+
ms.custom: template-how-to
12+
# appliesTo: <optional> leave commented out.
13+
# - item
14+
# - item
15+
# - item
16+
# - item
17+
18+
#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 re-use by citizen developers.
19+
title: |
20+
"Export API from API Center to Copilot Studio as a connector"
21+
22+
introduction: |
23+
You can export an API from your Azure API center to a connector in Microsoft Copilot Studio. This allows you to share the API with citizen developers who can use it in their applications. The exported connector is available for use in Microsoft Copilot Studio, where it can be used to create applications and workflows.
24+
25+
In this article, you create a custom connector using an OpenAPI definition in OpenAPI 2.0 format. Learn more about [creating a custom connector](/connectors/custom-connectors/define-openapi-definition) from an OpenAPI definition in the [Microsoft documentation](https://learn.microsoft.com/en-us/connectors/custom-connectors/define-openapi-connector).
26+
prerequisites:
27+
summary: |
28+
The following are prerequisites for this procedure.
29+
30+
dependencies:
31+
- An API center instance. You can [create one](set-up-api-center.md) in the Azure portal.
32+
- An API registered in the API center inventory. The API must have a version associated with a [deployment](configure-environments-depoloyments.md) and an API definition in OpenAPI 2.0 format
33+
- A Power Apps [environment](/power-apps/powerapps-overview#power-apps-for-admins) to export the API to.
34+
35+
36+
procedureSection:
37+
- title: |
38+
"Export API from API Center to Copilot Studio"
39+
summary: |
40+
Follow these steps to export an API from your Azure API center as a custom connector in Microsoft Copilot Studio.
41+
42+
steps:
43+
- |
44+
Navigate to your API center in the Azure portal.
45+
- |
46+
In the left menu, under **Assets**, select **Copilot Studio (preview)**.
47+
- |
48+
Select **Create a connector**. The **Create a connector** pane opens.
49+
- |
50+
Select a **Power Platform environment** to publish the API to.
51+
- |
52+
Enter a **Connector display name**.
53+
- |
54+
Select the **API**, **API version**, and **Deployment** to connect to the Power Platform.
55+
- |
56+
Enter a **Host** URL. This is the URL that the connector will use to connect to the API.
57+
- |
58+
Select the **API definition** to use for the connector.
59+
- |
60+
Select the **Security requirement** type to use for the connector.
61+
- |
62+
Select **Create**.
63+
The connector is now available for use in Microsoft Copilot Studio.
64+
65+
- title: |
66+
"[verb] * [noun]"
67+
summary: |
68+
[Introduce the procedure.]
69+
steps:
70+
- |
71+
Procedure step
72+
- |
73+
Procedure step
74+
- |
75+
Procedure step
76+
77+
nextStep:
78+
text: "[Next step text]"
79+
url: link.md

0 commit comments

Comments
 (0)