web

You’re offline. This is a read only version of the page.

News and Announcements icon

Power Platform CommunityForums Power Apps Custom Connector canno...

Power Apps

Unanswered

Custom Connector cannot be removed from policy

(0) Share

Report

Report

Posted on by Community Power Pla... Microsoft Employee

We added a custom connector to our DLP policy to allow to be used with other business data via Powershell and now when we try to remove it, it throws an error that it is not in the policy. However, when we list out the connectors in the policy, it is clearly there.

Also, after adding it, we still can't use it in our Flows/PowerApps (hence why we are trying to add/remove it)

Is there some sort of timing thing that needs to happen when running the Admin Powershell commands on the DLP Policies?

Categories:

Governance & administering

All responses Img

All responses (2)

Answers Img

Answers (0)

Sort by

v-monli-msft Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @Anonymous ,

Have you checked below documentation before managing custom connectors in DLP policies?

https://flow.microsoft.com/en-us/blog/introducing-http-and-custom-connector-support-for-data-loss-prevention-policies/

Please notice:

Only Custom Connectors stored in a tenant’s default environment will be displayed with its given icon and display name in the policy editor. All other custom connectors will be displayed with the default connector icon and their internal name.

Caution: WE DO NOT SUPPORT DOWNGRADING FROM SCHEMA VERSION 2018-11-01. Once HTTP support is added to a policy, it cannot be taken away. Attempting to do so may corrupt that DLP policy. Furthermore, if a DLP policy is updated to support HTTP connectors, current flows using these HTTP capabilities may be shut off.

Regards,

Mona
AlexDorfmayr 49 on at

Like
a
(0)

Report
Copy link

Link copied!
Hi @anonymous,
not sure if the cmdlt has been updated or anythin else has changed but for me I could remove my custom connector from a dlp.
The only thing I realised is that the "connector name" is clearly misleading because they actually want the "connector id" - with this in mind the removal works just fine for me.... this was my try - worked for me:

PS C:\Users\ABCDE> Remove-CustomConnectorFromPolicy Cmdlet Remove-CustomConnectorFromPolicy an der Befehlspipelineposition 1 Geben Sie Werte für die folgenden Parameter an: PolicyName: 2334XXXX-XXXX-XXXX-XXXX-XXXXaf04d0f6 ConnectorName: 5f645ebXXXXXXXXX-XXXXXXXXX579b43c6

Join the conversation