Deployment stopped working for my custom repo in DevTest Labs

Mitchell French 0 Reputation points
2026-10-19T07:54:27.1533333+00:00

Hi there,

It appears my resources have stopped deploying as of 13.10.26 from my ADO repo via Devtest Labs.

Its a pretty standard Policy and Role assignment, but when I went to do it on the 14.10 it just said

"ResourceOperationFailure → GeneralError: Value cannot be null. (Parameter 'stringToUnescape')"

The environment goes to Failed immediately; no resource group is created (no resourceGroupId), so ARM appears to never be reached.

I've tried it more recently and errors were saying something different as if MS were doing fixes. Something about not being part of the flow, but now i'm trying and nothing happens at all. As a workaround im deploying RG's and assigning the policy and roles via script, but it would be nice to see Devtest labs working again.

I know it'sgradually getting phased out, but there's been no word of it happening yet. I'd expect some form of warning.

Any advice would be appreciated.

Azure DevTest Labs
Azure DevTest Labs

An Azure service that is used for provisioning development and test environments.

0 comments No comments

1 answer

Sort by: Most helpful
  1. Zoha Fatima 675 Reputation points
    2026-10-19T19:04:08.7433333+00:00

    Hi Mitchell,

    Since the deployment fails immediately without creating a resource group, the issue may be occurring in the DevTest Labs environment provisioning process before the ARM template is submitted.

    The stringToUnescape error suggests a null or unexpected value being processed, but it does not confirm whether the problem is with your repository configuration or the DevTest Labs service.

    I recommend checking the Azure DevOps repository connection, authentication credentials, and environment template files. Also try deploying a minimal environment from the same repository to determine whether the failure affects all templates.

    If the issue began on October 13 without any configuration changes, please check Azure Service Health and raise an Azure DevTest Labs support case with the failure timestamps, region, and correlation IDs. This will help Microsoft investigate a possible service-side regression.

    I would continue using your scripted deployment workaround until the underlying issue is identified.

    Thank you, and feel free to respond back for more assistance.

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.