Skip to content

Commit

Permalink
Merge pull request #1785 from kavehkazms/patch-1
Browse files Browse the repository at this point in the history
Update DLP connector classification doc
  • Loading branch information
sericks007 committed Aug 1, 2023
2 parents 9c22228 + e97caf2 commit 3b8e2fe
Showing 1 changed file with 8 additions and 1 deletion.
9 changes: 8 additions & 1 deletion power-platform/admin/dlp-connector-classification.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,14 +4,15 @@ description: About ways to categorize connectors within a DLP policy.

ms.component: pa-admin
ms.topic: conceptual
ms.date: 01/05/2022
ms.date: 08/01/2023
ms.subservice: admin
author: mikferland-msft
ms.author: miferlan
ms.reviewer: jimholtz
contributors:
- mikferland-msft
- mihaelablendea
- kavehkazms
ms.custom: "admin-security"
search.audienceType:
- admin
Expand Down Expand Up @@ -82,6 +83,12 @@ The following connectors can't be blocked by using DLP policies.
> [!NOTE]
> If a currently unblockable connector is already in the **Blocked** group (for example, because it was blocked when restrictions were different), it will remain in the same group until you edit the policy. You'll get an error message stopping you from saving the policy until you move the unblockable connector to a **Business** or **Non-Business** group.
## Viewing the classification of connectors

When editing DLP policies in the Power Platform admin center, all available and visible connectors are shown, regardless of whether they have been classified in a policy. However, when viewing a DLP policy in PowerShell or through the Power Platform for Admins connector, you see only the connectors that have been explicitly classified in the Business, Non-business, or Blocked categories. DLP policies viewed from PowerShell or the Power Platform for Admins connector may include stale references to connectors that are no longer available or visible.

In general, the list of Power Platform connectors can differ depending on where you are viewing them, and there are several reasons for this. Some connectors may require specific licensing, and if your license doesn't include them, they're not visible. Different environments can also have different connectors available due to compliance and regulatory requirements. Microsoft may release updates to connectors, which may not be immediately available across all Power Platform components. Some connectors may only be available in Power Automate and not in Power Apps. Depending on your role and permissions, you may not have access to all connectors.

## Custom connector classification

### Environment-level DLP policies
Expand Down

0 comments on commit 3b8e2fe

Please sign in to comment.