We keep getting the error The template parameter 'runtimeConfiguration' is not found

Question

We keep getting the error The template parameter 'runtimeConfiguration' is not found

Charles Laymon 25

We keep getting this error below when we try to provision a Managed DevOps pool in our dev center project for the subscription. It works fine in another subscription we have. What is wrong with this subscription? We are using the azure portal to perform this deployment, not a script.

Unable to process template language expressions for resource '/subscriptions/01eba139-983f-445b-a98c-3f0bf2d15b19/resourceGroups/at-prd-resgrp-devops/providers/Microsoft.DevOpsInfrastructure/pools/at-prd-devops-pipeline-pools' at line '114' and column '9'. 'The template parameter 'runtimeConfiguration' is not found. Please see https://aka.ms/arm-syntax-parameters for usage details.' (Code: InvalidTemplate)

{

"code": "InvalidTemplate",

"message": "Unable to process template language expressions for resource '/subscriptions/01eba139-983f-445b-a98c-3f0bf2d15b19/resourceGroups/at-prd-resgrp-devops/providers/Microsoft.DevOpsInfrastructure/pools/at-prd-devops-pool-pipeline' at line '118' and column '9'. 'The template parameter 'runtimeConfiguration' is not found. Please see https://aka.ms/arm-syntax-parameters for usage details.'",

"additionalInfo": [

{

  "type": "TemplateViolation",

  "info": {

    "lineNumber": 118,

    "linePosition": 9,

    "path": ""

  }

}

]

}

/subscriptions/01eba139-983f-445b-a98c-3f0bf2d15b19/resourceGroups/at-prd-resgrp-devops/providers/Microsoft.Resources/deployments/at-prd-devops-pipeline-pools/operations/25304B1784BD7979

Deploy correlation Id:

3d1af4cb-2a6b-43c8-aeb2-f48e4663ef3b

Pravallika KV 3,565 Reputation points Microsoft External Staff Moderator

2025-12-10T20:08:34.7466667+00:00

Hi @Charles Laymon ,

Thanks for reaching out to Microsoft Q&A.

I will check and update you shortly.
Charles Laymon 25 Reputation points

2025-12-11T09:09:51.79+00:00

Ok thanks. So we already had the Microsoft.DevOpsInfrastructure provider registered. Also we had Owner on the subscription in question as well. However this morning it seems to work. Is it possible there is some delay to get everything configured in Azure before the provisioning of a Managed DevOps Pool can happen?
Charles Laymon 25 Reputation points

2025-12-11T13:14:12.6833333+00:00

We created the ticket per your request. Thanks for looking into this!
Pravallika KV 3,565 Reputation points Microsoft External Staff Moderator

2025-12-11T18:34:39.9266667+00:00
@Charles Laymon ,

Yes, that's exactly what must have happened. Even though the resource provider was registered and you had Owner permissions, there is often a propagation delay in Azure for preview features or new API versions.

Root cause:

Microsoft.DevOpsInfrastructure resource provider was registered, but the ARM schema and API version supporting runtimeConfiguration had not fully propagated to the subscription.

Enabling Managed DevOps Pools can take time to become fully available in a subscription, even if RP registration is complete.

Azure takes minutes to a few hours to propagate:

RP registration updates

Preview feature activation

New API versions / ARM schema

Once propagation completed, the portal could successfully provision the pool.
Charles Laymon 25 Reputation points

2025-12-11T18:45:52.82+00:00

Ok, feel free to mark this as completed. However it would be better if Azure somehow gave an indication of this incomplete state somehow so we could better understand teh problem.
Pravallika KV 3,565 Reputation points Microsoft External Staff Moderator

2025-12-11T18:49:39.0433333+00:00

@Charles Laymon , Thanks for the confirmation. I have summarized and posted the answer. If the resolution was helpful, kindly take a moment to accept the answer and upvote it 👍 it as a token of appreciation.

Answer accepted by question author

1 additional answer

Your answer

Pravallika KV 3,565 Reputation points Microsoft External Staff Moderator

2025-12-10T20:08:34.7466667+00:00

Hi @Charles Laymon ,

Thanks for reaching out to Microsoft Q&A.

I will check and update you shortly.
Charles Laymon 25 Reputation points

2025-12-11T09:09:51.79+00:00

Ok thanks. So we already had the Microsoft.DevOpsInfrastructure provider registered. Also we had Owner on the subscription in question as well. However this morning it seems to work. Is it possible there is some delay to get everything configured in Azure before the provisioning of a Managed DevOps Pool can happen?
Charles Laymon 25 Reputation points

2025-12-11T13:14:12.6833333+00:00

We created the ticket per your request. Thanks for looking into this!
Pravallika KV 3,565 Reputation points Microsoft External Staff Moderator

2025-12-11T18:34:39.9266667+00:00

@Charles Laymon ,

