Synpase 'Publish' in workspace is not updating Parameters in TemplateParametersForWorkspace.json as expected

Question

Synpase 'Publish' in workspace is not updating Parameters in TemplateParametersForWorkspace.json as expected

Drithi Deepak 0 Microsoft Employee

I am having an issue where LinkedServices in Synapse are not getting updated (connections strings) during rollout to PreProd and Prod workspaces. When I “Publish” in Synapse, Publish updates only TemplateForWorkspace.json but does not update TemplateParametersForWorkspace.json with newly added linked service parameters. As a result, linked-service overrides are not applied when "DeploySynapseArtifacts" Ev2 extension is called.

I have created “template-parameters-definition.json” parameter file for linked services at the root of my repo (same root folder is configured in my Dev Synpase Workspace). Issue seems to be Synapse Publish is not honoring template-parameters-definition.json for linked services in this workspace hence an updated TemplateParametersForWorkspace.json is not getting generated during Publish.

I have also included these Parameters in ScopeBindings and synapse.httpextensionParameters.json.

Pilladi Padma Sai Manisha 11,605 Reputation points Microsoft External Staff Moderator

2026-07-07T19:11:15.48+00:00
Hi @Drithi Deepak

Based on your description, the Publish operation should regenerate both TemplateForWorkspace.json and TemplateParametersForWorkspace.json by honoring the template-parameters-definition.json file. If only TemplateForWorkspace.json is being updated while the parameter template is not, it suggests that the custom parameter definition may not be getting picked up during the publish process.

Could you please confirm the following?

Is the template-parameters-definition.json file located at the root of the Git repository configured for your Synapse workspace?

Were the changes to this file committed to the collaboration branch before performing Publish?

Does this issue occur only in this workspace, or have you observed the same behavior in other Synapse workspaces?

Additionally, could you share the relevant section of your template-parameters-definition.json (with any sensitive information removed)? This will help us verify whether the parameter definitions are in the expected format and better understand why the linked service parameters are not being generated in TemplateParametersForWorkspace.json
Pilladi Padma Sai Manisha 11,605 Reputation points Microsoft External Staff Moderator

2026-07-08T18:51:51.66+00:00

Hi @Drithi Deepak
I hope you had a chance to review the information shared earlier, and I hope this information has been helpful! If you still have questions, please let us know what is needed in the comments so the question can be answered.
Drithi Deepak 0 Reputation points Microsoft Employee

2026-07-10T23:03:14.59+00:00
@Pilladi Padma Sai Manisha Thanks for your feedback! Please see my responses below:

Yes, template-parameters-definition.json is at the root of the repo

Yes, changes were committed long back and we do a Publish before every release

Currently issue is observed only in this workspace - we don't have Git enabled in other workspaces due to security hence I have been only able to test in this workspace

Sure, please find the attached template file - I have changed the extension type to .txt from .json to enable upload: template-parameters-definition.txt
Pilladi Padma Sai Manisha 11,605 Reputation points Microsoft External Staff Moderator

2026-07-11T23:49:05.79+00:00
Hi @Drithi Deepak
Thank you for sharing the template-parameters-definition.json content.

I reviewed the file, and the structure looks valid. The linked service properties (baseUrl, url, and database) are defined using the expected parameterization syntax, so I don't see an obvious issue with the configuration itself.

Since you've also confirmed that:

the file is located at the repository root,

the changes have been committed and published, and

the behavior is isolated to this specific Synapse workspace,

this doesn't appear to be a straightforward configuration issue.

To help us narrow this down further, could you also let us know:

Are the linked services (qms_key_vault, LS_QMS_ADLS, and LS_QMS_Kusto) newly created, or were they already present when the custom parameter file was introduced?

If you make a small change to one of these linked services (for example, updating its description) and perform Publish again, does TemplateParametersForWorkspace.json remain unchanged?

Are there any errors or warnings displayed during the Publish operation?

