CI/CD Devops in Synapse

Question

CI/CD Devops in Synapse

NickWong-8242 175

Hello,

I literally am not sure why this happens, I don't think there are anything wrong with my trigger to run pipeline in my synapse, in my production they are all running fine. but this just happens recently when we would like to make some changes in dev, Could you have a look into this? Without this, I am unable to push things into test and production. and I unwillingly would like to change anything in Prod LIVE synapse.

@cicdpipeline @S-AZ-AAES-SD-Synapse

User's image

Smaran Thoomu 35,870 Reputation points Microsoft External Staff Moderator

2026-08-17T12:52:39.37+00:00
Hi @Nick Wong
Thank you for providing the details and screenshot.

I understand that the issue is occurring in the Dev environment during the CI/CD deployment, while the corresponding triggers are working as expected in Production. We also understand that you would prefer not to make any changes directly in the Production Synapse workspace.

From the screenshot, the failure is occurring in the Azure Synapse Toggle Triggers task (v2.5.0) while the task is initializing the Synapse client:

Initializing SynapseClient...

Starting task...

##[error]Refer to above logs for more details.

At this stage, this does not appear to indicate that the trigger definition itself is incorrect. We would like to first determine whether the CI/CD task is able to authenticate and connect to the Dev Synapse workspace successfully.

Could you please provide the following information in private message so that we can investigate this further?

Complete raw log from the failed Toggle Triggers task. Please use View raw log and share the complete output around the failure.

Task inputs/configuration for the Toggle Triggers task. You can use View task inputs and share the relevant configuration, masking any secrets.

Dev Synapse workspace name/URL.

The Azure DevOps service connection being used by this task (please do not share any credentials/secrets).

Whether the same service connection is currently able to access the Dev Synapse workspace through other pipeline tasks.

Whether any changes were recently made to the Dev Synapse workspace, service connection, permissions/RBAC, networking/private endpoints, or pipeline configuration.

If possible, please provide the last successful pipeline run and the first failed run after the recent changes so that we can compare the executions.

Once we have the raw log and task inputs, we can determine whether the failure is related to the DevOps task, authentication/service connection, Synapse workspace access, networking, or the trigger operation itself.

There is no need to make any changes to the Production Synapse workspace while we investigate the Dev environment.
NickWong-8242 175 Reputation points

2026-08-17T15:15:10.07+00:00

Hello @smaran, how do i reply to your message privately please?
Smaran Thoomu 35,870 Reputation points Microsoft External Staff Moderator

2026-08-17T17:15:10.4066667+00:00

@Nick Wong You can follow this by doing private message.
NickWong-8242 175 Reputation points

2026-08-17T17:15:40.3966667+00:00

@Smaran Thoomu Hello,

I think i may know the issue is, I remember that we renewed the Personal token underthe library. and could be somewhere else in keyvault not updated probably for this will affect the trigger?
Smaran Thoomu 35,870 Reputation points Microsoft External Staff Moderator

2026-08-18T07:38:08.8633333+00:00
Hi @Nick Wong

Yes, that could potentially explain the recent behavior, especially if the renewed Personal Access Token is being referenced by the pipeline through a variable, Key Vault secret, or another credential configuration used by the Dev deployment.

Since the Toggle Triggers task is failing during the Synapse client initialization, we should verify whether the updated token has been propagated to all the locations where the Dev pipeline is consuming it.

Could you please check the following:

Confirm where the renewed PAT is stored/used for the Dev pipeline.

If the PAT is stored in an Azure DevOps Variable Group, confirm that the value has been updated there.

If the variable group references an Azure Key Vault secret, please verify that the corresponding Key Vault secret was also updated with the renewed token.

Check whether the pipeline is using a different variable/secret for the Toggle Triggers task than the one you updated.

Please verify that the Dev pipeline is actually consuming the latest value from the variable group/Key Vault.

After confirming the credential locations, please rerun the Dev pipeline and let us know whether the Toggle Triggers task succeeds.

If it still fails, please share the updated raw log from the failed Toggle Triggers task, and we can continue investigating the authentication/Synapse connection path.

There is no need to make any changes to the Production Synapse environment while we troubleshoot the Dev pipeline.
NickWong-8242 175 Reputation points

2026-08-18T09:52:33.7666667+00:00

Hi Smaran,

I dont have a private message button to reply you? or Team message if you are able to find my email address
Smaran Thoomu 35,870 Reputation points Microsoft External Staff Moderator

2026-08-18T12:52:03.6666667+00:00

@NickWong-8242 Could you check it again and let me know if you still can’t see the private message?
Dr Marziyeh Bahrami 0 Reputation points

2026-08-18T12:57:16.2233333+00:00
Hello,

Thank you for reporting this issue.

From the information provided, it looks like the problem is isolated to the Dev Synapse environment, since the same triggers and pipelines are running successfully in Production. This indicates that the pipeline trigger definition itself may not be the root cause.

We will investigate the following areas in the Dev Synapse workspace:

Trigger status and configuration

Verify that the trigger is enabled and correctly associated with the expected pipeline.

Compare the Dev trigger JSON/configuration with the working Production version.

Git / CI-CD synchronization

Confirm whether the latest changes are properly published from the collaboration branch.

Check whether the trigger exists in the published/live mode and not only in the development branch. Azure Synapse CI/CD deployments can sometimes have differences between the collaboration workspace and the live artifacts.

Linked services and Integration Runtime dependencies

Validate that all referenced linked services, datasets, and Integration Runtime names are identical between environments.

