Merge pull request #26008 from microsoftgraph/user/danlucui/add_teams_channel_container_type

add teamsChannel to plannerPlanContainer

Author: Danielabom

api-reference/beta/resources/enums.md

@@ -3423,6 +3423,7 @@ Possible values for user account types (group membership), per Windows definitio
 | project |
 | driveItem |
 | user |
+| teamsChannel|
 
 ### plannerPlanContextType values
 

api-reference/beta/resources/planner-overview.md

@@ -17,7 +17,7 @@ You can use the Planner API in Microsoft Graph to create tasks and assign them t
 Before you get started with the Planner API, it's helpful to understand how the main objects relate to each other and to Microsoft 365 groups.
 
 ## Plan containers
-In Microsoft Planner, plans are always contained in another resource. The containing resource, [plannerPlanContainer](plannerplancontainer.md), determines the authorization rules of the plan and all the tasks in it, and the lifecycle of the plan. You can create a plan in a container of one of the following types: [driveItem](driveitem.md), Microsoft 365 [group](group.md), Planner project, [roster](plannerroster.md), or [user](user.md).
+In Microsoft Planner, plans are always contained in another resource. The containing resource, [plannerPlanContainer](plannerplancontainer.md), determines the authorization rules of the plan and all the tasks in it, and the lifecycle of the plan. You can create a plan in a container of one of the following types: [driveItem](driveitem.md), Microsoft 365 [group](group.md), Planner project, [roster](plannerroster.md), [teamsChannel](channel.md), or [user](user.md).
 
 The most common type of container is a group.
 
@@ -35,8 +35,32 @@ GET /groups/{group-id}/planner/plans
 
 When you [create a new plan](../api/planner-post-plans.md), set the **container** property on a plan object to make a group its container. Plans must be contained by a supported resource.
 
->**Note:** The user who is creating the plan must be a member of the group that will contain the plan. When you create a new group by using [Create group](../api/group-post-groups.md), you are not added to the group as a member. After the group is created, add yourself as a member by using [group post members](../api/group-post-members.md).
+>**Note:** The user who creates the plan must be a member of the group that contains the plan. When you create a new group by using [Create group](../api/group-post-groups.md), you aren't added to the group as a member. After the group is created, add yourself as a member by using [group post members](../api/group-post-members.md).
 
+### Container type: Teams channel
+
+The `teamsChannel` container type supports plans created in shared channels in Teams, where the channel is the container for the plan. Plans that are pinned in shared channels are deleted when the channel is deleted.
+
+To [create a new plan](../api/planner-post-plans.md) in the container of a Teams channel, set the **container** property on a [plan](plannerplan.md) object with **type** as `teamsChannel`, and the ID should be formatted as "{team-id}/channels/{channel-id}".
+
+```json
+{
+    "container": {
+        "id": "{team-id}/channels/{channel-id}",
+        "type": "teamsChannel"
+    }
+}
+```
+
+Alternatively, you can specify the URL for a shared channel in Teams.
+
+```json
+{
+    "container": {
+        "url": "https://graph.microsoft.com/beta/teams/{team-id}/channels/{channel-id}"
+    }
+}
+```
 
 ### Container type: User
 

api-reference/beta/resources/plannerplancontainer.md

@@ -20,24 +20,25 @@ Planner currently supports the container types listed in the following table. Wh
 
 |Type|Description|Path to the resource|
 |----|-----------|--------------------|
+|driveItem| Plan is contained by a [driveItem](driveitem.md). | `https://graph.microsoft.com/beta/drives/<driveId>/items/<itemId>`|
 |group| Plan is contained by a [group](group.md).| `https://graph.microsoft.com/beta/groups/<id>` |
-|roster| Plan is contained by a [plannerRoster](plannerroster.md). | `https://graph.microsoft.com/beta/planner/rosters/<id>` |
 |project| Plan is contained by a Project from [Microsoft Project for the web](/project-for-the-web/projectforweb-admin-home). | Microsoft Project currently doesn't have a resource path on Microsoft Graph. Project details and members can be managed from [Microsoft Project](https://project.microsoft.com). |