Based on the information you've provided so far, if the custom parameter definition is valid and Publish continues to ignore it only for this workspace, we'll likely need to investigate this further as a workspace-specific Publish behavior.te this further as a workspace-specific Publish behavior.
Pilladi Padma Sai Manisha 11,605 Reputation points Microsoft External Staff Moderator

2026-07-14T18:54:10.7466667+00:00

HI @Drithi Deepak
I hope you had a chance to review the information shared earlier, and I hope this information has been helpful! If you still have questions, please let us know what is needed in the comments so the question can be answered.
Drithi Deepak 0 Reputation points Microsoft Employee

2026-07-15T19:36:04.45+00:00
@Pilladi Padma Sai Manisha TemplateFileNotGettingUpdated.png

No these LinkedServices were created a while ago and they were already present when the custom parameter file was introduced

I tested this by making a small change in the connection string of "LS_QMS_ADLS" linkedService and published it today (7/15) but the "TemplateParametersForWorkspace.json" did not get updated - I have included screenshots for these

No errors or warnings displayed, Publish is successful.
Pilladi Padma Sai Manisha 11,605 Reputation points Microsoft External Staff Moderator

2026-07-21T22:23:34.8133333+00:00

Thank you for confirming and for performing the additional validation.

Based on the information you've shared, you've reproduced the issue by modifying the LS_QMS_ADLS linked service and performing a Publish. Although the publish completed successfully and updated TemplateForWorkspace.json, TemplateParametersForWorkspace.json was not updated, and no errors or warnings were reported.

Since you've also confirmed that the linked services were already present when the custom parameter file was introduced and the template-parameters-definition.json is correctly configured, this behavior is not expected.

I'll engage the appropriate Synapse engineering team to review this behavior and determine why TemplateParametersForWorkspace.json is not being regenerated during the Publish operation for this workspace.

Thank you for providing the detailed information and screenshots. They will help with the investigation, and I'll keep you updated as soon as I have an update.
Drithi Deepak 0 Reputation points Microsoft Employee

2026-07-27T20:02:31.9533333+00:00

@Pilladi Padma Sai Manisha Is there any update from the Synapse team on this issue? This still persists in our workspace and requires manual intervention to update. Please let me know.
Drithi Deepak 0 Reputation points Microsoft Employee

2026-07-29T20:08:38.0366667+00:00

@Pilladi Padma Sai Manisha Could you please share the ICM link that was created with Synapse team for tracking?

1 answer

Your answer

Pilladi Padma Sai Manisha 11,605 Reputation points Microsoft External Staff Moderator

2026-07-07T19:11:15.48+00:00

Hi @Drithi Deepak

Based on your description, the Publish operation should regenerate both TemplateForWorkspace.json and TemplateParametersForWorkspace.json by honoring the template-parameters-definition.json file. If only TemplateForWorkspace.json is being updated while the parameter template is not, it suggests that the custom parameter definition may not be getting picked up during the publish process.

Could you please confirm the following?

Is the template-parameters-definition.json file located at the root of the Git repository configured for your Synapse workspace?

Were the changes to this file committed to the collaboration branch before performing Publish?

Does this issue occur only in this workspace, or have you observed the same behavior in other Synapse workspaces?

Additionally, could you share the relevant section of your template-parameters-definition.json (with any sensitive information removed)? This will help us verify whether the parameter definitions are in the expected format and better understand why the linked service parameters are not being generated in TemplateParametersForWorkspace.json
Pilladi Padma Sai Manisha 11,605 Reputation points Microsoft External Staff Moderator

2026-07-08T18:51:51.66+00:00

Hi @Drithi Deepak
I hope you had a chance to review the information shared earlier, and I hope this information has been helpful! If you still have questions, please let us know what is needed in the comments so the question can be answered.
Drithi Deepak 0 Reputation points Microsoft Employee

2026-07-10T23:03:14.59+00:00

