In case the Azure Marketplace deployment is not completed successfully, there are various ways to troubleshoot and redo the deployment. During the deployment, wizard makes varius checks to ensure that proper data is entered, but note that at this stage not all input can be checked against what is already available in Azure.
In general, make sure that names you provide for the creation of resources are unique in your Azure environment. This applies but is not limited to, for example, virtual machine names, Load Balancer names, Key Vault names, app registration names, etc.
Make sure that the objects you are referencing are accessible and properly configured. This applies but is not limited to Virtual Networks and Active Directory.
As a first step of toubleshooting, check all the values you provided and consult the section Before you start to gain insights into what values are allowed and what requirements need to be in place before you deploy.
You can view the result of the deployment at any time by clicking on the link under the Deployments label in the resource group where the Managed Application was deployed.
In this example, the deployment resulted in an error because the App Registration name that was provided already existed.
In some scenarios, the deployment history in the resource group where the managed application is published shows the error below.
In those cases, more details can be obtained by looking at the deployment history of the Managed Resource Group.
Click on the deployment to view the details. In this example, the User Assigned Managed Application did not have permissions on the specific VNet. As a result, the deployment cannot add the required network adapters to the VNet. To resolve this error, review the permissions in the introduction, provide the permissions, and try again.
In every case where the Managed Application deployment is unsuccessful, you will see the status below. At this point, you will see the Managed Application resources and a subnet of resources inside the Managed Resource Group.
There are two ways to redeploy a Managed Application:
Remove the Managed Application. This will result in an immediate removal of the entire Managed Resource Greconfigureroup as well. Once the removal is completed and you have fixed the errors, you can redeploy again.
Open the Resource Group where the Managed Application was deployed. Then, open the deployment history. Click on the Managed Application that failed and then click Redeploy.
In this case, you will see a slightly different deployment experience. All previously provided parameters are shown in a single view, except for secure values. You can fix the errors and redeploy again.