-|driveItem| Plan is contained by a [driveItem](driveitem.md). | `https://graph.microsoft.com/beta/drives/<driveId>/items/<itemId>`|
+|roster| Plan is contained by a [plannerRoster](plannerroster.md). | `https://graph.microsoft.com/beta/planner/rosters/<id>` |
+|teamsChannel| Plan is contained by a Teams [channel](channel.md). | `https://graph.microsoft.com/beta/teams/<teamId>/channels/<channelId>` |
 |user| Plan is contained by a [User](user.md) | `https://graph.microsoft.com/beta/users/<id>` |
 
 ## Properties
 |Property|Type|Description|
 |:---|:---|:---|
 |containerId|String|The identifier of the resource that contains the plan. Optional.|
-|type|plannerContainerType|The type of the resource that contains the plan. For supported types, see the previous table. Possible values are: `group`, `unknownFutureValue`, `roster`, `project`, `driveItem`, and `user`. You must use the `Prefer: include-unknown-enum-members` request header to get the following value in this [evolvable enum](/graph/best-practices-concept#handling-future-members-in-evolvable-enumerations): `roster`, `project`, `driveItem`, and `user`. Optional.|
+|type|plannerContainerType|The type of the resource that contains the plan. For supported types, see the previous table. Possible values are: `group`, `unknownFutureValue`, `roster`, `project`, `driveItem`, `user`, and `teamsChannel` . You must use the `Prefer: include-unknown-enum-members` request header to get the following value in this [evolvable enum](/graph/best-practices-concept#handling-future-members-in-evolvable-enumerations): `roster`, `project`, `driveItem`,`user`, and,`teamsChannel`. Optional.|
 |url|String|The full canonical URL of the container. Optional.|
 
 ## Relationships
 None.
 
 ## JSON representation
-The following example displays a JSON representation of a plan container.
+The following JSON representation shows the resource type.
 
 <!-- {
   "blockType": "resource",
@@ -47,9 +48,9 @@ The following example displays a JSON representation of a plan container.
 ``` json
 {
   "@odata.type": "#microsoft.graph.plannerPlanContainer",
-  "url": "String",
   "containerId": "String",
-  "type": "String"
+  "type": "String",
+  "url": "String"
 }
 ```
 

changelog/Microsoft.Tasks.json

@@ -1,5 +1,23 @@
 {
   "changelog": [
+    {
+      "ChangeList": [
+        {
+          "Id": "ac461ffd-f78b-4889-a030-1477634802db",
+          "ApiChange": "Member",
+          "ChangedApiName": "teamsChannel",
+          "ChangeType": "Addition",
+          "Description": "Added the `teamsChannel` member to the **plannerContainerType** enumeration.",
+          "Target": "plannerContainerType"
+        }
+      ],
+      "Id": "ac461ffd-f78b-4889-a030-1477634802db",
+      "Cloud": "Prod",
+      "Version": "beta",
+      "CreatedDateTime": "2025-01-12T20:25:44.9502669Z",
+      "WorkloadArea": "Tasks and plans",
+      "SubArea": ""
+    },
     {
       "ChangeList": [
         {

concepts/whats-new-overview.md

@@ -42,6 +42,10 @@ The functionality also allows you to configure the default fallback option when
 
 Use the [start](/graph/api/industrydata-industrydatarun-start?view=graph-rest-beta&preserve-view=true) operation on the [industryDataRun](/graph/api/resources/industrydata-industrydatarun?view=graph-rest-beta&preserve-view=true) resource to perform an on-demand run, with throttling limits of up to five successful runs every 12 hours.
 
+### Tasks and plans
+
+Use the [teamsChannel](/graph/api/resources/planner-overview?view=graph-rest-beta&preserve-view=true#container-type-teams-channel) container type to create plans in shared channels in Microsoft Teams.
+
 ## December 2024: New and generally available
 
 ### Reports