Published Jun 19, 2024
The modernized user-defined permissions experience for Microsoft 365 apps has been delayed due to a significant issue. The new feature offers a refreshed dialog for permissions configuration and renames usage rights groupings, with the rollout expected to begin in mid-July 2024 for preview and early September 2024 for general availability. Organizations may need to update internal documentation accordingly.
Updated October 25, 2024: We recently discovered a significant issue that has resulted in the temporary disabling of this feature until it is resolved. We apologize for any inconvenience this may cause.
There is a new experience for selecting which users should have which permissions when a sensitivity label configured for user-defined permissions is applied to a file in Microsoft 365 apps or when a user applies protection using standalone Information Rights Management.
This message is associated with Microsoft 365 Roadmap ID 189826
When this will happen:
Preview (Worldwide, GCC): We will begin rolling out mid-July 2024 and expect to complete by late July 2024.
General Availability (Worldwide, GCC): We will begin rolling out early September 2024 and expect to complete by late November 2024 (previously late September).
How this will affect your organization:
Users will see a modernized dialog when configuring user-defined permissions, whether these are applied using a sensitivity label configured for user-defined permissions or with standalone Information Rights Management. There are new names for some usage rights groupings for pre-set permissions levels compared to those in Microsoft Azure Information Protection (AIP):
The rights contained in each grouping are unchanged.
See Configure usage rights for Azure Information Protection for further information on usage rights.
This new feature is available by default.
What you need to do to prepare:
If your organization has training materials or internal documentation regarding the use of pre-set permissions levels, you may need to make updates based on the new names for these permissions levels.