Add teamsChannel to plannerContainerType enum

Author: Danielabom

api-reference/beta/resources/plannerplancontainer.md

@@ -31,7 +31,7 @@ Planner currently supports the container types listed in the following table. Wh
 |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