MS Exchange sending differed renewal subscription payload as compared to the given documentation.

Describe the bug

MS Exchange sending differed renewal subscription payload as compared to the given documentation. tenantId has been changed organizationId. however tenantid is still used other notifications like Mail, GroupChange

Expected behavior

Expected:

{
"value": [
{
"subscriptionId":"<subscription_guid>",
"subscriptionExpirationDateTime":"2019-03-20T11:00:00.0000000Z",
"tenantId": "<tenant_guid>",
"clientState":"",
"lifecycleEvent": "subscriptionRemoved or missed or reauthorizationRequired" }
]
}

Actual

{
"value": [
{
"subscriptionId": "",
"encryptedContent": null,
"organizationId": "",
"lifecycleEvent": "reauthorizationRequired",
"clientState": "",
"subscriptionExpirationDateTime": "2026-04-29T16:08:45.5745035+00:00",
"resource": "Subscriptions/",
"resourceChangeType": null,
"resourceData": {
"@odata.id": "subscriptions/",
"@odata.type": "#microsoft.graph.subscription",
"id": ""
}
}
]
}

How to reproduce

Create simple mail subscription with Lifecycleurl notification and monitor renew notification payload.

SDK Version

No response

Latest version known to work for scenario above?

No response

Known Workarounds

No response

Debug output

</details>


### Configuration

_No response_

### Other information

_No response_

Start by reproducing a Microsoft Graph mail subscription with a lifecycle URL and compare the renewal notification payload with the documented schema. Trace the SDK's lifecycle notification handling to determine why organizationId is emitted instead of tenantId; done when renewal payloads match the expected contract without changing tenantId behavior for Mail and GroupChange notifications.