CI/CD Devops in Synapse

Question

CI/CD Devops in Synapse

Nick Wong 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 335 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.
Nick Wong 175 Reputation points

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

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

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

@Nick Wong You can follow this by doing private message.
Nick Wong 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?

Your answer

Nick Wong 175 Reputation points

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

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

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

@Nick Wong You can follow this by doing private message.
Nick Wong 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?