Skip to content

Commit 42d0f7b

Browse files
authored
Merge pull request MicrosoftDocs#32901 from changeworld/patch-15
Fix nonunified
2 parents a0262e8 + 2968293 commit 42d0f7b

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/marketplace/cloud-partner-portal/azure-applications/cpp-handling-review-feedback.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -13,14 +13,14 @@ ms.author: pabutler
1313

1414
This article explains how to access the Azure DevOps environment used by the Microsoft Azure Marketplace review team. 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 these issues, you must resubmit your offer to continue to publish it on the Azure Marketplace. The following diagram illustrates how this feedback process relates to the publishing process.
1515

16-
![Publishing steps with VSTS feedback](./media/pub-flow-vsts-access.png)
16+
![Publishing steps with Azure DevOps feedback](./media/pub-flow-vsts-access.png)
1717

1818
Typically, review issues are referenced as pull request (PR). Each PR is linked to an online [Azure DevOps](https://azure.microsoft.com/services/devops/) (previously named Visual Studio Team Services (VSTS)) item, which contains details about the issue. The following image displays an example of a review PR reference. For complex situations, the review and support teams may also email you.
1919

2020
![Status tab displaying review feedback](./media/status-tab-ms-review.png)
2121

2222

23-
## VSTS access
23+
## Azure DevOps access
2424

2525
To view the PR items referenced in review feedback, publishers must first be granted proper authorization. Otherwise, new publishers receive a `401 - Not Authorized` response page when trying to view PRs. To request access to this Azure DevOps repository, perform the following steps:
2626

@@ -35,7 +35,7 @@ To view the PR items referenced in review feedback, publishers must first be gra
3535
![Support ticket category](./media/support-incident1.png)
3636

3737
4. In **Step 1 of 2** page, supply your contact information and select **Continue**.
38-
5. In **Step 2 of 2** page, specify an incident title (for example `Request VSTS access`) and supply the information you collected in the first step (above). Read and accept the agreement, then select **Submit**.
38+
5. In **Step 2 of 2** page, specify an incident title (for example `Request Azure DevOps access`) and supply the information you collected in the first step (above). Read and accept the agreement, then select **Submit**.
3939

4040
If the incident creation was successful, a confirmation page is displayed. Save the confirmation information on this page for your reference. The Microsoft Support Team should reply to your access request within a few business days.
4141

0 commit comments

Comments
 (0)