Skip to content

Commit 7834670

Browse files
authored
Merge pull request #21213 from cabailey/cabailey-m365docs-adminunitsmiponly
7/5: Admin units GA for MIP only
2 parents dbcf661 + 66fbda7 commit 7834670

4 files changed

Lines changed: 13 additions & 7 deletions

File tree

microsoft-365/compliance/apply-sensitivity-label-automatically.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: cabailey
77
manager: laurawi
88
audience: Admin
99
ms.service: O365-seccomp
10-
ms.date: 06/28/2023
10+
ms.date: 07/05/2023
1111
ms.localizationpriority: high
1212
ms.collection:
1313
- purview-compliance
@@ -331,7 +331,7 @@ Finally, you can use simulation mode to provide an approximation of the time nee
331331

332332
4. For the page **Name your auto-labeling policy**: Provide a unique name, and optionally a description to help identify the automatically applied label, locations, and conditions that identify the content to label.
333333

334-
5. For the page **Assign admin units**: This configuration is currently in preview. If your organization is using [administrative units in Azure Active Directory](/azure/active-directory/roles/administrative-units), auto-labeling policies for Exchange and OneDrive can be automatically restricted to specific users by selecting administrative units. If your account has been [assigned administrative units](microsoft-365-compliance-center-permissions.md#administrative-units-preview), you must select one or more administrative units.
334+
5. For the page **Assign admin units**: If your organization is using [administrative units in Azure Active Directory](/azure/active-directory/roles/administrative-units), auto-labeling policies for Exchange and OneDrive can be automatically restricted to specific users by selecting administrative units. If your account has been [assigned administrative units](microsoft-365-compliance-center-permissions.md#administrative-units-preview), you must select one or more administrative units.
335335

336336
If you don't want to restrict the policy by using administrative units, or your organization hasn't configured administrative units, keep the default of **Full directory**.
337337

microsoft-365/compliance/create-sensitivity-labels.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ f1.keywords:
55
ms.author: cabailey
66
author: cabailey
77
manager: laurawi
8-
ms.date: 06/10/2023
8+
ms.date: 07/05/2023
99
audience: Admin
1010
ms.topic: conceptual
1111
ms.service: O365-seccomp
@@ -161,7 +161,7 @@ To check your label's configuration, including advanced settings, use the follow
161161
> [!IMPORTANT]
162162
> If you select a sublabel, make sure you also select its parent label.
163163
164-
4. For the **Assign admin units**: This configuration is currently in preview. If your organization is using [administrative units in Azure Active Directory](/azure/active-directory/roles/administrative-units), the label policy can be automatically restricted to specific users by selecting administrative units. If your account has been [assigned administrative units](microsoft-365-compliance-center-permissions.md#administrative-units-preview), you must select one or more administrative units.
164+
4. For the **Assign admin units**: If your organization is using [administrative units in Azure Active Directory](/azure/active-directory/roles/administrative-units), the label policy can be automatically restricted to specific users by selecting administrative units. If your account has been [assigned administrative units](microsoft-365-compliance-center-permissions.md#administrative-units-preview), you must select one or more administrative units.
165165

166166
If you don't want to restrict the policy by using administrative units, or your organization hasn't configured administrative units, keep the default of **Full directory**.
167167

microsoft-365/compliance/get-started-with-sensitivity-labels.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ f1.keywords:
55
ms.author: cabailey
66
author: cabailey
77
manager: laurawi
8-
ms.date: 06/08/2023
8+
ms.date: 07/05/2023
99
audience: Admin
1010
ms.topic: conceptual
1111
ms.service: O365-seccomp
@@ -78,7 +78,7 @@ These permissions are required only to create and configure sensitivity labels a
7878

7979
## Support for administrative units
8080

81-
Now in preview, sensitivity labels support [administrative units that have been configured in Azure Active Directory](/azure/active-directory/roles/administrative-units):
81+
Sensitivity labels support [administrative units that have been configured in Azure Active Directory](/azure/active-directory/roles/administrative-units):
8282

8383
- You can assign administrative units to members of role groups that are used with Microsoft Purview Information Protection. Edit these role groups and select individual members, and then the **Assign admin units** option to select administrative units from Azure Active Directory. These administrators are now restricted to managing just the users in those administrative units.
8484

microsoft-365/compliance/whats-new.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ f1.keywords:
66
ms.author: robmazz
77
author: robmazz
88
manager: laurawi
9-
ms.date: 07/03/2023
9+
ms.date: 07/05/2023
1010
audience: Admin
1111
ms.topic: reference
1212
ms.service: O365-seccomp
@@ -39,6 +39,12 @@ Whether it be adding new solutions to the [Microsoft Purview compliance portal](
3939
4040
[!INCLUDE [purview-preview](../includes/purview-preview.md)]
4141

42+
## July 2023
43+
44+
### Sensitivity labels
45+
46+
- **General availability (GA)**: [Support for administrative units](get-started-with-sensitivity-labels.md#support-for-administrative-units).
47+
4248
## June 2023
4349

4450
### Data lifecycle management and records management

0 commit comments

Comments
 (0)