DevTest Labs deployment broken in Portal

Question

DevTest Labs deployment broken in Portal

Paul Dash 31

In Azure DevTest Labs, when deploying an Environment from a private repo, the UI prompts for parameters then closes side pane and then gives no feedback. Deployment does not start. Activity log shows nothing.

Initiating same deployment using Azure API with same parameter values starts the deployment.

I would like the Portal to show a status, even a failure.

0 comments

1 answer

Your answer

Answer 1

For this scenario, the supported troubleshooting path in Azure DevTest Labs is to check the Azure portal notifications first, then inspect the relevant activity logs and deployment logs.

In the Azure portal, open the notifications panel from the bell icon immediately after starting the environment deployment.
- If the portal detects a creation failure, the notification should contain the error message.
Check the environment Activity log:
- Open the lab home page.
- Select the environment.
- Select Activity log on the left menu.
- Find the failed event, open it, switch to the JSON tab, and inspect the statusMessage field.
If nothing appears at the environment level, check the lab configuration and policies Activity log:
- From the lab home page, select Configuration and policies.
- Select Activity log.
- Expand failed operations and inspect the details in the JSON tab.
- Look for statusMessage for the main error details.
If the environment was created through automation or an Azure Resource Manager template path, check the deployment logs for the lab resource group:
- Open the resource group that contains the lab.
- Select Deployments under Settings.
- Open any failed deployment.
- Select Operation details for the failed operation.
If deployment operations exist but the portal view is not surfacing the failure clearly, deployment operation details can also be reviewed with PowerShell by checking failed deployment operations and their StatusMessage.

The available guidance documents describe where DevTest Labs and Azure Resource Manager record failures, but they do not document a portal setting or feature that forces the DevTest Labs portal pane to always show a status when the side pane closes and no deployment starts. The documented path is to use notifications, activity logs, and deployment operation details to determine whether the request reached the service and where it failed.