You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Seems like a bug when trying to export the impact analysis to csv:
This is me trying to edit a "Exclude certain environments" Scope DLP where the default environment currently is excluded. I want it to be "Available" instead by doing:
Open the new DLP Impact Analysis App -> "Edit Policy" -> Select Default environment ->Press "Remove from policy"->Next
No impacted apps/flows visibly, there should be, and when pressing "Export to CSV" the flow run fails.
I believe the logic does not account for the case when a policy that has the scope "Exclude certain environments", and we remove such an exception, it does not get added to the data of envs that should be checked. Can that be correct? Or how can I get around this?
(Since if I try the app with a Scope "Add multiple environments" and try to add an environment, the data shows up and the flow runs fine).
Really appreciate an answer, need to assess this DLP change :) Thanks.
(By the way, either the data is wrong or the showing within the app that every Environment in my list is called the same..? This is only also appearing for when I'm editing the "Exclude certain environments" DLP. In the Admin View App, all environment names are correct.
(By the way 2, also when editing the same DLP, the Default Environment incorrectly shows up in the "Available" list in the DLP Impact Analysis app, which is should not:
From admin center:
Expected Behavior
No response
What solution are you experiencing the issue with?
Core
What solution version are you using?
4.15
What app or flow are you having the issue with?
DLP Editor>Parse impacted resources into CSV
What method are you using to get inventory and telemetry?
Cloud flows
Steps To Reproduce
See above
Anything else?
No response
AB#584
The text was updated successfully, but these errors were encountered:
Does this bug already exist in our backlog?
Describe the issue
Seems like a bug when trying to export the impact analysis to csv:
This is me trying to edit a "Exclude certain environments" Scope DLP where the default environment currently is excluded. I want it to be "Available" instead by doing:
Open the new DLP Impact Analysis App -> "Edit Policy" -> Select Default environment ->Press "Remove from policy"->Next
No impacted apps/flows visibly, there should be, and when pressing "Export to CSV" the flow run fails.
I believe the logic does not account for the case when a policy that has the scope "Exclude certain environments", and we remove such an exception, it does not get added to the data of envs that should be checked. Can that be correct? Or how can I get around this?
(Since if I try the app with a Scope "Add multiple environments" and try to add an environment, the data shows up and the flow runs fine).
Really appreciate an answer, need to assess this DLP change :) Thanks.
(By the way, either the data is wrong or the showing within the app that every Environment in my list is called the same..? This is only also appearing for when I'm editing the "Exclude certain environments" DLP. In the Admin View App, all environment names are correct.
(By the way 2, also when editing the same DLP, the Default Environment incorrectly shows up in the "Available" list in the DLP Impact Analysis app, which is should not:
From admin center:
Expected Behavior
No response
What solution are you experiencing the issue with?
Core
What solution version are you using?
4.15
What app or flow are you having the issue with?
DLP Editor>Parse impacted resources into CSV
What method are you using to get inventory and telemetry?
Cloud flows
Steps To Reproduce
See above
Anything else?
No response
AB#584
The text was updated successfully, but these errors were encountered: