Share via

Graph Task Subscriptions is not sending notification if the task is created through Outlook Desktop

Wei Hong 5 Reputation points
2026-06-02T14:59:00.17+00:00

I have created the a subscription for monitor the default tasks. However, it is only sending notification for tasks created through api. If the task is created through Outlook Desktop App, no notification received. I also test the event subscription, somehow the event notification is working perfectly without issues.

Here is the subscription and task object I used:

{
    "@odata.context": "https://graph.microsoft.com/beta/$metadata#subscriptions",
    "value": [
        {
            "id": "2c1fc264-22db-49e3-b1d9-466f3e356a41",
            "resource": "me/todo/lists/AAMkADRhZGQyZmQ2LTAxZTktNGUxYi04NDZjLTI0ZTVjYzUzMzlhMQAuAAAAAABPZ0FdwloCQ4H1MY8CRko9AQCxro6KkQdUSL8vkwYCuGCGAAAAAAESAAA=/tasks",
            "applicationId": "d705a3d0-78a5-4d66-821c-052cd000c238",
            "changeType": "created,updated,deleted",
            "clientState": null,
            "notificationUrl": "https://www.jobssos.com/connect/joswebhook.jsp?teamid=1&recruiterId=115548",
            "notificationQueryOptions": null,
            "notificationContentType": "application/json; charset=utf-8",
            "lifecycleNotificationUrl": "https://www.jobssos.com/connect/joswebhook.jsp?teamid=1&recruiterId=115548",
            "expirationDateTime": "2026-06-04T12:55:53Z",
            "creatorId": "de306015-cc84-43a0-8ca6-0daef779a832",
            "includeResourceData": null,
            "latestSupportedTlsVersion": "v1_2",
            "encryptionCertificate": null,
            "encryptionCertificateId": null,
            "notificationUrlAppId": null,
            "resourceChangeType": null
        },

https://graph.microsoft.com/v1.0/me/todo/lists/AAMkADRhZGQyZmQ2LTAxZTktNGUxYi04NDZjLTI0ZTVjYzUzMzlhMQAuAAAAAABPZ0FdwloCQ4H1MY8CRko9AQCxro6KkQdUSL8vkwYCuGCGAAAAAAESAAA=/tasks?$top=5&$orderby=lastModifiedDateTime%20desc/tasks

    "value": [
        {
            "@odata.etag": "W/\"sa6OipEHVEi/L5MGArhghgAHxrRZxA==\"",
            "importance": "normal",
            "isReminderOn": false,
            "status": "notStarted",
            "title": "Created In Outlook Desktop App",
            "createdDateTime": "2026-06-02T14:49:28.0099497Z",
            "lastModifiedDateTime": "2026-06-02T14:49:28.1190303Z",
            "hasAttachments": false,
            "categories": [],
            "id": "AAMkADRhZGQyZmQ2LTAxZTktNGUxYi04NDZjLTI0ZTVjYzUzMzlhMQBGAAAAAABPZ0FdwloCQ4H1MY8CRko9BwCxro6KkQdUSL8vkwYCuGCGAAAAAAESAACxro6KkQdUSL8vkwYCuGCGAAfLcxenAAA=",
            "body": {
                "content": "",
                "contentType": "text"
            }
        },
Microsoft Security | Microsoft Graph
0 comments No comments

2 answers

Sort by: Most helpful
  1. Ward Wilmsen 0 Reputation points
    2026-06-09T19:27:18.8166667+00:00

    Same issue here, even if adding private tasks through the new Planner UI the subscription notifications are not triggered anymore. Looks more like a general bug / issue to me since the new Planner UI update.

    Was this answer helpful?

    0 comments No comments

  2. AI answer

    2026-06-02T14:59:19.5533333+00:00

    Outlook tasks created via the classic Outlook tasks API are no longer a supported source for change notifications. The Outlook tasks API (/me/outlook/tasks) is deprecated and stopped returning data on August 20, 2022. The guidance is to use Microsoft To Do tasks (/me/todo/...) instead.

    The subscription shown targets a To Do task list (me/todo/lists/{id}/tasks). Notifications are only raised for changes that flow through the To Do task backend. Tasks created in Outlook Desktop that still use the old Outlook tasks store will not generate Microsoft Graph To Do (todoTask) change notifications, even though they may appear in the UI.

    To receive notifications consistently:

    1. Use To Do tasks instead of the deprecated Outlook tasks API:
      • Create and manage tasks via the To Do API (/me/todo/lists/{todoTaskListId}/tasks).
      • Ensure the Outlook client is using To Do / Microsoft 365 tasks (not the legacy Outlook tasks store) so that tasks are backed by the same To Do service.
    2. Keep the subscription valid:
      • Ensure the subscription is renewed before expirationDateTime using PATCH /subscriptions/{id} with a new expirationDateTime.
    3. If tasks are still being created via the deprecated Outlook tasks API (/me/outlook/tasks), move the workflow to To Do tasks, because the Outlook tasks API is deprecated and not supported for production or for new integrations.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.