Skip to content

Commit 0f4af4f

Browse files
authored
Merge pull request #207915 from dlepow/ppupd
[APIM] Update Power Platform custom connector
2 parents 1f45bac + abefd57 commit 0f4af4f

File tree

2 files changed

+22
-4
lines changed

2 files changed

+22
-4
lines changed

articles/api-management/TOC.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -222,8 +222,6 @@
222222
href: api-management-revisions.md
223223
- name: Backends
224224
href: backends.md
225-
- name: Export APIs to the Power Platform
226-
href: export-api-power-platform.md
227225
- name: Automate API deployments
228226
href: /azure/architecture/example-scenario/devops/automated-api-deployments-apiops?toc=%2Fazure%2Fapi-management%2Ftoc.json&bc=/azure/api-management/breadcrumb/toc.json
229227
- name: Cache
@@ -341,6 +339,8 @@
341339
href: developer-portal-use-community-widgets.md
342340
- name: Test self-hosted portal
343341
href: developer-portal-testing.md
342+
- name: Export APIs to the Power Platform
343+
href: export-api-power-platform.md
344344
- name: Monitor APIs
345345
items:
346346
- name: Get API analytics

articles/api-management/export-api-power-platform.md

Lines changed: 20 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: dlepow
66

77
ms.service: api-management
88
ms.topic: how-to
9-
ms.date: 07/27/2021
9+
ms.date: 08/12/2022
1010
ms.author: danlep
1111

1212
---
@@ -31,6 +31,7 @@ This article walks through the steps in the Azure portal to create a custom Powe
3131
1. Select an API to publish to the Power Platform.
3232
1. Select a Power Platform environment to publish the API to.
3333
1. Enter a display name, which will be used as the name of the custom connector.
34+
1. Optionally, if the API doesn't already require a subscription, select **Create subscription key connection parameter**.
3435
1. Optionally, if the API is [protected by an OAuth 2.0 server](api-management-howto-protect-backend-with-aad.md), provide details including **Client ID**, **Client secret**, **Authorization URL**, **Token URL**, and **Refresh URL**.
3536
1. Select **Create**.
3637

@@ -40,8 +41,25 @@ Once the connector is created, navigate to your [Power Apps](https://make.powera
4041

4142
:::image type="content" source="media/export-api-power-platform/custom-connector-power-app.png" alt-text="Custom connector in Power Platform":::
4243

44+
## Manage a custom connector
45+
46+
You can manage your custom connector in your Power Apps or Power Platform environment. For details about settings, see [Create a custom connector from scratch](/connectors/custom-connectors/define-blank).
47+
48+
1. Select your connector from the list of custom connectors.
49+
1. Select the pencil (Edit) icon to edit and test the custom connector.
50+
4351
> [!NOTE]
44-
> To call the API from the Power Apps test console, you need to add the "https://flow.microsoft.com" URL as an origin to the [CORS policy](api-management-cross-domain-policies.md#CORS) in your API Management instance.
52+
> To call the API from the Power Apps test console, you need to add the `https://flow.microsoft.com` URL as an origin to the [CORS policy](api-management-cross-domain-policies.md#CORS) in your API Management instance.
53+
54+
## Update a custom connector
55+
56+
From API Management, you can update a connector to target a different API or Power Apps environment, or to update authorization settings.
57+
58+
1. Navigate to your API Management service in the Azure portal.
59+
1. In the menu, under **APIs**, select **Power Platform**.
60+
1. Select **Update a connector**.
61+
1. Select the API you want to update the connector for, update settings as needed, and select **Update**.
62+
4563

4664
## Next steps
4765

0 commit comments

Comments
 (0)