Skip to content

Change notification (subscription lifecycle events) with an organizationId not fully parsed #1551

@jonathan-grs

Description

@jonathan-grs

Expected behavior

Subscription Lifecycle events (and possibly others) that contain an organizationId property instead of a tenantId property should be fully parsed.

Actual behavior

When a subscription lifecycle notification such as the following is sent, organizationId property not being parsed (does not exist in the ChangeNotification class):

{
    "value": [
        {
            "lifecycleEvent": "reauthorizationRequired",
            "subscriptionId": "subscription-id-uuid",
            "resource": "",
            "clientState": "client-state",
            "sequence": null,
            "resourceData": {
                "@odata.type": "#microsoft.graph.subscription",
                "@odata.id": "subscriptions/subscription-id-uuid",
                "id": "resource-id-uuid"
            },
            "encryptedContent": null,
            "organizationId": "organization-id-uuid",
            "subscriptionExpirationDateTime": "2023-09-05T01:03:01.889254-07:00"
        }
    ],
    "validationTokens": [
        "validation-toke-value"
    ]
}

Steps to reproduce the behavior

As it is unclear (to me at least) when change notifications are sent with the organizationId property instead of the tenantId property, there is no consistent reproduction scenario.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions