Merge pull request #208135 from dannyevers/74118-webhook

74118-webhook

Author: prmerger-automator[bot]

articles/marketplace/partner-center-portal/pc-saas-fulfillment-operations-api.md

@@ -4,7 +4,7 @@ description: Learn how to use the Operations APIs, which are part of the SaaS Fu
 ms.service: marketplace
 ms.subservice: partnercenter-marketplace-publisher
 ms.topic: reference
-ms.date: 03/07/2022
+ms.date: 08/24/2022
 author: arifgani
 ms.author: argani
 ---
@@ -13,6 +13,10 @@ ms.author: argani
 
 This article describes version 2 of the SaaS fulfillment operations APIs.
 
+Operations are useful to respond to any requests that come through the webhook as part of ChangePlan, ChangeQuantity, and ReInstate actions. This provides an opportunity to accept or reject a request by patch that webhook operation with Success or Failure by using the below APIs.
+
+This only applies to webhook events such as ChangePlan, ChangeQuantity, and ReInstate that need an ACK. No action is needed from the independent software vendor (ISV) on Renew, Suspend, and Unsubscribe events because they are notify-only events.
+
 ## List outstanding operations
 
 Get list of the pending operations for the specified SaaS subscription. The publisher should acknowledge returned operations by calling the [Operation Patch API](#update-the-status-of-an-operation).

articles/marketplace/partner-center-portal/pc-saas-fulfillment-webhook.md

@@ -4,7 +4,7 @@ description: Learn how to implement a webhook on the SaaS service by using the f
 ms.service: marketplace
 ms.subservice: partnercenter-marketplace-publisher
 ms.topic: reference
-ms.date: 06/14/2022
+ms.date: 08/24/2022
 author: arifgani
 ms.author: argani
 ---
@@ -18,10 +18,10 @@ When creating a transactable SaaS offer in Partner Center, the partner provides
     * ChangeQuantity
     * Renew
     * Suspend
-    * Unsubscribe
+    * Unsubscribe (notify only, no ACK needed)
 * When SaaS subscription is in *Suspended* status:
     * Reinstate
-    * Unsubscribe
+    * Unsubscribe (notify only, no ACK needed)
 
 The publisher must implement a webhook in the SaaS service to keep the SaaS subscription status consistent with the Microsoft side.  The SaaS service is required to call the Get Operation API to validate and authorize the webhook call and payload data before taking action based on the webhook notification. The publisher should return HTTP 200 to Microsoft as soon as the webhook call is processed. This value acknowledges that the webhook call has been received successfully by the publisher.
 
@@ -232,6 +232,8 @@ The publisher must implement a webhook in the SaaS service to keep the SaaS subs
 
 *Webhook payload example of unsubscribe event:*
 
+This is a notify only event. There is no send to ACK for this event.
+
 ```json
 {
   "id": "<guid>",