Microsoft Graph webhook events
6 Microsoft Graph event types in 2 resources. 5 have sample payloads.
Every event here can also reach agents as an MCP event through Hookdeck: MCP events →
change
created
documented from Microsoft Graph docs (example)
created A resource you subscribed to is created
Identified by changeType on each value item; lifecycleEvent on lifecycle notices
Resource change
{
"value": [
{
"id": "lsgTZMr9KwAAA",
"subscriptionId": "{subscription_guid}",
"subscriptionExpirationDateTime": "2016-03-19T22:11:09.952Z",
"clientState": "secretClientValue",
"changeType": "created",
"resource": "users/{user_guid}@{tenant_guid}/messages/{long_id_string}",
"tenantId": "84bd8158-6d4d-4958-8b9f-9d6445542f95",
"resourceData": { … }
}
]
} Key fields
| Field | Type | Example |
|---|---|---|
value[0].id | string | lsgTZMr9KwAAA |
Full schema: 14 fields.
From Microsoft Graph docs
-
Content type
application/json
updated
documented from Microsoft Graph docs (example)
updated A resource you subscribed to is updated
Identified by changeType on each value item; lifecycleEvent on lifecycle notices
Resource change
{
"value": [
{
"subscriptionId": "{Subscription id}",
"clientState": "{secret client state}",
"changeType": "updated",
"tenantId": "{Organization/Tenant id}",
"resource": "communications/presences/{id}",
"subscriptionExpirationDateTime": "2023-09-14T10:00:00.0000000Z",
"resourceData": { … },
"organizationId": "{Organization/Tenant id}"
}
]
} deleted
documented No payload yet
deleted A resource you subscribed to is deleted
Identified by changeType on each value item; lifecycleEvent on lifecycle notices
Resource change
No payload yet.
lifecycle
missed
documented official schema
missed Some change notifications weren't delivered, so resync
Identified by changeType on each value item; lifecycleEvent on lifecycle notices
Resource lifecycle
{
"value": [
{
"subscriptionId": "<subscription_guid>",
"subscriptionExpirationDateTime": "2019-03-20T11:00:00.0000000Z",
"tenantId": "<tenant_guid>",
"clientState": "<secretClientState>",
"lifecycleEvent": "missed"
}
]
} subscriptionRemoved
documented official schema
subscriptionRemoved Graph removes the subscription, so create a new one
Identified by changeType on each value item; lifecycleEvent on lifecycle notices
Resource lifecycle
{
"value": [
{
"subscriptionId": "<subscription_guid>",
"subscriptionExpirationDateTime": "2019-03-20T11:00:00.0000000Z",
"tenantId": "<tenant_guid>",
"clientState": "<secretClientState>",
"lifecycleEvent": "subscriptionRemoved"
}
]
} reauthorizationRequired
documented official schema
reauthorizationRequired The subscription needs reauthorizing before notifications pause
Identified by changeType on each value item; lifecycleEvent on lifecycle notices
Resource lifecycle
{
"value": [
{
"subscriptionId": "<subscription_guid>",
"subscriptionExpirationDateTime": "2019-03-20T11:00:00.0000000Z",
"tenantId": "<tenant_guid>",
"clientState": "<secretClientState>",
"lifecycleEvent": "reauthorizationRequired"
}
]
} Buffer Graph's batches before they reach your handler.
Event Gateway accepts each batched POST, queues it and retries to your service on your schedule, so a slow handler doesn't lose notifications.