cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
Helper I
Helper I

Custom Connector in the Environment Data Policy

Dear everyone,

 

I have an issue that the Data Policy / DLP is still blocking combination of connectors and custom connector in my PowerApps.

 

Setup of the Data Policy

 

The result in the Data Policy UI is also positive actually:

  • In PowerPlatform Admin (Data Policy Preview) this custom connectors are NOT visible. 
  • In PowerApps Admin:
    2020-05-04_16-42-17.png
  • The standard connectors and custom connectors are all added and visible in the PowerApps Admin

 

The result in the PowerApps

  • Combination of 2 standard connectors are working. 😀
    • 2020-05-06_10-08-00.png
  • If I try to add Custom Connector in combination with the standand connector, the issues happens. 😟
    • It keeps on showing the following error: Conflict with the company data loss prevention policies
    • 2020-05-06_10-04-46.png

 

Anyone could help??

Thanks.

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Helper I
Helper I

Re: Custom Connector in the Environment Data Policy

Hi @v-xida-msft ,

after long email with MS Support, they came with the suggestion:

  • “I noticed that you also have a Global policy which applies to all environments in your tenant.  And since custom connector cannot be added to global policy, it means a custom connector cannot work alongside with any other connectors

    I understood that's why you created a env-specific policy for it.  However, the way it works when multiple policies exist is that the most restrictive rule wins; as a result, the custom policy does not work here.”

  • One thing we can try here is to change the Global policy to exclude the environment in which you want to run custom connector with CDS and Office365Users. 

  • This is where you can exclude the Environment from the Global Policy
    2020-05-31_11-35-00-GlobalPolicy.png

 

For how to add the custom connector using the Power Shell, these 2 articles are helpful and the steps are working:

Thanks all. 

 

 

View solution in original post

7 REPLIES 7
Highlighted
Frequent Visitor

Re: Custom Connector in the Environment Data Policy

Hi,
Even I am also facing the same problem

Highlighted
Community Support
Community Support

Re: Custom Connector in the Environment Data Policy

Hi @hsu ,

Based on the issue that you mentioned, I have made a test, and the issue is confirmed on my side. The Custom connector would be visible in PowerApps Admin Center, but not in Power Platform Admin Center.

 

Actually, the DLP Policy feature in Power Platform Admin Center is still in Preview, the whole DLP feature in PowerApps Admin Center has not been migrated into Power Platform Admin Center.

 

If you would like this feature to be achieved in Power Platform Admin Center, please consider submit an idea to PowerApps Ideas Forum:

https://powerusers.microsoft.com/t5/Power-Apps-Ideas/idb-p/PowerAppsIdeas

 

Simultaneously, the DLP setting you set up in your PowerApps Admin Center would still take effect within PowerApps Environment.

 

Best regards,

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Highlighted
Helper I
Helper I

Re: Custom Connector in the Environment Data Policy

Hi @v-xida-msft ,

 

thanks for your confirmation about the differences in the Admin UI.

 

However, I need help to enable the usage of custom connector and standard connector in the data policy.

Now I tried already for hours, deleting and re-creating the policy, but still it does not work.

 

Any guidelines on how to setup environment level data policy for custom connectors and also how to debug it?

 

Or anyone successfully create and able to share?

 

Or @v-xida-msft : Any suggestion on how to get further help from MS?

 

Thank you in advance.

Highlighted
Community Support
Community Support

Re: Custom Connector in the Environment Data Policy

Hi @hsu ,

Do you want to use the standard connector and custom connector together within your canvas app against the DLP?

 

I have made a test on my side, and the standard connector and custom connector could work together within my Environment the DLP applied to (add some standard connectors and custom connector into Business Data Only Group). When add another standard connector (in Non-Business Data Group) into my canvas app, the error would show up:

1.JPG

 

Please make sure the DLP you set up has been applied to proper Environment on your side. Also please take a try to re-create a new DLP policy on your side using PowerApps PowerShell cmdlets:

https://alextofan.com/2019/05/15/how-to-add-http-actions-and-custom-connectors-to-a-data-loss-preven...

Also please make sure the custom connector you added into the "Business Data Only Group" of your DLP is the same as that you want to add/use within your canvas app in current Environment.

 

If the issue still exists, please consider submit an assisted support ticket through the following link:

https://powerapps.microsoft.com/en-us/support/pro

 

Best regards,

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Highlighted
Helper I
Helper I

Re: Custom Connector in the Environment Data Policy

Hi @v-xida-msft ,

 

I have repeated the steps in the Personal Productivity environment, and also still failed to add 2 connectors (1 standard premium, 1 custom connector). Another info here is that my custom connector is to access intranet resource utilizing the On Prem Gateway.

 

At the end I created a support ticket as your suggestion.

 

Thanks and meanwhile I will wait. 

Highlighted
Helper I
Helper I

Re: Custom Connector in the Environment Data Policy

About this I have exchanged emails with Microsoft support and then with the PowerPlatform technical engineer.

Their suggestions is going to the direction that the Global Policy is preventing it.

However I think there is still inconsistent message.

 

I also still need to verify their latest suggestions, by setting something using the PowerShell.

 

Will update again in the future.

 

Highlighted
Helper I
Helper I

Re: Custom Connector in the Environment Data Policy

Hi @v-xida-msft ,

after long email with MS Support, they came with the suggestion:

  • “I noticed that you also have a Global policy which applies to all environments in your tenant.  And since custom connector cannot be added to global policy, it means a custom connector cannot work alongside with any other connectors

    I understood that's why you created a env-specific policy for it.  However, the way it works when multiple policies exist is that the most restrictive rule wins; as a result, the custom policy does not work here.”

  • One thing we can try here is to change the Global policy to exclude the environment in which you want to run custom connector with CDS and Office365Users. 

  • This is where you can exclude the Environment from the Global Policy
    2020-05-31_11-35-00-GlobalPolicy.png

 

For how to add the custom connector using the Power Shell, these 2 articles are helpful and the steps are working:

Thanks all. 

 

 

View solution in original post

Helpful resources

Announcements
August 2020 Community Challenge: Can You Solve These?

August 2020 Community Challenge: Can You Solve These?

We're excited to announce our first cross-community 'Can You Solve These?' challenge!

secondImage

Return to Workplace

Reopen responsibly, monitor intelligently, and protect continuously with solutions for a safer work environment.

secondImage

Super Users Coming in August

We are excited for the next Super User season.

secondImage

Community User Group Member Badges

FIll out a quick form to claim your community user group member badge today!

secondImage

Power Platform 2020 release wave 2 plan

Features releasing from October 2020 through March 2021

Users online (6,686)