I am trying to fetch resource data for teams messages so I have set includeResourceData to true and also sending the additional information required. My notificationUrl and lifecycleNotificationUrl are both different. I do see the data being correctly sent to the API when registering a new webhook. When the validation happens though, both the request go to notificationUrl instead of one going to lifecycleNotificationUrl. From the doc, it says I should be receiving 2 notifications for validating the callback 1 on notificationUrl and other on lifecycleNotificationUrl
Request:
{
"changeType": "created, updated",
"notificationUrl": "https://dd6e05ac695e.ngrok.io/callback/test",
"resource": "chats/allMessages",
"expirationDateTime": "2020-07-09T00:32:28.663625Z",
"clientState": "bb295845-30ad-453e-bf57-d6b07f95263f",
"includeResourceData": true,
"lifecycleNotificationUrl": "https://dd6e05ac695e.ngrok.io/lifecycle_callback/test",
"encryptionCertificateId": "a51092ab-6954-4ee1-8342-db809fb02e78",
"encryptionCertificate": <base64 self-signed certificate>
}
Validation Log:
2020-07-08 23:37:27,687 : [INFO] [views.py:callback:73] Received path /callback/test
[08/Jul/2020 23:37:27] "POST /callback/test?validationToken=Validation%3a+Testing+client+application+reachability+for+subscription+Request-Id%3a+3076b8ff-1b56-49dd-b668-660cd7c325f9 HTTP/1.1" 200 117
2020-07-08 23:37:27,943 : [INFO] [views.py:callback:73] Received path /callback/test
[08/Jul/2020 23:37:27] "POST /callback/test?validationToken=Validation%3a+Testing+client+application+reachability+for+subscription+Request-Id%3a+3076b8ff-1b56-49dd-b668-660cd7c325f9 HTTP/1.1" 200 117
My app permission:

⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
Hi @hkadakia thanks for bringing this to our attention.
I've been able to reproduce the issue and I've let the engineering team know about it.
I'll update this issue with any progress.
thank you for your patience on the matter.
The fix is being deployed to production, we expect it to be fully rolled out within a week or two.
Closing.
Most helpful comment
Hi @hkadakia thanks for bringing this to our attention.
I've been able to reproduce the issue and I've let the engineering team know about it.
I'll update this issue with any progress.