Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dlp-known-issues.md #2715

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions power-platform/admin/dlp-known-issues.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,8 +4,8 @@ description: Learn more about the known limitations when using our suite of data
ms.topic: conceptual
ms.date: 11/04/2024
ms.subservice: admin
author: mikferland-msft
ms.author: miferlan
author: laneswenka
ms.author: laswenka
ms.reviewer: sericks
contributors:
- mikferland-msft
Expand All @@ -29,10 +29,10 @@ Below are known limitations to know about when using our suite of data loss prev
Power Apps treats [Dataverse native](/power-apps/maker/canvas-apps/data-platform-create-app-scratch) and [Dataverse (legacy)](/connectors/commondataservice/) connections as the same for DLP enforcement.

> [!NOTE]
> DLP authoring experiences allow [Dataverse (legacy)](/connectors/commondataservice/) and [Dataverse](/connectors/commondataserviceforapps/) connectors to be grouped separately. If the following conditions are true, it can cause an app to not be DLP compliant:
> - The Dataverse connectors are grouped separately
> - An app triggers a flow
> - Both the app and flow connect to Dataverse
> Although the DLP authoring experience supports the technical possibility of grouping [Dataverse (legacy)](/connectors/commondataservice/) and [Dataverse](/connectors/commondataserviceforapps/) connectors in separate groups, doing so may result in non-compliant Canvas Apps when:
> - The app has an embedded flow, and
> - Both the app and embedded flow connect to Dataverse
> This is due to the connector in the app being treated as Dataverse (legacy), as mentioned in the first statement of this section. **To prevent errors, both [Dataverse (legacy)](/connectors/commondataservice/) and [Dataverse](/connectors/commondataserviceforapps/) connectors must be in the same group.**

### Desktop flows
- There's no support for cross checking the categories between a cloud flow and the desktop flows it calls. This will be supported when [DLP for desktop flows](/power-automate/prevent-data-loss#data-loss-prevention-dlp-for-desktop-flows-preview) is generally available.
Expand Down