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?
Hi @jwesener2 ,
Have you checked below documentation before managing custom connectors in DLP policies?
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.