Publish Extension Update

Publish Extension Update

Upload a package, await validation, then submit and track publication.

1. Upload the new extension package as a draft for the product. The API accepts the upload asynchronously and returns an operation identifier used to track validation progress.
2. Poll the package upload operation until it leaves the InProgress state. A Succeeded status means the package validated and is ready to submit; a Failed status stops the workflow.
3. Create a submission for the validated draft package, initiating the review and publishing process. The API queues the submission and returns 202 Accepted with the new submission identifier.
4. Poll the submission until it reaches a terminal state. InReview means the review is still running, Published means the update is live, and Failed or Cancelled stops the workflow.

What you'll need to have ready

• accessToken: Azure AD bearer access token acquired via the client credentials flow for the Microsoft Partner Center scope.
• productId: The product (extension) identifier to publish an update for.
• packageContent: The binary contents of the extension package ZIP file.
• notes: Optional notes for the review team attached to the submission.

For your developer

Arazzo workflow microsoft-edge:publish-extension-update, 4 operations: uploadPackage → getPackageUploadStatus → createSubmission → getSubmission. Specs on APIs.io.