| Service | Microsoft Docs article | Related commit history on GitHub | Change details |
|---|---|---|---|
| v1.0 | Plannerplandetails Get | https://github.com/microsoftgraph/microsoft-graph-docs/commits/main/api-reference/beta/api/plannerplandetails-get.md | Content-type: application/json "category3": null, "category4": null, "category5": "Needs materials",- "category6": "Needs equipment" + "category6": "Needs equipment", + "category7": "Description of category 7", + "category8": "Description of category 8", + "category9": "Description of category 9", + "category10": "Description of category 10", + "category11": "Description of category 11", + "category12": "Description of category 12", + "category13": "Description of category 13", + "category14": "Description of category 14", + "category15": "Description of category 15", + "category16": "Description of category 16", + "category17": "Description of category 17", + "category18": "Description of category 18", + "category19": "Description of category 19", + "category20": "Description of category 20", + "category21": "Description of category 21", + "category22": "Description of category 22", + "category23": "Description of category 23", + "category24": "Description of category 24", + "category25": "Description of category 25" }, "id": "xqQg5FS2LkCp935s-FIFm2QAFkHM" } |
| v1.0 | Plannerplandetails Update | https://github.com/microsoftgraph/microsoft-graph-docs/commits/main/api-reference/beta/api/plannerplandetails-update.md | Content-type: application/json "category3": null, "category4": null, "category5": "Needs materials",- "category6": "Needs equipment" + "category6": "Needs equipment", + "category7": "Description of category 7", + "category8": "Description of category 8", + "category9": "Description of category 9", + "category10": "Description of category 10", + "category11": "Description of category 11", + "category12": "Description of category 12", + "category13": "Description of category 13", + "category14": "Description of category 14", + "category15": "Description of category 15", + "category16": "Description of category 16", + "category17": "Description of category 17", + "category18": "Description of category 18", + "category19": "Description of category 19", + "category20": "Description of category 20", + "category21": "Description of category 21", + "category22": "Description of category 22", + "category23": "Description of category 23", + "category24": "Description of category 24", + "category25": "Description of category 25" }, "id": "xqQg5FS2LkCp935s-FIFm2QAFkHM" } |
| v1.0 | Plannertask Get | https://github.com/microsoftgraph/microsoft-graph-docs/commits/main/api-reference/beta/api/plannertask-get.md | Content-type: application/json "orderHint": "RWk1" } },- "id":"01gzSlKkIUSUl6DF_EilrmQAKDhh" + "id":"01gzSlKkIUSUl6DF_EilrmQAKDhh", + "priority": 5 } ``` |
| v1.0 | User List Licensedetails | https://github.com/microsoftgraph/microsoft-graph-docs/commits/main/api-reference/beta/api/user-list-licensedetails.md | Namespace: microsoft.graph [!INCLUDE [beta-disclaimer](../../includes/beta-disclaimer.md)] -Retrieve a list of **licenseDetails** objects for enterprise users. +Retrieve a list of [licenseDetails](../resources/licensedetails.md) objects for enterprise users. This API returns details for licenses that are directly assigned and those transitively assigned through memberships in licensed groups. ## Permissions One of the following permissions is required to call this API. To learn more, including how to choose permissions, see [Permissions](/graph/permissions-reference). HTTP/1.1 200 OK Content-type: application/json {- "value": [ - { - "servicePlans": [ + "@odata.context": "https://graph.microsoft.com/beta/$metadata#users('071cc716-8147-4397-a5ba-b2105951cc0b')/assignedLicenses", + "value": [ {- "servicePlanId": "servicePlanId-value", - "servicePlanName": "servicePlanName-value", - "provisioningStatus": "provisioningStatus-value", - "appliesTo": "appliesTo-value" + "disabledPlans": [], + "skuId": "b05e124f-c7cc-45a0-a6aa-8cf78c946968" }- ], - "skuId": "skuId-value", - "skuPartNumber": "skuPartNumber-value", - "id": "id-value" - } - ] + ] } ``` |
| v1.0 | Chunkeduploadsessiondescriptor | https://github.com/microsoftgraph/microsoft-graph-docs/commits/main/api-reference/beta/resources/chunkeduploadsessiondescriptor.md | Title: "chunkedUploadSessionDescriptor resource type" -description: "Here is a JSON representation of the resource" +description: "chunkedUploadSessionDescriptor resource type" ms.localizationpriority: medium doc_type: resourcePageType Namespace: microsoft.graph ## JSON representation -Here is a JSON representation of the resource +Here is a JSON representation of the resource. <!-- { "blockType": "resource", |
| v1.0 | Cloudappsecuritystate | https://github.com/microsoftgraph/microsoft-graph-docs/commits/main/api-reference/beta/resources/cloudappsecuritystate.md | Title: "cloudAppSecurityState resource type" description: "Contains stateful information about the cloud application (destinationServiceName, destinationServiceIp)." ms.localizationpriority: medium doc_type: resourcePageType |
| v1.0 | Copystatusmodel | https://github.com/microsoftgraph/microsoft-graph-docs/commits/main/api-reference/beta/resources/copystatusmodel.md | Title: "copyStatusModel resource type" -description: "Here is a JSON representation of the resource." +description: "Here is a JSON representation of the copyStatusModel resource." ms.localizationpriority: medium doc_type: resourcePageType |
| v1.0 | Filehash | https://github.com/microsoftgraph/microsoft-graph-docs/commits/main/api-reference/beta/resources/filehash.md | Title: "fileHash resource type" description: "Contains stateful information about file hashes (cryptographic and location-sensitive)." ms.localizationpriority: medium doc_type: resourcePageType |
| v1.0 | Filehashtypeenumtype | https://github.com/microsoftgraph/microsoft-graph-docs/commits/main/api-reference/beta/resources/filehashtypeenumtype.md | Title: "fileHashType enum" description: "Enum for file hash types." ms.localizationpriority: medium doc_type: enumPageType |
| v1.0 | Filesecuritystate | https://github.com/microsoftgraph/microsoft-graph-docs/commits/main/api-reference/beta/resources/filesecuritystate.md | Title: "fileSecurityState resource type" description: " > **Important:** APIs under the /beta version in Microsoft Graph are in preview and are subject to change. Use of these APIs in production applications is not supported." ms.localizationpriority: medium doc_type: resourcePageType |
| v1.0 | Geolocationcolumn | https://github.com/microsoftgraph/microsoft-graph-docs/commits/main/api-reference/beta/resources/geolocationcolumn.md | Last updated 09/10/2018 Title: GeolocationColumn ms.localizationpriority: medium doc_type: resourcePageType # geolocationColumn resource type |
| v1.0 | Importstatusmodel | https://github.com/microsoftgraph/microsoft-graph-docs/commits/main/api-reference/beta/resources/importstatusmodel.md | Title: "importStatusModel resource type" -description: "Here is a JSON representation of the resource." +description: "Here is a JSON representation of the importStatusModel resource." ms.localizationpriority: medium doc_type: resourcePageType |
| v1.0 | Incompletedata | https://github.com/microsoftgraph/microsoft-graph-docs/commits/main/api-reference/beta/resources/incompletedata.md | Last updated 10/06/2017 Title: IncompleteData ms.localizationpriority: medium doc_type: resourcePageType # incompleteData resource type |
| v1.0 | Planner Overview | https://github.com/microsoftgraph/microsoft-graph-docs/commits/main/api-reference/beta/resources/planner-overview.md | 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 will be helpful to understand how the main objects relate to each other as well as to Microsoft 365 groups. ## Plan containers-In Planner, plans are always contained by another resource. The containing resource determines the authoization rules of the plan and all the tasks in it, as well as the lifecycle of the plan. For example, for plans contained by Microsoft 365 groups, +In Microsoft Planner, plans are always contained by another resource. The containing resource determines the authorization rules of the plan and all the tasks in it, as well as the lifecycle of the plan. For example, for plans contained by Microsoft 365 groups, group members will be able to create, edit, resolve, and delete tasks in the plan, as well as changing some plan-level properties, such as the name of the plan or label names. Additionally, when the group is deleted, all the plans in the group are automatically deleted, or if a group is restored, all the plans will be automatically restored. The most common type of container is a Microsoft 365 group. To [get the plans owned by a group](../api/plannergroup-list-plans.md), make the GET /groups/{group-id}/planner/plans ``` -When [creating a new plan](../api/planner-post-plans.md), make a group its container by setting the `container` property on a plan object. Plans must be contained by a supported resource. +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). ## Plans [Plans](plannerplan.md) are the containers of [tasks](plannertask.md).-To [create a task in a plan](../api/planner-post-tasks.md), set the `planId` property on the task object to the ID of the plan while creating the task. +To [create a task in a plan](../api/planner-post-tasks.md), set the **planId** property on the task object to the ID of the plan while creating the task. Tasks currently cannot be created without plans. To [retrieve the tasks in a plan](../api/plannerplan-list-tasks.md), make the following HTTP request. GET /planner/plans/{plan-id}/tasks ## Tasks Each task can be assigned to a user by adding an [assignment](plannerassignment.md) in the [assignments](plannerassignments.md) property on the task object.-The ID of the user to assign the task is the name of the open property on `assignments`, and the `orderHint` property on the assignment must be specified. +The ID of the user to assign the task is the name of the open property on **assignments**, and the **orderHint** property on the assignment must be specified. ## Task and plan details Aside from task and plan data, the Planner API also provides resources for creat | Tasks are shown as | Tasks are ordered with information from | | :- | : |-| Flat list (tasks in a plan) | `orderHint` property on tasks | -| Flat list (tasks assigned to a user) | `assigneePriority` property on tasks | +| Flat list (tasks in a plan) | **orderHint** property on tasks | +| Flat list (tasks assigned to a user) | **assigneePriority** property on tasks | | Board view with columns for assignees (assigned to task board) | [assignedToTaskBoardTaskFormat](plannerassignedtotaskboardtaskformat.md) object | | Board view with columns for progress of the task towards completion (progress task board) | [progressTaskBoardTaskFormat](plannerprogresstaskboardtaskformat.md) object | | Board view with custom columns of tasks (bucket task board): | [bucketTaskBoardTaskFormat](plannerbuckettaskboardtaskformat.md) object | -The custom columns in the bucket task board are represented by [bucket](plannerbucket.md) objects, and their order by `orderHint` property on the object. +The custom columns in the bucket task board are represented by [bucket](plannerbucket.md) objects, and their order by **orderHint** property on the object. All the ordering is controlled by the principles described in [Planner order hints](planner-order-hint-format.md). Users are subscribed to the following objects. | Planner resource type | Subscribed instances | | :-- | : |-| Tasks | <ul><li>Created by the user</li><li>Assigned to the user</li><li>Belong to a plan that the user owns</li><li>Contained in a plan shared with the user through the plan's **SharedWith** collection</li> | -| Plans | <ul><li>Shared with the user through the plan's **SharedWith** collection</li></ul> | -| Buckets | <ul><li>Contained in a plan shared with the user through the plan's **SharedWith** collection</li></ul> | +| **tasks** | <ul><li>Created by the user</li><li>Assigned to the user</li><li>Belong to a plan that the user owns</li><li>Contained in a plan shared with the user through the plan's **sharedWith** collection</li> | +| **plans** | <ul><li>Shared with the user through the plan's **sharedWith** collection</li></ul> | +| **buckets** | <ul><li>Contained in a plan shared with the user through the plan's **sharedWith** collection</li></ul> | ### <a name="objectcache">Populate the object cache for delta queries</a> In certain scenarios, the caller might want to distinguish between object creati These guidelines can be used to infer object creation: -* The `createdBy` property will only appear on newly created objects. -* A newly created `plannerTask` object will be followed by its corresponding `plannerTaskDetails` object. -* A newly created `plannerPlan` object will be followed by its corresponding `plannerPlanDetails` object. +* The **createdBy** property will only appear on newly created objects. +* A newly created **plannerTask** object will be followed by its corresponding **plannerTaskDetails** object. +* A newly created **plannerPlan** object will be followed by its corresponding **plannerPlanDetails** object. ### Usage The caller is expected to have a cache containing subscribed objects. For detail Planner's delta query call flow is as follows: -1. The caller initiates a delta sync query, obtaining a `@odata.nextLink` and an empty collection of changes. +1. The caller initiates a delta sync query, obtaining a `nextLink` and an empty collection of changes. 2. The caller must [populate the object cache for delta queries](#populate-the-object-cache-for-delta-queries) with objects that the user is subscribed to, updating its cache.-3. The caller follows the `@odata.nextLink` provided in the initial delta sync query to obtain a new `@odata.deltaLink` to any changes since previous step. +3. The caller follows the `nextLink` provided in the initial delta sync query to obtain a new `deltaLink` to any changes since previous step. 4. The caller applies the changes in the returned delta response to the objects in its cache.-5. The caller follows the new deltaLink to obtain the next deltaLink and changes since the current `@odata.deltaLink` was generated. +5. The caller follows the new `deltaLink` to obtain the next `deltaLink` and changes since the current `deltaLink` was generated. 6. The caller applies the changes (if any) and waits a short time before rerunning the previous step and this step. ## Planner resource versioning -Planner versions all resources using **etags**. These **etags** are returned with `@odata.etag` property on each resource. `PATCH` and `DELETE` requests require the last **etag** known by the client to be specified with a `If-Match` header. -Planner allows changes to older versions of resources, if the intended change does not conflict with newer changes accepted by the Planner service on the same resource. The clients can identify which **etag** for the same resource is newer by calculating which **etag** value is greater in ordinal string comparison. -Each resource has a unique **etag**. Etag values for different resources, including those with containment relationships, cannot be compared. -The client apps are expected to handle versioning related [error codes](/graph/errors) **409** and **412** by reading the latest version of the item and resolving the conflicting changes. +Planner versions all resources using etags. These etags are returned with **@odata.etag** property on each resource. `PATCH` and `DELETE` requests require the last etag known by the client to be specified with a `If-Match` header. +Planner allows changes to older versions of resources, if the intended change does not conflict with newer changes accepted by the Planner service on the same resource. The clients can identify which etag for the same resource is newer by calculating which etag value is greater in ordinal string comparison. +Each resource has a unique etag. Etag values for different resources, including those with containment relationships, cannot be compared. +The client apps are expected to handle versioning related [error codes](/graph/errors) `409` and `412` by reading the latest version of the item and resolving the conflicting changes. ## Common Planner error conditions In addition to [general errors](/graph/errors) that apply to Microsoft Graph, so In some common scenarios, `POST` and `PATCH` requests can return a 400 status code. The following are some of the common causes: -* Open Type properties are not of correct types, or the type isn't specified, or they do not contain any properties. For example, [plannerAssignments](plannerassignments.md) properties with complex values need to declare `@odata.type` property with value `microsoft.graph.plannerAssignment`. +* Open Type properties are not of correct types, or the type isn't specified, or they do not contain any properties. For example, [plannerAssignments](plannerassignments.md) properties with complex values need to declare **@odata.type** property with value `microsoft.graph.plannerAssignment`. * Order hint values do not have the [correct format](planner-order-hint-format.md). For example, an order hint value is being set directly to the value returned to the client. * The data is logically inconsistent. For example, start date of task is later than due date of the task. ### 403 Forbidden -In addition to the general errors, the Planner API also returns the 403 status code when a service-defined limit has been exceeded. If this is the case, the `code` property on the error resource type will indicate the type of the limit exceeded by the request. +In addition to the general errors, the Planner API also returns the `403` status code when a service-defined limit has been exceeded. If this is the case, the **code** property on the error resource type will indicate the type of the limit exceeded by the request. The following are the possible values for the limit types. | Value | Description | | :- | :- |-| MaximumProjectsOwnedByUser | The maximum number of Plans owned by a group limit has been exceeded. This limit is based on the `owner` property on the [plannerPlan](plannerplan.md) resource. | -| MaximumProjectsSharedWithUser | The maximum number of Plans shared with a user limit has been exceeded. This limit is based on the `sharedWith` property on the [plannerPlanDetails](plannerplandetails.md) resource. | -| MaximumTasksCreatedByUser | The maximum number of Tasks created by a user limit has been exceeded. This limit is based on the `createdBy` property on the [plannerTask](plannertask.md) resource. | -| MaximumTasksAssignedToUser | The maximum number of Tasks assigned to a user limit has been exceeded. This limit is based on the `assignments` property on the [plannerTask](plannertask.md) resource. | -| MaximumTasksInProject | The maximum number of Tasks in a Plan limit has been exceeded. This limit is based on the `planId` property on the [plannerTask](plannertask.md) resource. | -| MaximumActiveTasksInProject | The maximum number of Tasks that aren't completed in a Plan limit has been exceeded. This limit is based on the `planId` and `percentComplete` properties on the [plannerTask](plannertask.md) resource. | -| MaximumBucketsInProject | The maximum number of Buckets in a Plan limit has been exceeded. This limit is based on the `planId` property on the [plannerBucket](plannerbucket.md) resource. | -| MaximumUsersSharedWithProject | The `sharedWith` property on the [plannerPlanDetails](plannerplandetails.md) resource contains too many values. | -| MaximumReferencesOnTask | The `references` property on the [plannerTaskDetails](plannertaskdetails.md) resource contains too many values. | -| MaximumChecklistItemsOnTask | The `checklist` property on the [plannerTaskDetails](plannertaskdetails.md) resource contains too many values. | -| MaximumAssigneesInTasks | The `assignments` property on the [plannerTask](plannertask.md) resource contains too many values. | -| MaximumFavoritePlansForUser | The `favoritePlanReferences` property on the [plannerUser](planneruser.md) resource contains too many values. | -| MaximumRecentPlansForUser | The `recentPlanReferences` property on the [plannerUser](planneruser.md) resource contains too many values. | -| MaximumContextsOnPlan | The `contexts` property on the [plannerPlan](plannerplan.md) resource contains too many values. | -| MaximumPlannerPlans | The group already contains a Plan. Currently, groups can only contain one Plan. **Note:** Some Microsoft apps can exceed this limit. In the future, we will extend this capability to all apps. | +| MaximumProjectsOwnedByUser | The maximum number of plans contained by a group limit has been exceeded. This limit applies to plans contained by a group based on the **container** property of the [plannerPlan](plannerplan.md) resource. | +| MaximumProjectsSharedWithUser | The maximum number of plans shared with a user limit has been exceeded. This limit is based on the **sharedWith** property on the [plannerPlanDetails](plannerplandetails.md) resource. | +| MaximumTasksCreatedByUser | The maximum number of tasks created by a user limit has been exceeded. This limit is based on the **createdBy** property on the [plannerTask](plannertask.md) resource. | +| MaximumTasksAssignedToUser | The maximum number of tasks assigned to a user limit has been exceeded. This limit is based on the **assignments** property on the [plannerTask](plannertask.md) resource. | +| MaximumTasksInProject | The maximum number of tasks in a plan limit has been exceeded. This limit is based on the **planId** property on the [plannerTask](plannertask.md) resource. | +| MaximumActiveTasksInProject | The maximum number of tasks that aren't completed in a plan limit has been exceeded. This limit is based on the **planId** and **percentComplete** properties on the [plannerTask](plannertask.md) resource. | +| MaximumBucketsInProject | The maximum number of buckets in a plan limit has been exceeded. This limit is based on the **planId** property on the [plannerBucket](plannerbucket.md) resource. | +| MaximumUsersSharedWithProject | The **sharedWith** property on the [plannerPlanDetails](plannerplandetails.md) resource contains too many values. | +| MaximumReferencesOnTask | The **references** property on the [plannerTaskDetails](plannertaskdetails.md) resource contains too many values. | +| MaximumChecklistItemsOnTask | The **checklist** property on the [plannerTaskDetails](plannertaskdetails.md) resource contains too many values. | +| MaximumAssigneesInTasks | The **assignments** property on the [plannerTask](plannertask.md) resource contains too many values. | +| MaximumFavoritePlansForUser | The **favoritePlanReferences** property on the [plannerUser](planneruser.md) resource contains too many values. | +| MaximumRecentPlansForUser | The **recentPlanReferences** property on the [plannerUser](planneruser.md) resource contains too many values. | +| MaximumContextsOnPlan | The **contexts** property on the [plannerPlan](plannerplan.md) resource contains too many values. | +| MaximumPlannerPlans | The group already contains a **plan**. Currently, groups can only contain one **plan**. **Note:** Some Microsoft apps can exceed this limit. In the future, we will extend this capability to all apps. | ### 412 Precondition Failed -All Planer API `POST`, `PATCH`, and `DELETE` requests require the `If-Match` header to be specified with the last known etag value of the resource that is subject to the request. +All Planner API `POST`, `PATCH`, and `DELETE` requests require the `If-Match` header to be specified with the last known etag value of the resource that is subject to the request. The 412 status code can also be returned if the etag value specified in the request no longer matches a version of the resource in the service. In this case, the clients should read the resource again and get a new etag. ## What's new |
| v1.0 | Subscription | https://github.com/microsoftgraph/microsoft-graph-docs/commits/main/api-reference/beta/resources/subscription.md | A subscription allows a client app to receive change notifications about changes - A [baseTask][] of a user in Microsoft To Do.* - A [user][] in Azure Active Directory. -For the possible resource path values for each supported resource and to learn how resources use lifecycle notifications, see [Use the Microsoft Graph API to get change notifications](webhooks.md). +For the possible resource path values for each supported resource, see [Use the Microsoft Graph API to get change notifications](webhooks.md). To learn how to use lifecycle notifications, see [Reduce missing subscriptions and change notifications](/graph/webhooks-lifecycle). ## Methods |
| v1.0 | Plannerplan Get | https://github.com/microsoftgraph/microsoft-graph-docs/commits/main/api-reference/v1.0/api/plannerplan-get.md | Content-type: application/json } }, "createdDateTime": "2015-03-30T18:36:49.2407981Z",- "owner": "ebf3b108-5234-4e22-b93d-656d7dae5874", + "container": { + "@odata.type": "microsoft.graph.plannerPlanContainer", + "url": "https://graph.microsoft.com/v1.0/groups/ebf3b108-5234-4e22-b93d-656d7dae5874", + "containerId": "ebf3b108-5234-4e22-b93d-656d7dae5874", + "type": "group" + }, "title": "title-value", "id": "xqQg5FS2LkCp935s-FIFm2QAFkHM" } |
| v1.0 | Plannerplan Update | https://github.com/microsoftgraph/microsoft-graph-docs/commits/main/api-reference/v1.0/api/plannerplan-update.md | Content-type: application/json } }, "createdDateTime": "2015-03-30T18:36:49.2407981Z",- "owner": "ebf3b108-5234-4e22-b93d-656d7dae5874", + "container": { + "@odata.type": "microsoft.graph.plannerPlanContainer", + "url": "https://graph.microsoft.com/v1.0/groups/ebf3b108-5234-4e22-b93d-656d7dae5874", + "containerId": "ebf3b108-5234-4e22-b93d-656d7dae5874", + "type": "group" + }, "title": "title-value", "id": "xqQg5FS2LkCp935s-FIFm2QAFkHM" } |
| v1.0 | Plannerplandetails Get | https://github.com/microsoftgraph/microsoft-graph-docs/commits/main/api-reference/v1.0/api/plannerplandetails-get.md | Content-type: application/json "category3": null, "category4": null, "category5": "Needs materials",- "category6": "Needs equipment" + "category6": "Needs equipment", + "category7": "Description of category 7", + "category8": "Description of category 8", + "category9": "Description of category 9", + "category10": "Description of category 10", + "category11": "Description of category 11", + "category12": "Description of category 12", + "category13": "Description of category 13", + "category14": "Description of category 14", + "category15": "Description of category 15", + "category16": "Description of category 16", + "category17": "Description of category 17", + "category18": "Description of category 18", + "category19": "Description of category 19", + "category20": "Description of category 20", + "category21": "Description of category 21", + "category22": "Description of category 22", + "category23": "Description of category 23", + "category24": "Description of category 24", + "category25": "Description of category 25" }, "id": "xqQg5FS2LkCp935s-FIFm2QAFkHM" } |
| v1.0 | Plannerplandetails Update | https://github.com/microsoftgraph/microsoft-graph-docs/commits/main/api-reference/v1.0/api/plannerplandetails-update.md | Content-type: application/json "category3": null, "category4": null, "category5": "Needs materials",- "category6": "Needs equipment" + "category6": "Needs equipment", + "category7": "Description of category 7", + "category8": "Description of category 8", + "category9": "Description of category 9", + "category10": "Description of category 10", + "category11": "Description of category 11", + "category12": "Description of category 12", + "category13": "Description of category 13", + "category14": "Description of category 14", + "category15": "Description of category 15", + "category16": "Description of category 16", + "category17": "Description of category 17", + "category18": "Description of category 18", + "category19": "Description of category 19", + "category20": "Description of category 20", + "category21": "Description of category 21", + "category22": "Description of category 22", + "category23": "Description of category 23", + "category24": "Description of category 24", + "category25": "Description of category 25" }, "id": "xqQg5FS2LkCp935s-FIFm2QAFkHM" } |
| v1.0 | Plannertask Get | https://github.com/microsoftgraph/microsoft-graph-docs/commits/main/api-reference/v1.0/api/plannertask-get.md | Content-type: application/json "orderHint": "RWk1" } },- "id":"01gzSlKkIUSUl6DF_EilrmQAKDhh" + "id":"01gzSlKkIUSUl6DF_EilrmQAKDhh", + "priority": 5 } ``` |
| v1.0 | Plannertask Update | https://github.com/microsoftgraph/microsoft-graph-docs/commits/main/api-reference/v1.0/api/plannertask-update.md | Title: "Update plannertask" -description: "Update the properties of **plannertask** object." + Title: "Update plannerTask" +description: "Update the properties of **plannerTask** object." ms.localizationpriority: medium ms.prod: "planner" doc_type: apiPageType -# Update plannertask +# Update plannerTask Namespace: microsoft.graph -Update the properties of **plannertask** object. +Update the properties of **plannerTask** object. ## Permissions One of the following permissions is required to call this API. To learn more, including how to choose permissions, see [Permissions](/graph/permissions-reference). In the request body, supply the values for relevant fields that should be update |conversationThreadId|String|Thread id of the conversation on the task. This is the id of the conversation thread object created in the group.| |dueDateTime|DateTimeOffset|Date and time at which the task is due. The Timestamp type represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is `2014-01-01T00:00:00Z`| |orderHint|String|Hint used to order items of this type in a list view. The format is defined in [Using order hints in Planner](../resources/planner-order-hint-format.md).|+|priority|Int32|Priority of the task. The valid range of values is between `0` and `10`, with the increasing value being lower priority (`0` has the highest priority and `10` has the lowest priority). Currently, Planner interprets values `0` and `1` as "urgent", `2`, `3` and `4` as "important", `5`, `6`, and `7` as "medium", and `8`, `9`, and `10` as "low". Additionally, Planner sets the value `1` for "urgent", `3` for "important", `5` for "medium", and `9` for "low".| |percentComplete|Int32|Percentage of task completion. When set to `100`, the task is considered completed. | |startDateTime|DateTimeOffset|Date and time at which the task starts. The Timestamp type represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is `2014-01-01T00:00:00Z`| |title|String|Title of the task.| Content-type: application/json "category5": true, "category6": true, },- "id":"01gzSlKkIUSUl6DF_EilrmQAKDhh" + "id":"01gzSlKkIUSUl6DF_EilrmQAKDhh", + "priority": 5 } ``` |
| v1.0 | User List Licensedetails | https://github.com/microsoftgraph/microsoft-graph-docs/commits/main/api-reference/v1.0/api/user-list-licensedetails.md | doc_type: apiPageType Namespace: microsoft.graph -Retrieve a list of **licenseDetails** objects for enterprise users. +Retrieve a list of [licenseDetails](../resources/licensedetails.md) objects for enterprise users. This API returns details for licenses that are directly assigned and those transitively assigned through memberships in licensed groups. + ## Permissions One of the following permissions is required to call this API. To learn more, including how to choose permissions, see [Permissions](/graph/permissions-reference). HTTP/1.1 200 OK Content-type: application/json {- "value": [ - { - "servicePlans": [ + "@odata.context": "https://graph.microsoft.com/v1.0/$metadata#users('071cc716-8147-4397-a5ba-b2105951cc0b')/assignedLicenses", + "value": [ {- "servicePlanId": "servicePlanId-value", - "servicePlanName": "servicePlanName-value", - "provisioningStatus": "provisioningStatus-value", - "appliesTo": "appliesTo-value" + "disabledPlans": [], + "skuId": "b05e124f-c7cc-45a0-a6aa-8cf78c946968" }- ], - "skuId": "skuId-value", - "skuPartNumber": "skuPartNumber-value", - "id": "id-value" - } - ] + ] } ``` |
| v1.0 | Enums | https://github.com/microsoftgraph/microsoft-graph-docs/commits/main/api-reference/v1.0/resources/enums.md | Namespace: microsoft.graph | radio +### plannerContainerType values ++|Member| +|:| +|group| +|unknownFutureValue| +|roster| ++ ### plannerPreviewType values | Member |
| v1.0 | Planner Overview | https://github.com/microsoftgraph/microsoft-graph-docs/commits/main/api-reference/v1.0/resources/planner-overview.md | doc_type: conceptualPageType You can use the Planner API in Microsoft Graph to create tasks and assign them to users in a group in Microsoft 365. -Before you get started with Planner API, you will want to understand how the main objects relate to each other as well as to Microsoft 365 groups. +Before you get started with the Planner API, it will be helpful to understand how the main objects relate to each other as well as to Microsoft 365 groups. -## Microsoft 365 groups +## Plan containers +In Microsoft Planner, plans are always contained by another resource. The containing resource determines the authorization rules of the plan and all the tasks in it, as well as the lifecycle of the plan. For example, for plans contained by Microsoft 365 groups, +group members will be able to create, edit, resolve, and delete tasks in the plan, as well as changing some plan-level properties, such as the name of the plan or label names. Additionally, when the group is deleted, all the plans in the group are automatically deleted, or if a group is restored, all the plans will be automatically restored. -Microsoft 365 groups are the owners of the plans in the Planner API. +The most common type of container is a Microsoft 365 group. ++### Container type: Microsoft 365 groups ++Plans are commonly contained in Microsoft 365 groups in the Planner API. To [get the plans owned by a group](../api/plannergroup-list-plans.md), make the following HTTP request. ``` http GET /groups/{group-id}/planner/plans ``` -When [creating a new plan](../api/planner-post-plans.md), make a group its owner by setting the `owner` property on a plan object. Plans must be owned by groups. +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 own 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 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). ## Plans -[Plans](plannerplan.md) are the containers of [tasks](plannertask.md). -To [create a task in a plan](../api/planner-post-tasks.md), set the `planId` property on the task object to the ID of the plan while creating the task. +[Plans](plannerplan.md) are the containers of [tasks](plannertask.md). +To [create a task in a plan](../api/planner-post-tasks.md), set the **planId** property on the task object to the ID of the plan while creating the task. Tasks currently cannot be created without plans. To [retrieve the tasks in a plan](../api/plannerplan-list-tasks.md), make the following HTTP request. GET /planner/plans/{plan-id}/tasks ## Tasks Each task can be assigned to a user by adding an [assignment](plannerassignment.md) in the [assignments](plannerassignments.md) property on the task object.-The ID of the user to assign the task is the name of the open property on `assignments`, and the `orderHint` property on the assignment must be specified. +The ID of the user to assign the task is the name of the open property on **assignments**, and the **orderHint** property on the assignment must be specified. ## Task and plan details Aside from task and plan data, the Planner API also provides resources for creat | Tasks are shown as | Tasks are ordered with information from | | :- | : |-| Flat list (tasks in a plan) | `orderHint` property on tasks | -| Flat list (tasks assigned to a user) | `assigneePriority` property on tasks | +| Flat list (tasks in a plan) | **orderHint** property on tasks | +| Flat list (tasks assigned to a user) | **assigneePriority** property on tasks | | Board view with columns for assignees (assigned to task board) | [assignedToTaskBoardTaskFormat](plannerassignedtotaskboardtaskformat.md) object | | Board view with columns for progress of the task towards completion (progress task board) | [progressTaskBoardTaskFormat](plannerprogresstaskboardtaskformat.md) object | | Board view with custom columns of tasks (bucket task board): | [bucketTaskBoardTaskFormat](plannerbuckettaskboardtaskformat.md) object | -The custom columns in the bucket task board are represented by [bucket](plannerbucket.md) objects, and their order by `orderHint` property on the object. +The custom columns in the bucket task board are represented by [bucket](plannerbucket.md) objects, and their order by **orderHint** property on the object. All the ordering is controlled by the principles described in [Planner order hints](planner-order-hint-format.md). ## Planner resource versioning -Planner versions all resources using **etags**. These **etags** are returned with `@odata.etag` property on each resource. `PATCH` and `DELETE` requests require the last **etag** known by the client to be specified with a `If-Match` header. -Planner allows changes to older versions of resources, if the intended change does not conflict with newer changes accepted by the Planner service on the same resource. The clients can identify which **etag** for the same resource is newer by calculating which **etag** value is greater in ordinal string comparison. -Each resource has a unique **etag**. Etag values for different resources, including those with containment relationships, cannot be compared. -The client apps are expected to handle versioning related [error codes](/graph/errors) **409** and **412** by reading the latest version of the item and resolving the conflicting changes. +Planner versions all resources using etags. These etags are returned with **@odata.etag** property on each resource. `PATCH` and `DELETE` requests require the last etag known by the client to be specified with a `If-Match` header. +Planner allows changes to older versions of resources, if the intended change does not conflict with newer changes accepted by the Planner service on the same resource. The clients can identify which etag for the same resource is newer by calculating which etag value is greater in ordinal string comparison. +Each resource has a unique etag. Etag values for different resources, including those with containment relationships, cannot be compared. +The client apps are expected to handle versioning related [error codes](/graph/errors) `409` and `412` by reading the latest version of the item and resolving the conflicting changes. ## Common Planner error conditions In addition to [general errors](/graph/errors) that apply to Microsoft Graph, so In some common scenarios, `POST` and `PATCH` requests can return a 400 status code. The following are some of the common causes: -* Open Type properties are not of correct types, or the type isn't specified, or they do not contain any properties. For example, [plannerAssignments](plannerassignments.md) properties with complex values need to declare `@odata.type` property with value `microsoft.graph.plannerAssignment`. +* Open Type properties are not of correct types, or the type isn't specified, or they do not contain any properties. For example, [plannerAssignments](plannerassignments.md) properties with complex values need to declare **@odata.type** property with value `microsoft.graph.plannerAssignment`. * Order hint values do not have the [correct format](planner-order-hint-format.md). For example, an order hint value is being set directly to the value returned to the client. * The data is logically inconsistent. For example, start date of task is later than due date of the task. ### 403 Forbidden -In addition to the general errors, the Planner API also returns the 403 status code when a service-defined limit has been exceeded. If this is the case, the `code` property on the error resource type will indicate the type of the limit exceeded by the request. +In addition to the general errors, the Planner API also returns the `403` status code when a service-defined limit has been exceeded. If this is the case, the **code** property on the error resource type will indicate the type of the limit exceeded by the request. The following are the possible values for the limit types. | Value | Description | | :- | :- |-| MaximumProjectsOwnedByUser | The maximum number of Plans owned by a group limit has been exceeded. This limit is based on the `owner` property on the [plannerPlan](plannerplan.md) resource. | -| MaximumProjectsSharedWithUser | The maximum number of Plans shared with a user limit has been exceeded. This limit is based on the `sharedWith` property on the [plannerPlanDetails](plannerplandetails.md) resource. | -| MaximumTasksCreatedByUser | The maximum number of Tasks created by a user limit has been exceeded. This limit is based on the `createdBy` property on the [plannerTask](plannertask.md) resource. | -| MaximumTasksAssignedToUser | The maximum number of Tasks assigned to a user limit has been exceeded. This limit is based on the `assignments` property on the [plannerTask](plannertask.md) resource. | -| MaximumTasksInProject | The maximum number of Tasks in a Plan limit has been exceeded. This limit is based on the `planId` property on the [plannerTask](plannertask.md) resource. | -| MaximumActiveTasksInProject | The maximum number of Tasks that aren't completed in a Plan limit has been exceeded. This limit is based on the `planId` and `percentComplete` properties on the [plannerTask](plannertask.md) resource. | -| MaximumBucketsInProject | The maximum number of Buckets in a Plan limit has been exceeded. This limit is based on the `planId` property on the [plannerBucket](plannerbucket.md) resource. | -| MaximumUsersSharedWithProject | The `sharedWith` property on the [plannerPlanDetails](plannerplandetails.md) resource contains too many values. | -| MaximumReferencesOnTask | The `references` property on the [plannerTaskDetails](plannertaskdetails.md) resource contains too many values. | -| MaximumChecklistItemsOnTask | The `checklist` property on the [plannerTaskDetails](plannertaskdetails.md) resource contains too many values. | -| MaximumAssigneesInTasks | The `assignments` property on the [plannerTask](plannertask.md) resource contains too many values. | -| MaximumPlannerPlans | The group already contains a Plan. Currently, groups can only contain one Plan. **Note:** Some Microsoft apps can exceed this limit. In the future, we will extend this capability to all apps. | +| MaximumProjectsOwnedByUser | The maximum number of plans contained by a group limit has been exceeded. This limit applies to plans contained by a group based on the **container** property of the [plannerPlan](plannerplan.md) resource. | +| MaximumProjectsSharedWithUser | The maximum number of plans shared with a user limit has been exceeded. This limit is based on the **sharedWith** property on the [plannerPlanDetails](plannerplandetails.md) resource. | +| MaximumTasksCreatedByUser | The maximum number of tasks created by a user limit has been exceeded. This limit is based on the **createdBy** property on the [plannerTask](plannertask.md) resource. | +| MaximumTasksAssignedToUser | The maximum number of tasks assigned to a user limit has been exceeded. This limit is based on the **assignments** property on the [plannerTask](plannertask.md) resource. | +| MaximumTasksInProject | The maximum number of tasks in a plan limit has been exceeded. This limit is based on the **planId** property on the [plannerTask](plannertask.md) resource. | +| MaximumActiveTasksInProject | The maximum number of tasks that aren't completed in a plan limit has been exceeded. This limit is based on the **planId** and **percentComplete** properties on the [plannerTask](plannertask.md) resource. | +| MaximumBucketsInProject | The maximum number of buckets in a plan limit has been exceeded. This limit is based on the **planId** property on the [plannerBucket](plannerbucket.md) resource. | +| MaximumUsersSharedWithProject | The **sharedWith** property on the [plannerPlanDetails](plannerplandetails.md) resource contains too many values. | +| MaximumReferencesOnTask | The **references** property on the [plannerTaskDetails](plannertaskdetails.md) resource contains too many values. | +| MaximumChecklistItemsOnTask | The **checklist** property on the [plannerTaskDetails](plannertaskdetails.md) resource contains too many values. | +| MaximumAssigneesInTasks | The **assignments** property on the [plannerTask](plannertask.md) resource contains too many values. | +| MaximumPlannerPlans | The group already contains a **plan**. Currently, groups can only contain one **plan**. **Note:** Some Microsoft apps can exceed this limit. In the future, we will extend this capability to all apps. | ### 412 Precondition Failed -All Planer API `POST`, `PATCH`, and `DELETE` requests require the `If-Match` header to be specified with the last known etag value of the resource that is subject to the request. +All Planner API `POST`, `PATCH`, and `DELETE` requests require the `If-Match` header to be specified with the last known etag value of the resource that is subject to the request. The 412 status code can also be returned if the etag value specified in the request no longer matches a version of the resource in the service. In this case, the clients should read the resource again and get a new etag. ## What's new Find out about the [latest new features and updates](/graph/whats-new-overview) for this API set. - |
| v1.0 | Plannercategorydescriptions | https://github.com/microsoftgraph/microsoft-graph-docs/commits/main/api-reference/v1.0/resources/plannercategorydescriptions.md | Title: "plannerCategoryDescriptions resource type" -description: "The **plannerCategoryDescriptions** resource represents the descriptive labels for the categories that have been defined for a plan. It belongs to the plan details object. There can be up to 6 categories defined. " +description: "Represents the descriptive labels for the categories that have been defined for a plan. It belongs to the plan details object. There can be up to 25 categories defined. " ms.localizationpriority: medium ms.prod: "planner" doc_type: resourcePageType Namespace: microsoft.graph -The **plannerCategoryDescriptions** resource represents the descriptive labels for the categories that have been defined for a plan. It belongs to the [plan details](plannerplandetails.md) object. There can be up to 6 categories defined. +Represents the descriptive labels for the categories that have been defined for a plan. It belongs to the [plan details](plannerplandetails.md) object. There can be up to 25 categories defined. ## Properties The **plannerCategoryDescriptions** resource represents the descriptive labels f |category4|String|The label associated with Category 4| |category5|String|The label associated with Category 5| |category6|String|The label associated with Category 6|+|category7|String|The label associated with Category 7| +|category8|String|The label associated with Category 8| +|category9|String|The label associated with Category 9| +|category10|String|The label associated with Category 10| +|category11|String|The label associated with Category 11| +|category12|String|The label associated with Category 12| +|category13|String|The label associated with Category 13| +|category14|String|The label associated with Category 14| +|category15|String|The label associated with Category 15| +|category16|String|The label associated with Category 16| +|category17|String|The label associated with Category 17| +|category18|String|The label associated with Category 18| +|category19|String|The label associated with Category 19| +|category20|String|The label associated with Category 20| +|category21|String|The label associated with Category 21| +|category22|String|The label associated with Category 22| +|category23|String|The label associated with Category 23| +|category24|String|The label associated with Category 24| +|category25|String|The label associated with Category 25| ## JSON representation-Here is a JSON representation of the resource. +The following is a JSON representation of the resource. <!-- { "blockType": "resource", Here is a JSON representation of the resource. ```json {+ "@odata.type": "#microsoft.graph.plannerCategoryDescriptions", "category1": "String", "category2": "String", "category3": "String", "category4": "String", "category5": "String",- "category6": "String" + "category6": "String", + "category7": "String", + "category8": "String", + "category9": "String", + "category10": "String", + "category11": "String", + "category12": "String", + "category13": "String", + "category14": "String", + "category15": "String", + "category16": "String", + "category17": "String", + "category18": "String", + "category19": "String", + "category20": "String", + "category21": "String", + "category22": "String", + "category23": "String", + "category24": "String", + "category25": "String" }- ``` <!-- uuid: 8fcb5dbc-d5aa-4681-8e31-b001d5168d79 |
| v1.0 | Plannerplan | https://github.com/microsoftgraph/microsoft-graph-docs/commits/main/api-reference/v1.0/resources/plannerplan.md | The **plannerPlan** resource represents a plan in Microsoft 365. A plan can be o ## Properties | Property | Type |Description| |:|:--|:-|+|container|[plannerPlanContainer](../resources/plannerplancontainer.md)|Identifies the container of the plan. After it is set, this property canΓÇÖt be updated. Required.| +|createdBy|[identitySet](identityset.md)|Read-only. The user who created the plan.| |createdDateTime|DateTimeOffset|Read-only. Date and time at which the plan is created. The Timestamp type represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is `2014-01-01T00:00:00Z`| |id|String| Read-only. ID of the plan. It is 28 characters long and case-sensitive. [Format validation](planner-identifiers-disclaimer.md) is done on the service.|-|owner|String|ID of the [Group](group.md) that owns the plan. A valid group must exist before this field can be set. After it is set, this property canΓÇÖt be updated.| |title|String|Required. Title of the plan.|-|createdBy|[identitySet](identityset.md)|Read-only. The user who created the plan.| +|owner (deprecated) |String| Use the **container** property instead. ID of the [group](group.md) that owns the plan. After it is set, this property canΓÇÖt be updated. This property will not return a valid group ID if the container of the plan is not a group.| ## Relationships | Relationship | Type |Description| Here is a JSON representation of the resource. ```json {+ "container": { + "@odata.type": "microsoft.graph.plannerPlanContainer", + "containerId": "String", + "type": "String", + "url": "String" + }, "createdBy": {"@odata.type": "microsoft.graph.identitySet"}, "createdDateTime": "String (timestamp)", "id": "String (identifier)",- "owner": "String", "title": "String" } ``` |
| v1.0 | Plannerplancontainer | https://github.com/microsoftgraph/microsoft-graph-docs/commits/main/api-reference/v1.0/resources/plannerplancontainer.md | + + Title: "plannerPlanContainer resource type" +description: "Represents a container for a plannerPlan. The container is a resource that specifies authorization rules and the lifetime of the plan." ++ms.localizationpriority: high +++# plannerPlanContainer resource type ++Namespace: microsoft.graph ++Represents a container for a [plannerPlan](plannerplan.md). The container is a resource that specifies authorization rules and the lifetime of the plan. This means that only the people who are authorized to work with the resource containing the plan will be able to work with the plan and the tasks within it. When the containing resource is deleted, the contained plans are also deleted. The properties of the **plannerPlanContainer** cannot be changed after the plan is created. ++Microsoft Planner currently supports the container types listed in the following table. When you create a plan, you must specify the **containerUrl** property with the path of the resource identified in the following table. ++|Type|Description|Path to the resource| +|-|--|--| +|group| Plan is contained by a [group](group.md).| https://graph.microsoft.com/v1.0/groups/{id}| +|roster| Plan is contained by a **plannerRoster** | https://graph.microsoft.com/beta/planner/rosters/{id}. **plannerRosters** are currently only accessible using the beta version.| ++## Properties +|Property|Type|Description| +|:|:|:| +|containerId|String|The identifier of the resource that contains the plan.| +|type|plannerContainerType| The type of the resource that contains the plan. For supported types, see the previous table. Possible values are: `group`, `unknownFutureValue`, `roster`. Note that 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`.| +|url|String|The full canonical URL of the container.| ++## Relationships +None. ++## JSON representation +The following is a JSON representation of the resource. +<!-- { + "blockType": "resource", + "@odata.type": "microsoft.graph.plannerPlanContainer" +} +--> +``` json +{ + "@odata.type": "#microsoft.graph.plannerPlanContainer", + "containerId": "String", + "type": "String", + "url": "String" +} +``` + |
| v1.0 | Plannerplandetails | https://github.com/microsoftgraph/microsoft-graph-docs/commits/main/api-reference/v1.0/resources/plannerplandetails.md | The **plannerPlanDetails** resource represents the additional information about ## Properties | Property | Type |Description| |:|:--|:-|-|categoryDescriptions|[plannerCategoryDescriptions](plannercategorydescriptions.md)|An object that specifies the descriptions of the six categories that can be associated with tasks in the plan| +|categoryDescriptions|[plannerCategoryDescriptions](plannercategorydescriptions.md)|An object that specifies the descriptions of the 25 categories that can be associated with tasks in the plan.| |id|String| Read-only. ID of the plan details. It is 28 characters long and case-sensitive. [Format validation](planner-identifiers-disclaimer.md) is done on the service.| |sharedWith|[plannerUserIds](planneruserids.md)|Set of user ids that this plan is shared with. If you are leveraging Microsoft 365 groups, use the Groups API to manage group membership to share the [group's](group.md) plan. You can also add existing members of the group to this collection though it is not required for them to access the plan owned by the group. | |
| v1.0 | Plannertask | https://github.com/microsoftgraph/microsoft-graph-docs/commits/main/api-reference/v1.0/resources/plannertask.md | The **plannerTask** resource represents a Planner task in Microsoft 365. A Plann |id|String|Read-only. ID of the task. It is 28 characters long and case-sensitive. [Format validation](planner-identifiers-disclaimer.md) is done on the service.| |orderHint|String|Hint used to order items of this type in a list view. The format is defined as outlined [here](planner-order-hint-format.md).| |percentComplete|Int32|Percentage of task completion. When set to `100`, the task is considered completed. |+|priority|Int32|Priority of the task. The valid range of values is between `0` and `10`, with the increasing value being lower priority (`0` has the highest priority and `10` has the lowest priority). Currently, Planner interprets values `0` and `1` as "urgent", `2`, `3` and `4` as "important", `5`, `6`, and `7` as "medium", and `8`, `9`, and `10` as "low". Additionally, Planner sets the value `1` for "urgent", `3` for "important", `5` for "medium", and `9` for "low".| |planId|String|Plan ID to which the task belongs.| |previewType|String|This sets the type of preview that shows up on the task. The possible values are: `automatic`, `noPreview`, `checklist`, `description`, `reference`.| |referenceCount|Int32|Number of external references that exist on the task.| Here is a JSON representation of the resource. ```json {- "activeChecklistItemCount": 1024, + "activeChecklistItemCount": "Int32", "appliedCategories": {"@odata.type": "microsoft.graph.plannerAppliedCategories"}, "assigneePriority": "String", "assignments": {"@odata.type": "microsoft.graph.plannerAssignments"}, "bucketId": "String",- "checklistItemCount": 1024, + "checklistItemCount": "Int32", "completedBy": {"@odata.type": "microsoft.graph.identitySet"}, "completedDateTime": "String (timestamp)", "conversationThreadId": "String", Here is a JSON representation of the resource. "hasDescription": true, "id": "String (identifier)", "orderHint": "String",- "percentComplete": 1024, + "percentComplete": "Int32", + "priority": "Int32", "planId": "String", "previewType": "String",- "referenceCount": 1024, + "referenceCount": "Int32", "startDateTime": "String (timestamp)", "title": "String" } |
| v1.0 | Subscription | https://github.com/microsoftgraph/microsoft-graph-docs/commits/main/api-reference/v1.0/resources/subscription.md | A subscription allows a client app to receive change notifications about changes - A [printer][] (when a print job for the printer gets to JobFetchable state - ready to be fetched for printing) and a [printTaskDefinition][] in Universal Print. For more information, see [Subscribe to change notifications from cloud printing APIs](/graph/universal-print-webhook-notifications). - A [user][] in Azure Active Directory. -For the possible resource path values for each supported resource and to learn how resources use lifecycle notifications, see [Use the Microsoft Graph API to get change notifications](webhooks.md). +For the possible resource path values for each supported resource, see [Use the Microsoft Graph API to get change notifications](webhooks.md). To learn how to use lifecycle notifications, see [Reduce missing subscriptions and change notifications](/graph/webhooks-lifecycle). ## Methods |