Azure Devops pipeline and dataset parametrization issue

As mentioned in the message the file I shared is arm-template-parameters-definition.json with pipeline parameters in them

Deepa M Thanks for the clarification, and apologies for the confusion earlier.

You're right, if the arm-template-parameters-definition.json you shared already contains the pipeline parameters, then let’s troubleshoot further based on that.
Here are a few things to check that could cause parameters not to appear in Azure DevOps:

Parameter Structure and Naming

Even when parameters are present, DevOps expects them to follow a specific pattern. Please double-check that:

The parameter names are fully qualified (e.g., pipeline1_parameters_jobId)

They are structured like this:

{
  "parameters": {
    "pipeline1_parameters_jobId": {
      "value": ""
    }
  }
}

Any mismatch in naming or format could prevent them from showing up in the override UI.

DevOps Task Configuration

Check your release pipeline's ARM deployment step:

• Ensure both files (ARMTemplateForFactory.json and arm-template-parameters-definition.json) are referenced correctly
• Use the correct task type like AzureResourceManagerTemplateDeployment@3 (older versions may not fully support parameter override UI)
• If using a YAML pipeline, confirm the parametersFile path is correct and relative to the repo root

DevOps Metadata Caching

DevOps sometimes caches metadata for override UI:

• Try removing and re-adding the ARM deployment task
• Alternatively, create a new release pipeline to test if parameters show up there.

Hope this helps. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

I have tried them all , I need clarification with "pipeline1_parameters_jobId" as of now the structure I am following the structure which is as per microsoft recommendation as shown below . when you say is as pipeline_parametrs_jobid, where do I fetch it from . The name of the pipeline is fecthed from properties of the pipeline under name section. also if my pipeline is within a folder do I have to mention the folder name anywhere ?

 "Microsoft.DataFactory/factories/pipelines": {
        "Name_of_Pipeline": {
            "parameters": {
                    "General_parameter1": { "type": "string" },
                    "General_parameter2": { "type": "string" },
                    "General_parameter3": { "type": "string" },
                    "General_parameter4": { "type": "string" },
 	                "General_parameter5": { "type": "string" }
                }

Hi Deepa M You're on the right track with the structure you're using. To clarify further Azure DevOps expects override parameter names to follow a specific pattern based on the pipeline and parameter names. Here's how it works:

Where do names like pipeline1_parameters_jobId come from?

Azure DevOps automatically prefixes parameter names in the arm-template-parameters-definition.json using this format:

<ADFObjectName>_parameters_<ParameterName>

So, if your pipeline is named LoadCustomerData and has a parameter called JobId, the parameter in the override file must be written as:

{
  "parameters": {
    "LoadCustomerData_parameters_JobId": {
      "value": ""
    }
  }
}

This is how DevOps maps parameters to individual ADF objects (pipelines/datasets).

Do pipeline folders affect this naming?

No, the folder name does not need to be included in the parameter name.

The ADF export process (via “Export ARM Template” in the ADF UI) automatically strips out folder hierarchy and uses only the object name. So even if your pipeline is under a folder, just use the pipeline's name as shown under name in its properties (e.g., "LoadCustomerData").

Finally Check:

Re-check your arm-template-parameters-definition.json file and ensure that parameter names follow this pattern: "<pipelineName>_parameters_<parameterName>"

Ensure the pipeline name matches exactly (case-sensitive) with what’s shown in the ADF JSON under "name".

No need to include folder names in parameter paths.

Example based on your structure:

If your pipeline JSON looks like:

"Microsoft.DataFactory/factories/pipelines": {
    "ProcessOrders": {
        "properties": {
            "parameters": {
                "Region": { "type": "string" }
            }
        }
    }
}

Then your arm-template-parameters-definition.json should include:

{
  "parameters": {
    "ProcessOrders_parameters_Region": {
      "value": ""
    }
  }
}

Hope this helps. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Hi Deepa M Following up to see if the above answer was helpful. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.