Skip to content

Commit 0c18efb

Browse files
author
gitName
committed
rough draft
1 parent 9d9e5d3 commit 0c18efb

File tree

2 files changed

+23
-25
lines changed

2 files changed

+23
-25
lines changed
Lines changed: 23 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
### YamlMime:HowTo
22

33
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."
4+
title: Export API from API Center to Copilot Studio connector
5+
description: Learn how to export an API definition from your Azure API center as a connector in Microsoft Copilot Studio.
66
author: dlepow
77
ms.author: danlep
88
ms.service: azure-api-management
@@ -15,29 +15,29 @@ metadata:
1515
# - item
1616
# - item
1717

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.
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 use in agents.
1919
title: |
20-
"Export API from API Center to Copilot Studio as a connector"
20+
Export API definition from API Center to Copilot Studio as a connector
2121
2222
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.
23+
You can export an API definition from your Azure API center as a [connector in Microsoft Copilot Studio](/connectors/overview). The exported connector is available for use in Microsoft Copilot Studio, where it can be used by citizen developers to extend the capabilities of AI agents. [Learn more about extending agent capabilities with Copilot connectors](/microsoft-copilot-studio/copilot-connectors-in-copilot-studio).
2424
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).
25+
In this article, you create a custom connector from an OpenAPI definition associated with an API in an API center. Learn more about [creating a custom connector](/connectors/custom-connectors/define-openapi-definition) from an OpenAPI definition.
2626
prerequisites:
2727
summary: |
2828
The following are prerequisites for this procedure.
2929
3030
dependencies:
3131
- 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
32+
- An API registered in the API center inventory. The API must have a version associated with a [deployment](configure-environments-deployments.md) and an API definition in OpenAPI 2.0 format
3333
- A Power Apps [environment](/power-apps/powerapps-overview#power-apps-for-admins) to export the API to.
3434

3535

3636
procedureSection:
3737
- title: |
38-
"Export API from API Center to Copilot Studio"
38+
Export API definition from API Center
3939
summary: |
40-
Follow these steps to export an API from your Azure API center as a custom connector in Microsoft Copilot Studio.
40+
Follow these steps to export an API definition from your Azure API center as a custom connector in Microsoft Copilot Studio.
4141
4242
steps:
4343
- |
@@ -57,23 +57,21 @@ procedureSection:
5757
- |
5858
Select the **API definition** to use for the connector.
5959
- |
60-
Select the **Security requirement** type to use for the connector.
60+
Optionally, select an available **Security requirement** type to use for the connector.
6161
- |
6262
Select **Create**.
63-
The connector is now available for use in Microsoft Copilot Studio.
6463
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
64+
:::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.":::
65+
66+
67+
The connector is now available for use in Microsoft Copilot Studio.
68+
69+
You can [test the connector](/connectors/custom-connectors/define-openapi-definition#test-the-connector) in Power Automate or Power Apps. Manage the custom connector in Microsoft Copilot Studio. After testing, you can use the connector in [Microsoft Copilot Studio]() to create applications and workflows.
70+
71+
relatedContent:
72+
73+
- text: Learn more about building AI-driven agents with Microsoft Copilot Studio
74+
url: /microsoft-copilot-studio/nlu-gpt-overview
7675

77-
nextStep:
78-
text: "[Next step text]"
79-
url: link.md
76+
- text: Get started with Microsoft Copilot Studio
77+
url: /training/modules/power-virtual-agents-bots
84.1 KB
Loading

0 commit comments

Comments
 (0)