Handle review feedback for Azure application offers

This article explains how to access feedback from the Microsoft Azure Marketplace review team in Azure DevOps. If critical issues are found in your Azure application offer during the Microsoft review step, you can sign into this system to view detailed information about these issues (review feedback). After you fix all issues, you must resubmit your offer to continue to publish it on Azure Marketplace. The following diagram illustrates how this feedback process relates to the publishing process.

You can download our TTK and test your offers locally before you submit them to ensure that they will pass once you go live.

Screenshot of Azure apps verification process.

Typically, review issues are referenced as a pull request (PR). Each PR is linked to an online Azure DevOps item, which contains details about the issue. The following image displays an example of the Partner Center experience if issues are found during reviews.

Publishing status

The PR that contains specific details about the submission will be mentioned in the “View Certification Report” link. For complex situations, the review and support teams may also email you.

Azure DevOps access

All users with access to the “developer” role in Partner Center will have access to view the PR items referenced in review feedback.

Reviewing the pull request

Use the following procedure to review issues documented in the pull request.

  1. In the Microsoft review sections of Publishing steps form, select a PR link to launch your browser and navigate to the Overview (home) page for this PR. The following image depicts an example of the critical issue home page for the Contoso sample app offer. This page contains useful summary information about the review issues found in the Azure app.

    Pull request home page
    Click on this image to expand.

  2. (Optional) On the right side of the window, in the section Policies, select the issue message (in this example: Policy Validation failed) to investigate the low-level details of the issue, including the associated log files. Errors are typically displayed at the bottom of the log files.

  3. In the menu on the left-side of the home page, select Files to display the list files that comprise the technical assets for this offer. The Microsoft reviewers should have added comments describing the discovered critical issues. In the following example, two issues have been discovered.

    Screenshot that highlights Files and the two issues that were discovered.
    Click on this image to expand.

  4. Select each comment node in the left tree to navigate to the comment in context of the surrounding code. Fix your source code in your team's project to correct the issue described by the comment.


You cannot edit your offer's technical assets within the review team's Azure DevOps environment. For publishers, this is a read-only environment for the contained source code. However, you can leave replies to the comments for the benefit of the Microsoft review team.

In the following example, the publisher has reviewed, corrected, and replied to the first issue.

First fix and comment reply

Next steps