Environment-specific differences (for example, Integration Runtime naming or configuration mismatches) can cause triggered executions to fail even when manual/debug runs work.

Trigger execution logs

Review the Monitor hub in Synapse and collect:
- Trigger run history - Pipeline run ID - Error details - Activity-level failure logs

We understand that you do not want to make any changes directly in the Production Synapse environment. We will avoid any production modification and focus only on identifying the issue in Dev so the changes can safely move through the normal Dev → Test → Production deployment process.

Answer recommended by moderator

0 additional answers

Your answer

NickWong-8242 175 Reputation points

2026-08-17T15:15:10.07+00:00

Hello @smaran, how do i reply to your message privately please?
Smaran Thoomu 35,870 Reputation points Microsoft External Staff Moderator

2026-08-17T17:15:10.4066667+00:00

@Nick Wong You can follow this by doing private message.
NickWong-8242 175 Reputation points

2026-08-17T17:15:40.3966667+00:00

@Smaran Thoomu Hello,

I think i may know the issue is, I remember that we renewed the Personal token underthe library. and could be somewhere else in keyvault not updated probably for this will affect the trigger?
Smaran Thoomu 35,870 Reputation points Microsoft External Staff Moderator

2026-08-18T07:38:08.8633333+00:00

Hi @Nick Wong

Yes, that could potentially explain the recent behavior, especially if the renewed Personal Access Token is being referenced by the pipeline through a variable, Key Vault secret, or another credential configuration used by the Dev deployment.

Since the Toggle Triggers task is failing during the Synapse client initialization, we should verify whether the updated token has been propagated to all the locations where the Dev pipeline is consuming it.

Could you please check the following:

Confirm where the renewed PAT is stored/used for the Dev pipeline.

If the PAT is stored in an Azure DevOps Variable Group, confirm that the value has been updated there.

If the variable group references an Azure Key Vault secret, please verify that the corresponding Key Vault secret was also updated with the renewed token.

Check whether the pipeline is using a different variable/secret for the Toggle Triggers task than the one you updated.

Please verify that the Dev pipeline is actually consuming the latest value from the variable group/Key Vault.

After confirming the credential locations, please rerun the Dev pipeline and let us know whether the Toggle Triggers task succeeds.

If it still fails, please share the updated raw log from the failed Toggle Triggers task, and we can continue investigating the authentication/Synapse connection path.

There is no need to make any changes to the Production Synapse environment while we troubleshoot the Dev pipeline.
NickWong-8242 175 Reputation points

2026-08-18T09:52:33.7666667+00:00

Hi Smaran,

I dont have a private message button to reply you? or Team message if you are able to find my email address
Smaran Thoomu 35,870 Reputation points Microsoft External Staff Moderator

2026-08-18T12:52:03.6666667+00:00

@NickWong-8242 Could you check it again and let me know if you still can’t see the private message?
Dr Marziyeh Bahrami 0 Reputation points

2026-08-18T12:57:16.2233333+00:00

Hello,

Thank you for reporting this issue.

From the information provided, it looks like the problem is isolated to the Dev Synapse environment, since the same triggers and pipelines are running successfully in Production. This indicates that the pipeline trigger definition itself may not be the root cause.

We will investigate the following areas in the Dev Synapse workspace:

Trigger status and configuration

Verify that the trigger is enabled and correctly associated with the expected pipeline.

Compare the Dev trigger JSON/configuration with the working Production version.

Git / CI-CD synchronization

Confirm whether the latest changes are properly published from the collaboration branch.

Check whether the trigger exists in the published/live mode and not only in the development branch. Azure Synapse CI/CD deployments can sometimes have differences between the collaboration workspace and the live artifacts.

Linked services and Integration Runtime dependencies

Validate that all referenced linked services, datasets, and Integration Runtime names are identical between environments.

Environment-specific differences (for example, Integration Runtime naming or configuration mismatches) can cause triggered executions to fail even when manual/debug runs work.

Trigger execution logs

Review the Monitor hub in Synapse and collect:
- Trigger run history - Pipeline run ID - Error details - Activity-level failure logs

We understand that you do not want to make any changes directly in the Production Synapse environment. We will avoid any production modification and focus only on identifying the issue in Dev so the changes can safely move through the normal Dev → Test → Production deployment process.

Answer 1

NickWong-8242 175

Hi @Dr Marziyeh Bahrami

We found the problem now, apparently we need to rotate the clients secret but not sure why people managing our azure didnt receive the notification at all, glad that I spoke to my colleage to try things in our SQL database for pull request, it failed as well. but under the pipeline in SQL database it provides us a clear answer of the client secret error needs to be rotated, and it is relevant to the DARPAC accoridng to the failure log, i have been waiting for some who is responsible for this, as soon as this problem is sorted. I wil provide tou a clear pic.

Thank you once again

Smaran Thoomu 35,870 Reputation points Microsoft External Staff Moderator

2026-08-18T17:45:14.2066667+00:00

Hi @NickWong-8242

Thank you for the update. Glad to hear that you were able to identify the issue.

Based on your findings, the failure appears to be related to the client secret rotation for the DARPAC account.

Once the client secret has been rotated and the updated secret is propagated to the required pipeline/Key Vault configuration, please rerun the Dev pipeline and confirm whether the Toggle Triggers task is successful.

If the pipeline succeeds after the rotation, please let us know so we can confirm the issue is resolved and proceed with the case closure.

We will wait for your confirmation and the details once the change is completed.