[CoE Starter Kit - BUG] DLP Policy Main Form - Connectors wrongly assigned to blocked/confidential

[P-focT]

Does this bug already exist in our backlog?

• I have checked and confirm this is a new bug.

Describe the issue

Having a DLP policy with a blocked connector, which is made visible to a Maker, triggers synchronization with Dataverse.

Using the Power Platform for Admin View
Choose - Environment and temporarily relate a DLP Policy to the environment. Access the DLP Policy record.
The related Connector is successfully assigned to the DLP Policy record, but shown as confidential instead of blocked.

Having a look at the API on the admin_dlppolicy table, everything looks good:

{
"@odata.context": "https://xyz.crm4.dynamics.com/api/data/v9.2/$metadata#admin_dlppolicies(admin_name,admin_blocked_policy_connectors(admin_displayname),admin_confidential_policy_connectors(admin_displayname))",
"value": [
{
"@odata.etag": "W/\"15063984\"",
"admin_name": "Block HTTP",
"admin_dlppolicyid": "xxx-xxx-xxx-xxx",
"admin_blocked_policy_connectors": [
{
"@odata.etag": "W/\"14983677\"",
"admin_displayname": "HTTP",
"admin_connectorid": "xxx-xxx-xxx-xxx"
}
],
"admin_confidential_policy_connectors": [],
}
]
}

Having a look at the main form of the DLP Policy it seems as the relationships for confidential and blocked connectors have been swapped.

Expected Behavior

On the Main Form of the DLP Policy entity I expect blocked connectors to show up in the blocked connectors subgrid.

What solution are you experiencing the issue with?

Core

What solution version are you using?

4.13

What app or flow are you having the issue with?

Power Platform for Admin View

What method are you using to get inventory and telemetry?

None

Steps To Reproduce

1. Create a DLP solution from the Admin Center
2. Assign a Connector to the blocked category
3. Publish
4. Go to the Admin - Environment Request app
5. Choose Data policies
6. Select the previously created DLP policy and click make visible
7. Go to the Power Platform for Admin View app and select an environment
8. Relate this DLP policy with the environment
9. Navigate to the DLP policy
10. Choose the Connectors tab on the form

Anything else?

No response

[manuelap-msft]

Looks like we had the wrong views selected in those subgrids. Fixed for September.

I'm not sure what your use case is for relating Environments to the DLP policy in the Power Platform Admin View, but note that this won't add the environment to the DLP policy. You'll have to do that in the admin center.

[P-focT]

Thank you for the quick reply, I know they are not linked, but it was the quickest way to access the DLP policy record ;)

[manuelap-msft]

Would it be helpful if we added the DLP Policy table to the Power Platform Admin View so you could access it from there to browse policies you made visible?

[P-focT]

Yeah, I think that would be a great idea. Thanks a lot

[manuelap-msft]

Ok I've added that for the September release as well.

[CoEStarterKitBot]

@P-focT This has been fixed in the latest release. Please install the latest version of the toolkit following the instructions for installing updates. Note that if you do not remove the unmanaged layers as described there you will not receive updates from us.