check before: 2023-09-06
Product:
Microsoft Graph, Microsoft Loop, Planner, Purview Information Protection
Platform:
Developer, US Instances, Web, World tenant
Status:
Launched
Change type:
Admin impact, New feature, Updated message
Links:
Details:
Microsoft Planner will soon support container sensitivity labels for rosters, which can be set to respect policy settings. The rollout will begin in early January 2024 and is expected to complete by early March 2024. Rosters can be configured with container labels being mandatory, and if a request is made without a label, it will be rejected. It is the client's responsibility to apply the default label to ensure roster creation does not fail when labels are mandatory.
Updated February 16, 2024: We have updated the rollout timeline below. Thank you for your patience.
Customers will soon be able to apply container labels to rosters in Microsoft Planner. This is enabled directly in Planner by using Microsoft Graph APIs. When this feature is rolled out, the roster sensitivity labels can be set to respect the policy settings. If the tenant admin has made container labels mandatory and has set a default label, then the default label will be used for roster creation through Microsoft Loop client.
On the Loop client, if the default label is provided, it will be used as the roster's lable when creating the roster. The roster system will not allow the user to create an unlabeled roster or to un-label a previously labeled roster.
On the Microsoft Graph API, if a request is made and the label is not included, the request is rejected as the default label is not applied by the service. Users will need to ensure that a default label is provided when labels are mandatory so that roster creation does not fail.
Note: The container sensitivity label applied to a roster applies only to the information in Microsoft Planner and does not protect or encrypt the information when it syncs with the Loop client.
This message is associated with Microsoft 365 Roadmap ID 155837
[When this will happen:]
We will begin rolling out in early January 2024 (previously late October) and is expected to complete by early March 2024 (previously early February).
USSec/USNat: Rollout will begin in mid-March 2024 (previously late January) and is expected to complete by mid-April 2024 (previously late February).
Change Category:
XXXXXXX ...
Scope:
XXXXXXX ...
Release Phase:
General Availability
Created:
2023-08-23
updated:
2024-02-17
the free basic plan is required to see all details. Sign up here
A cloudsocut.one plan is required to see all the changed details. If you are already a customer, choose login.
If you are new to cloudscout.one please choose a plan.
changes*
| Date | Property | old | new |
| 2024-02-17 | MC Last Updated | 11/02/2023 23:54:53 | 2024-02-16T23:41:37Z |
| 2024-02-17 | MC Messages | Updated November 2, 2023: We have updated the rollout timeline below. Thank you for your patience.
Customers will soon be able to apply container labels to rosters in Microsoft Planner. This is enabled directly in Planner by using Microsoft Graph APIs. When this feature is rolled out, the roster sensitivity labels can be set to respect the policy settings. If the tenant admin has made container labels mandatory and has set a default label, then the default label will be used for roster creation through Microsoft Loop client. On the Loop client, if the default label is provided, it will be used as the roster's lable when creating the roster. The roster system will not allow the user to create an unlabeled roster or to un-label a previously labeled roster. On the Microsoft Graph API, if a request is made and the label is not included, the request is rejected as the default label is not applied by the service. Users will need to ensure that a default label is provided when labels are mandatory so that roster creation does not fail. Note: The container sensitivity label applied to a roster applies only to the information in Microsoft Planner and does not protect or encrypt the information when it syncs with the Loop client. This message is associated with Microsoft 365 Roadmap ID 155837 [When this will happen:] We will begin rolling out in early January 2024 (previously late October) and is expected to complete by early February 2024 (previously late November). | Updated February 16, 2024: We have updated the rollout timeline below. Thank you for your patience.
Customers will soon be able to apply container labels to rosters in Microsoft Planner. This is enabled directly in Planner by using Microsoft Graph APIs. When this feature is rolled out, the roster sensitivity labels can be set to respect the policy settings. If the tenant admin has made container labels mandatory and has set a default label, then the default label will be used for roster creation through Microsoft Loop client. On the Loop client, if the default label is provided, it will be used as the roster's lable when creating the roster. The roster system will not allow the user to create an unlabeled roster or to un-label a previously labeled roster. On the Microsoft Graph API, if a request is made and the label is not included, the request is rejected as the default label is not applied by the service. Users will need to ensure that a default label is provided when labels are mandatory so that roster creation does not fail. Note: The container sensitivity label applied to a roster applies only to the information in Microsoft Planner and does not protect or encrypt the information when it syncs with the Loop client. This message is associated with Microsoft 365 Roadmap ID 155837 [When this will happen:] We will begin rolling out in early January 2024 (previously late October) and is expected to complete by early March 2024 (previously early February). USSec/USNat: Rollout will begin in mid-March 2024 (previously late January) and is expected to complete by mid-April 2024 (previously late February). |
| 2024-02-17 | MC End Time | 03/18/2024 09:00:00 | 2024-04-08T10:00:00Z |
| 2024-02-17 | MC Summary | Microsoft Planner will soon support container sensitivity labels for rosters, which can be set to respect policy settings. The rollout will begin in early January 2024 and is expected to complete by early March 2024. Rosters can be configured with container labels being mandatory, and if a request is made without a label, it will be rejected. It is the client's responsibility to apply the default label to ensure roster creation does not fail when labels are mandatory. | |
| 2023-11-03 | MC Last Updated | 09/27/2023 21:28:16 | 2023-11-02T23:54:53Z |
| 2023-11-03 | MC Messages | Updated September 27, 2023: We have updated the rollout timeline below. Thank you for your patience.
Customers will soon be able to apply container labels to rosters in Microsoft Planner. This is enabled directly in Planner by using Microsoft Graph APIs. When this feature is rolled out, the roster sensitivity labels can be set to respect the policy settings. If the tenant admin has made container labels mandatory and has set a default label, then the default label will be used for roster creation through Microsoft Loop client. On the Loop client, if the default label is provided, it will be used as the roster's lable when creating the roster. The roster system will not allow the user to create an unlabeled roster or to un-label a previously labeled roster. On the Microsoft Graph API, if a request is made and the label is not included, the request is rejected as the default label is not applied by the service. Users will need to ensure that a default label is provided when labels are mandatory so that roster creation does not fail. Note: The container sensitivity label applied to a roster applies only to the information in Microsoft Planner and does not protect or encrypt the information when it syncs with the Loop client. This message is associated with Microsoft 365 Roadmap ID 155837 [When this will happen:] We will begin rolling out in late October 2023 (previously mid-September) and is expected to complete by late November 2023 (previously mid-October). | Updated November 2, 2023: We have updated the rollout timeline below. Thank you for your patience.
Customers will soon be able to apply container labels to rosters in Microsoft Planner. This is enabled directly in Planner by using Microsoft Graph APIs. When this feature is rolled out, the roster sensitivity labels can be set to respect the policy settings. If the tenant admin has made container labels mandatory and has set a default label, then the default label will be used for roster creation through Microsoft Loop client. On the Loop client, if the default label is provided, it will be used as the roster's lable when creating the roster. The roster system will not allow the user to create an unlabeled roster or to un-label a previously labeled roster. On the Microsoft Graph API, if a request is made and the label is not included, the request is rejected as the default label is not applied by the service. Users will need to ensure that a default label is provided when labels are mandatory so that roster creation does not fail. Note: The container sensitivity label applied to a roster applies only to the information in Microsoft Planner and does not protect or encrypt the information when it syncs with the Loop client. This message is associated with Microsoft 365 Roadmap ID 155837 [When this will happen:] We will begin rolling out in early January 2024 (previously late October) and is expected to complete by early February 2024 (previously late November). |
| 2023-11-03 | MC End Time | 12/30/2023 09:00:00 | 2024-03-18T09:00:00Z |
| 2023-09-28 | MC Messages | Updated August 30, 2023: We have updated the rollout timeline below. Thank you for your patience.
Customers will soon be able to apply container labels to rosters in Microsoft Planner. This is enabled directly in Planner by using Microsoft Graph APIs. When this feature is rolled out, the roster sensitivity labels can be set to respect the policy settings. If the tenant admin has made container labels mandatory and has set a default label, then the default label will be used for roster creation through Microsoft Loop client. On the Loop client, if the default label is provided, it will be used as the roster's lable when creating the roster. The roster system will not allow the user to create an unlabeled roster or to un-label a previously labeled roster. On the Microsoft Graph API, if a request is made and the label is not included, the request is rejected as the default label is not applied by the service. Users will need to ensure that a default label is provided when labels are mandatory so that roster creation does not fail. Note: The container sensitivity label applied to a roster applies only to the information in Microsoft Planner and does not protect or encrypt the information when it syncs with the Loop client. This message is associated with Microsoft 365 Roadmap ID 155837 [When this will happen:] We will begin rolling out in mid-September 2023 (previously late August) and is expected to complete by mid-October 2023 (previously late September). < | Updated September 27, 2023: We have updated the rollout timeline below. Thank you for your patience.
Customers will soon be able to apply container labels to rosters in Microsoft Planner. This is enabled directly in Planner by using Microsoft Graph APIs. When this feature is rolled out, the roster sensitivity labels can be set to respect the policy settings. If the tenant admin has made container labels mandatory and has set a default label, then the default label will be used for roster creation through Microsoft Loop client. On the Loop client, if the default label is provided, it will be used as the roster's lable when creating the roster. The roster system will not allow the user to create an unlabeled roster or to un-label a previously labeled roster. On the Microsoft Graph API, if a request is made and the label is not included, the request is rejected as the default label is not applied by the service. Users will need to ensure that a default label is provided when labels are mandatory so that roster creation does not fail. Note: The container sensitivity label applied to a roster applies only to the information in Microsoft Planner and does not protect or encrypt the information when it syncs with the Loop client. This message is associated with Microsoft 365 Roadmap ID 155837 [When this will happen:] We will begin rolling out in late October 2023 (previously mid-September) and is expected to complete by late November 2023 (previously mid-October). |
| 2023-09-28 | MC Last Updated | 08/30/2023 23:36:12 | 2023-09-27T21:28:16Z |
| 2023-08-31 | MC Messages | Customers will soon be able to apply container labels to rosters in Microsoft Planner. This is enabled directly in Planner by using Microsoft Graph APIs. When this feature is rolled out, the roster sensitivity labels can be set to respect the policy settings. If the tenant admin has made container labels mandatory and has set a default label, then the default label will be used for roster creation through Microsoft Loop client.
On the Loop client, if the default label is provided, it will be used as the roster's lable when creating the roster. The roster system will not allow the user to create an unlabeled roster or to un-label a previously labeled roster. On the Microsoft Graph API, if a request is made and the label is not included, the request is rejected as the default label is not applied by the service. Users will need to ensure that a default label is provided when labels are mandatory so that roster creation does not fail. Note: The container sensitivity label applied to a roster applies only to the information in Microsoft Planner and does not protect or encrypt the information when it syncs with the Loop client. This message is associated with Microsoft 365 Roadmap ID 155837 [When this will happen:] We will begin rolling out in late August 2023 and is expected to complete by late September 2023. | Updated August 30, 2023: We have updated the rollout timeline below. Thank you for your patience.
Customers will soon be able to apply container labels to rosters in Microsoft Planner. This is enabled directly in Planner by using Microsoft Graph APIs. When this feature is rolled out, the roster sensitivity labels can be set to respect the policy settings. If the tenant admin has made container labels mandatory and has set a default label, then the default label will be used for roster creation through Microsoft Loop client. On the Loop client, if the default label is provided, it will be used as the roster's lable when creating the roster. The roster system will not allow the user to create an unlabeled roster or to un-label a previously labeled roster. On the Microsoft Graph API, if a request is made and the label is not included, the request is rejected as the default label is not applied by the service. Users will need to ensure that a default label is provided when labels are mandatory so that roster creation does not fail. Note: The container sensitivity label applied to a roster applies only to the information in Microsoft Planner and does not protect or encrypt the information when it syncs with the Loop client. This message is associated with Microsoft 365 Roadmap ID 155837 [When this will happen:] We will begin rolling out in mid-September 2023 (previously late August) and is expected to complete by mid-October 2023 (previously late September). < |
| 2023-08-31 | MC Title | Rosters in Microsoft Planner Supporting Container Sensitivity Labels | (Updated) Rosters in Microsoft Planner Supporting Container Sensitivity Labels |
| 2023-08-31 | MC Last Updated | 08/23/2023 00:53:45 | 2023-08-30T23:36:12Z |
| 2023-08-31 | MC MessageTagNames | New feature, Admin impact | Updated message, New feature, Admin impact |
*starting April 2022
Last updated 5 months ago
