Solved: Cannot Add to DLP - error message "cannot read pro...

ZiaUddin · ‎06-08-2021

Hi

We have a bunch of DLP's setup, one for each of our environment(s). However, we want to move a connector from non-business to business, which we do for the environment, but when we reach the point where we 'Save' and update the policy (Review stage), we are shown an error message which essentially says:

It looks like something went wrong

We couldn't get the information you're looking for.

Cannot read property 'rules' of undefined

Time: 2021-06-08T10:06:31.594Z

Session Id: a92a7619-25f5-416f-b416-b8bebdf57886

Please can someone advise, this issue is not to do with the specific connector we are moving, as it seems to have happen for any connector we try and add now. So I am not quite sure what is going one. Note the specific connector we are trying to update the the policy is (after moving it to the Business connectors list) is named 'HTTP with Azure AD'. Note that months ago (maybe 3 months ago) we were able to add to do this to another Data Policy we have setup for Dev environment, but cannot understand why we cannot add to this UAT data policy we have had for a while. A few other facts:

1) There are existing connectors in the Business group already setup from months ago, and they are still in place.

2) I am an environment maker and PowerApps admin - and I get the above issue as described.

3) Our tenant admin has also had a go and gets the same issue.

Please assist with this if you can - we are unable to deploy some Flow changes because we require the specific connectors to be in place in the DLP.

ZiaUddin · ‎06-08-2021

Hi All,

don't know if MS did anything in the background, but I seem to have it working now; for some reason I am not getting that error anymore and was able to update the policy by adding the connector to the business group. One thing I did differently was actually create a dummy test Data Policy group to see if it would work and that did, after that I wen into the others that were failing and then they suddenly started accepting and saving the connectors. Don't know if it just wanted a kick to get it going but it worked.

I am closing this off.

View solution in original post

ZiaUddin · ‎06-08-2021

Hi All,

don't know if MS did anything in the background, but I seem to have it working now; for some reason I am not getting that error anymore and was able to update the policy by adding the connector to the business group. One thing I did differently was actually create a dummy test Data Policy group to see if it would work and that did, after that I wen into the others that were failing and then they suddenly started accepting and saving the connectors. Don't know if it just wanted a kick to get it going but it worked.

I am closing this off.

alrez · ‎06-09-2021

Hi,

Thanks for your follow up post! I am glad that you were able to get this figured out on your side. Hopefully this will prove useful for any future communities users who are having similar issues.

Regards,

Alex

-------

Community Support Team _ Alex Rezac
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.