Azure-docs: SAAS Fulfillment webhook ID is not a GUID

Created on 9 Feb 2020  Â·  7Comments  Â·  Source: MicrosoftDocs/azure-docs

As defined in the documentation for implimenting a webhook on a SaaS service located here: https://docs.microsoft.com/en-us/azure/marketplace/partner-center-portal/pc-saas-fulfillment-api-v2#implementing-a-webhook-on-the-saas-service the "id" field being returned is not a GUID. It follows the format org:{guid}, {guid}. See example response json below.

This issue seems to be referenced in this issue as well: https://github.com/MicrosoftDocs/azure-docs/issues/40907

When the user initiates the change from the ISV service, the webhook acts as intended, with the "id" field properly populated by a GUID. However, when the user initiates the change from the Marketplace, we see the format mentioned above. JSON Below:

{ "id":"org:594e91a9-c6d8-4c2e-be51-722253734a9a,3bdea509-507a-59bd-10ff-e7deb9cd216d", "activityId":"aa821975-f8c4-4e99-8e12-f06a95486bd3", "subscriptionId":"subid", "publisherId":"publisher", "offerId":"offerid", "planId":"preview", "quantity":"4", "timeStamp":"2020-02-07T20:27:10.7294526Z", "action":"ChangeQuantity", "status":"Succeeded" }


Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Pri3 assigned-to-author marketplacsvc partnercenter-marketplace-publishesubsvc product-question triaged

All 7 comments

@nickolasfisher
Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

@YutongTie-MSFT do we have an ETA on this?

@YutongTie-MSFT @qianw211 STill waiting on resolution for this issue

@nickolasfisher @YutongTie-MSFT This is a bug on engineering side. This field should have guid format in all cases. Thanks for your feedback!

please-close

@YutongTie-MSFT @qianw211 How do we get this to engineering?

@nickolasfisher Hi, this GitHub issue has been reported to the engineering team, and the above is their reply. Thanks!

please-close this was fixed.

Was this page helpful?
0 / 5 - 0 ratings