@Pilladi Padma Sai Manisha Thanks for your feedback! Please see my responses below:

Yes, template-parameters-definition.json is at the root of the repo

Yes, changes were committed long back and we do a Publish before every release

Currently issue is observed only in this workspace - we don't have Git enabled in other workspaces due to security hence I have been only able to test in this workspace

Sure, please find the attached template file - I have changed the extension type to .txt from .json to enable upload: template-parameters-definition.txt
Pilladi Padma Sai Manisha 11,605 Reputation points Microsoft External Staff Moderator

2026-07-11T23:49:05.79+00:00

Hi @Drithi Deepak
Thank you for sharing the template-parameters-definition.json content.

I reviewed the file, and the structure looks valid. The linked service properties (baseUrl, url, and database) are defined using the expected parameterization syntax, so I don't see an obvious issue with the configuration itself.

Since you've also confirmed that:

the file is located at the repository root,

the changes have been committed and published, and

the behavior is isolated to this specific Synapse workspace,

this doesn't appear to be a straightforward configuration issue.

To help us narrow this down further, could you also let us know:

Are the linked services (qms_key_vault, LS_QMS_ADLS, and LS_QMS_Kusto) newly created, or were they already present when the custom parameter file was introduced?

If you make a small change to one of these linked services (for example, updating its description) and perform Publish again, does TemplateParametersForWorkspace.json remain unchanged?

Are there any errors or warnings displayed during the Publish operation?

Based on the information you've provided so far, if the custom parameter definition is valid and Publish continues to ignore it only for this workspace, we'll likely need to investigate this further as a workspace-specific Publish behavior.te this further as a workspace-specific Publish behavior.
Pilladi Padma Sai Manisha 11,605 Reputation points Microsoft External Staff Moderator

2026-07-14T18:54:10.7466667+00:00

HI @Drithi Deepak
I hope you had a chance to review the information shared earlier, and I hope this information has been helpful! If you still have questions, please let us know what is needed in the comments so the question can be answered.
Drithi Deepak 0 Reputation points Microsoft Employee

2026-07-15T19:36:04.45+00:00

@Pilladi Padma Sai Manisha TemplateFileNotGettingUpdated.png

No these LinkedServices were created a while ago and they were already present when the custom parameter file was introduced

I tested this by making a small change in the connection string of "LS_QMS_ADLS" linkedService and published it today (7/15) but the "TemplateParametersForWorkspace.json" did not get updated - I have included screenshots for these

No errors or warnings displayed, Publish is successful.
Pilladi Padma Sai Manisha 11,605 Reputation points Microsoft External Staff Moderator

2026-07-21T22:23:34.8133333+00:00

Thank you for confirming and for performing the additional validation.

Based on the information you've shared, you've reproduced the issue by modifying the LS_QMS_ADLS linked service and performing a Publish. Although the publish completed successfully and updated TemplateForWorkspace.json, TemplateParametersForWorkspace.json was not updated, and no errors or warnings were reported.

Since you've also confirmed that the linked services were already present when the custom parameter file was introduced and the template-parameters-definition.json is correctly configured, this behavior is not expected.

I'll engage the appropriate Synapse engineering team to review this behavior and determine why TemplateParametersForWorkspace.json is not being regenerated during the Publish operation for this workspace.

Thank you for providing the detailed information and screenshots. They will help with the investigation, and I'll keep you updated as soon as I have an update.
Drithi Deepak 0 Reputation points Microsoft Employee

2026-07-27T20:02:31.9533333+00:00

@Pilladi Padma Sai Manisha Is there any update from the Synapse team on this issue? This still persists in our workspace and requires manual intervention to update. Please let me know.
Drithi Deepak 0 Reputation points Microsoft Employee

2026-07-29T20:08:38.0366667+00:00

@Pilladi Padma Sai Manisha Could you please share the ICM link that was created with Synapse team for tracking?