Yes, that's exactly what must have happened. Even though the resource provider was registered and you had Owner permissions, there is often a propagation delay in Azure for preview features or new API versions.

Root cause:

Microsoft.DevOpsInfrastructure resource provider was registered, but the ARM schema and API version supporting runtimeConfiguration had not fully propagated to the subscription.

Enabling Managed DevOps Pools can take time to become fully available in a subscription, even if RP registration is complete.

Azure takes minutes to a few hours to propagate:

RP registration updates

Preview feature activation

New API versions / ARM schema

Once propagation completed, the portal could successfully provision the pool.
Charles Laymon 25 Reputation points

2025-12-11T18:45:52.82+00:00

Ok, feel free to mark this as completed. However it would be better if Azure somehow gave an indication of this incomplete state somehow so we could better understand teh problem.
Pravallika KV 3,565 Reputation points Microsoft External Staff Moderator

2025-12-11T18:49:39.0433333+00:00

@Charles Laymon , Thanks for the confirmation. I have summarized and posted the answer. If the resolution was helpful, kindly take a moment to accept the answer and upvote it 👍 it as a token of appreciation.

Answer 1

Hi @Charles Laymon ,

Thanks for reaching out to Microsoft Q&A.

Managed DevOps pools require specific DevOps features or entitlements. Some subscriptions e.g., certain EA, CSP, or internal subscriptions may have newer DevOps features enabled, which include the runtimeConfiguration parameter. The subscription failing likely does not have this feature enabled, so the portal ARM template cannot resolve the parameter.

Resource provider registration

The resource provider Microsoft.DevOpsInfrastructure may not be fully registered or up-to-date in this subscription.

You can check this via Azure CLI:

az provider show --namespace Microsoft.DevOpsInfrastructure

If registrationState is not Registered, register it:

az provider register --namespace Microsoft.DevOpsInfrastructure

Ensure you have at least DevOps Contributor or Owner role on the subscription/resource group.
Compare feature flags, resource provider versions, and RBAC roles between the working and failing subscriptions.

Test with CLI / PowerShell

Using CLI/PowerShell allows you to explicitly pass the runtimeConfiguration parameter, bypassing the portal template. For example:

New-AzResourceGroupDeployment `
    -ResourceGroupName "at-prd-resgrp-devops" `
    -TemplateFile "ManagedDevOpsPool.json" `
    -runtimeConfiguration @{ "osType" = "windows"; "agentVersion" = "2.0" }

Is it possible there is some delay to get everything configured in Azure before the provisioning of a Managed DevOps Pool can happen?

Yes, that's exactly what must have happened. Even though the resource provider was registered and you had Owner permissions, there is often a propagation delay in Azure for preview features or new API versions.

Root cause:

Microsoft.DevOpsInfrastructure resource provider was registered, but the ARM schema and API version supporting runtimeConfiguration had not fully propagated to the subscription.

Enabling Managed DevOps Pools can take time to become fully available in a subscription, even if RP registration is complete.

Azure takes minutes to a few hours to propagate:

RP registration updates
Preview feature activation
New API versions / ARM schema

Once propagation completed, the portal could successfully provision the pool.

Hope it helps!

Please do not forget to click "Accept the answer” and Yes, this can be beneficial to other community members.

User's image

If you have any other questions, let me know in the "comments" and I would be happy to help you.

Answer 2

The error message you are encountering indicates that the template parameter 'runtimeConfiguration' is not found during the deployment of the Managed DevOps pool. This typically occurs when the ARM template being used does not define the 'runtimeConfiguration' parameter, or the parameter is not being passed correctly in the deployment process.

Here are a few steps you can take to troubleshoot this issue:

Check the ARM Template: Ensure that the ARM template you are using to deploy the Managed DevOps pool includes the 'runtimeConfiguration' parameter. If it is missing, you will need to add it to the parameters section of your template.
Parameter Passing: Verify that when you are deploying the template, you are providing a value for the 'runtimeConfiguration' parameter. If you are using the Azure portal, make sure that this parameter is included in the parameters input section.
Compare with Working Subscription: Since you mentioned that it works fine in another subscription, compare the ARM templates and parameters used in both subscriptions. Look for any discrepancies that might be causing the issue in the failing subscription.
Template Validation: Use the Azure Resource Manager template validation feature to check for any syntax errors or missing parameters in your template before deployment.

By following these steps, you should be able to identify and resolve the issue with the missing 'runtimeConfiguration' parameter in your deployment.

References:

Troubleshoot Managed DevOps Pools issues

Charles Laymon 25 Reputation points

2025-12-10T19:50:08.8066667+00:00

This answer is not clear nor applicable. We are performing the deploy from the Azure portal so the portal is generating the script and thus is the culprit. We have developer support and want an engineer to look at this.

Share via

We keep getting the error The template parameter 'runtimeConfiguration' is not found

1 additional answer

Your answer