From bd80fbc5063072a817a47584620b7a776a5620e6 Mon Sep 17 00:00:00 2001 From: kavehkazms Date: Thu, 16 Feb 2023 13:11:54 -0800 Subject: [PATCH 1/2] Update DLP connector classification doc Update DLP connector classification doc to clarify discrepancies when viewing the DLP policy --- power-platform/admin/dlp-connector-classification.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/power-platform/admin/dlp-connector-classification.md b/power-platform/admin/dlp-connector-classification.md index 391cd2983e..b62faa7b5f 100644 --- a/power-platform/admin/dlp-connector-classification.md +++ b/power-platform/admin/dlp-connector-classification.md @@ -87,6 +87,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 via the Power Platform for Admins connector, you will only see the connectors that have been explicitly classified (i.e. 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 will not be 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 From e97caf24bfc8b48cec51d7e480d04e47cd3e688f Mon Sep 17 00:00:00 2001 From: Sally Erickson Date: Tue, 1 Aug 2023 12:58:04 -0500 Subject: [PATCH 2/2] Update dlp-connector-classification.md --- power-platform/admin/dlp-connector-classification.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/power-platform/admin/dlp-connector-classification.md b/power-platform/admin/dlp-connector-classification.md index b62faa7b5f..b2c309f967 100644 --- a/power-platform/admin/dlp-connector-classification.md +++ b/power-platform/admin/dlp-connector-classification.md @@ -4,7 +4,7 @@ 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 @@ -12,6 +12,7 @@ ms.reviewer: jimholtz contributors: - mikferland-msft - mihaelablendea + - kavehkazms ms.custom: "admin-security" search.audienceType: - admin @@ -89,9 +90,9 @@ The following connectors can't be blocked by using DLP policies. ## 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 via the Power Platform for Admins connector, you will only see the connectors that have been explicitly classified (i.e. 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. +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 will not be 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. +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