Answer 1

Hi Drithi,

This usually happens when Synapse Publish is not actually reading the custom parameter definition file, or the JSON path in the file does not match the linked service JSON.

A few things to check:

The file name must be exactly:

template-parameters-definition.json

It must be committed in the root of the Git branch that Synapse uses as the collaboration branch. If the file is only in another branch, local folder, or not committed before Publish, Synapse will use the default parameter template.

For Synapse, make sure the resource type is:

"Microsoft.Synapse/workspaces/linkedServices"

not the Data Factory type:

"Microsoft.DataFactory/factories/linkedServices"

Make sure the property path matches the linked service JSON. For example, for a connection string under typeProperties:

{
  "Microsoft.Synapse/workspaces/linkedServices": {
    "*": {
      "properties": {
        "typeProperties": {
          "connectionString": "|:-connectionString:secureString"
        }
      }
    }
  }
}

Re-publish from Synapse Studio after committing the file, then check whether TemplateParametersForWorkspace.json in the publish branch contains the new parameter.

ScopeBindings and synapse.httpextensionParameters.json will not create parameters by themselves. They can only override parameters that already exist in TemplateParametersForWorkspace.json.

If it is still not generated, I would test with a very small parameter definition first, for only one obvious linked service property such as connectionString or Key Vault baseUrl. If that works, then add the remaining linked service properties one by one.

Also, if the linked service uses Key Vault, it is usually better to keep the secret name consistent across environments and parameterize the Key Vault linked service/base URL rather than hardcoding connection strings in the deployment pipeline.

Docs:

Synapse CI/CD custom parameters: https://learn.microsoft.com/en-us/azure/synapse-analytics/cicd/continuous-integration-delivery#create-custom-parameters-in-the-workspace-template

Synapse workspace deployment task: https://learn.microsoft.com/en-us/azure/synapse-analytics/cicd/continuous-integration-delivery

Parameterize linked services: https://learn.microsoft.com/en-us/azure/data-factory/parameterize-linked-services

Drithi Deepak 0 Reputation points Microsoft Employee

2026-07-15T19:45:09.08+00:00

@Ravi Kiran Pagidi Thanks for your feedback! Please see my responses below:

I have checked the 3 things - file name matches correctly, resource type says LinkedServices and Connection string is under "typeProperties" - I have also attached my template file here for your reference.

I tested by updated a LinkedService connection string and published but neither the parameter or updated connection string appears in "TemplateParametersForWorkspace.json" file. For this test, I choose a LinkedService that does not use Key Vault.

Please advise as this issue persists.
Ravi Kiran Pagidi 170 Reputation points

2026-07-16T02:12:20.47+00:00

Hi Drithi,

Thanks for checking. One thing I would verify now is the exact casing and structure of the custom template file.

For Synapse, the resource type key should be exactly:

"Microsoft.Synapse/workspaces/linkedServices"

not LinkedServices or any other casing. The sample structure should look like this:

{ "Microsoft.Synapse/workspaces/linkedServices": { "*": { "properties": { "typeProperties": { "connectionString": "|:-connectionString:secureString" } } } } }

A few additional checks:

Make sure the file is in the root of the collaboration branch, not only in the publish branch.

Check the actual linked service JSON and confirm the connection string is really at:

properties.typeProperties.connectionString

Some linked services store the value differently, for example under parameters, Key Vault references, or encrypted credentials.

If the connection string is parameterized inside the linked service itself using @{linkedService().parameterName}, then the ARM parameter file may not show the actual updated connection string value. In that case, check whether the linked service parameter default value is being generated instead.

Try a simple test by adding a clearly visible property such as baseUrl, accountName, or server depending on the linked service type. If no linked service properties are generated at all, Synapse is not reading the custom file.

If possible, paste only the linked service section from your template-parameters-definition.json and one sanitized linked service JSON. The issue is usually easier to identify by comparing the JSON path.