Skip to content

Commit fd11d6f

Browse files
Merge pull request #226252 from inward-eye/patch-109
Update access-policies-configuration-generic.md
2 parents f72e5ce + e47cccc commit fd11d6f

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/purview/includes/access-policies-configuration-generic.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ ms.author: vlrodrig
44
ms.service: purview
55
ms.subservice: purview-data-policies
66
ms.topic: include
7-
ms.date: 10/28/2022
7+
ms.date: 02/03/2023
88
ms.custom:
99
---
1010

@@ -38,7 +38,7 @@ For more information about managing Microsoft Purview role assignments, see [Cre
3838
>[!NOTE]
3939
> Currently, Microsoft Purview roles related to creating, updating, and deleting policies must be configured at the root collection level.
4040
>
41-
> In addition to the Microsoft Purview *Policy author* role, users might need [Directory Readers](../../active-directory/roles/permissions-reference.md#directory-readers) permission in Azure Active Directory to create a policy. This is a common permission for users in an Azure tenant.
41+
> In addition, to easily search Azure AD users or groups when creating or updating the subject of a policy, the Policy Author may greatly benefit from having the [Directory Readers](../../active-directory/roles/permissions-reference.md#directory-readers) permission in Azure AD. This is a common permission for users in an Azure tenant. Without the Directory Reader permission, the Policy Author will have to type the complete username or email for all the principals included in the subject.
4242
4343
#### Configure Microsoft Purview permissions for publishing Data Owner policies
4444

0 commit comments

Comments
 (0)