Azure Data Factory: How to stop/start triggers in ADF environments using CI/CD release pipeline?

Question

Azure Data Factory: How to stop/start triggers in ADF environments using CI/CD release pipeline?

Reyshma Sekar 20

We would like to stop all triggers in our dev ADF environment after deploying to production. I've seen the below script being used:

task: AzurePowerShell@4 displayName: 'Data Factory: Stop all triggers'

inputs: azureSubscription: '${{ parameters.connection }}'

ScriptType: InlineScript

Inline: | $triggers = Get-AzDataFactoryV2Trigger -ResourceGroupName ${{ parameters.resourcegroupName }} -DataFactoryName ${{ parameters.dataFactoryName }} -ErrorAction SilentlyContinue

if($triggers)

{ for each($trigger in $triggers)

{ Stop-AzDataFactoryV2Trigger -ResourceGroupName ${{ parameters.resourcegroupName }} -DataFactoryName ${{ parameters.dataFactoryName }} -Name $trigger. TriggerName -Force } }

azurePowerShellVersion: latest version

When I break it down and run Get-AzDataFactoryV2Trigger, it returns all the triggers in my data factory but when running Stop-AzDataFactoryV2Trigger, it returns true but when checking in ADF, the trigger is not stopped. I tried to run these commands in the release pipeline using Azure Powershell and, in the portal, using Azure CLI. confirmed the right subscription is being used.

Confirmed that the DataFactory Contributor role is set for the dev resource group and other permissions are set up for the subscription and resource group.

What else can I try? Has anyone had this issue before?

Chandra Boorla 15,480 Reputation points Microsoft External Staff Moderator

2025-01-30T21:23:14.91+00:00
Hi @Reyshma Sekar

Greetings & Welcome to Microsoft Q&A forum! Thanks for posting your query!

It seems like the PowerShell script you're using to stop all the triggers in your Azure Data Factory (ADF) environment is almost there, but there could be a couple of reasons why it’s not reflecting in the portal despite returning True.

To stop all triggers in your Azure Data Factory (ADF) environment using a CI/CD release pipeline, the script you provided appears to be correct in its structure. However, if the triggers are not stopping as expected, consider the following troubleshooting steps:

Check Trigger Status - After running the Stop-AzDataFactoryV2Trigger command, ensure that you are checking the status of the triggers correctly. You can use Get-AzDataFactoryV2Trigger to verify if the triggers are indeed stopped.

Permissions - Confirm that the Azure account being used has sufficient permissions. You mentioned that the DataFactory Contributor role is set but ensure that there are no additional role assignments or policies that might restrict the stopping of triggers.

Execution Context - Make sure that the script is running in the correct context. If you are using Azure DevOps, verify that the pipeline is configured to use the correct Azure subscription and that the service connection has the necessary permissions.

Error Handling - Since you are using -ErrorAction SilentlyContinue, consider removing this parameter temporarily to see if any errors are being suppressed that could provide insight into why the triggers are not stopping.

Azure PowerShell Version - Ensure that you are using the latest version of Azure PowerShell in your pipeline, as older versions may have bugs or lack features that could affect the execution of your commands.

Manual Testing - As a last resort, try running the commands manually in the Azure PowerShell console to see if they work outside of the pipeline context. This can help isolate whether the issue is with the script itself or with the pipeline execution.

Please refer the following documentations for more details:

Sample pre- and post-deployment script

Automate continuous integration using Azure Pipelines releases

I hope this information helps. Please do let us know if you have any further queries.

Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.

Thank you.
Chandra Boorla 15,480 Reputation points Microsoft External Staff Moderator

2025-01-31T19:11:21.9266667+00:00

@Reyshma Sekar

Just checking in to see if the below answer provided by @ Sina Salam helped.

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.

Answer accepted by question author

0 additional answers

Your answer

Chandra Boorla 15,480 Reputation points Microsoft External Staff Moderator

2025-01-31T19:11:21.9266667+00:00

@Reyshma Sekar

Just checking in to see if the below answer provided by @ Sina Salam helped.

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.

Answer 1

Hello Reyshma Sekar,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

I understand that you would like to stop/start triggers in ADF environments using CI/CD release pipeline in Azure Data Factory.

Instead of generic troubleshooting for common issues, since Stop-AzDataFactoryV2Trigger returns True but does not actually stop the triggers, the root cause was limited to these four areas:

Triggers Are in a Queued or Inactive State
Some triggers are linked to pipelines that need explicit stopping.
If using an older version, this could be a known issue.
If an ARM policy enforces a specific trigger state, it may automatically restart or prevent the stop command from taking effect.

Therefore, my best practice advice to resolve your issue are the followings:

Use the Azure REST API to Stop Triggers:

      $accessToken = (Get-AzAccessToken -ResourceUrl "https://management.azure.com").Token
      $resourceGroupName = "<Your_ResourceGroup>"
      $dataFactoryName = "<Your_DataFactory>"
      $triggers = Get-AzDataFactoryV2Trigger -ResourceGroupName $resourceGroupName -DataFactoryName $dataFactoryName
      foreach ($trigger in $triggers) {
          $triggerName = $trigger.TriggerName
          $url = "https://management.azure.com/subscriptions/<your_subscription_id>/resourceGroups/$resourceGroupName/providers/Microsoft.DataFactory/factories/$dataFactoryName/triggers/$triggerName/stop?api-version=2018-06-01"
          Invoke-RestMethod -Uri $url -Method Post -Headers @{Authorization="Bearer $accessToken"} -ContentType "application/json"
          Write-Output "Stopping trigger: $triggerName"
      }

Verify Trigger State:

   Get-AzDataFactoryV2Trigger -ResourceGroupName $resourceGroupName -DataFactoryName $dataFactoryName | ForEach-Object {
     $_.Properties.RuntimeState
      }

Check for Auto-Restart Policies:
1. In the Azure Portal, check the trigger settings for any auto-restart policies.
2. Ensure that triggers are not linked to pipelines with Start on Completion dependencies.

Update Azure PowerShell Module:

      Update-Module -Name Az -Force
      (Get-Module -Name Az).Version

This will resolve the issue.

I hope this is helpful! Do not hesitate to let me know if you have any other questions.

Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful.

Reyshma Sekar 20 Reputation points

2025-01-31T15:35:32.3833333+00:00

Hi Sina, thank you so much for your response, it is super helpful, and the explanation matches the problem I am having. I am running into an issue with using the 'POST' method, it is returning an error "

Response status code does not indicate success: 405 (Method Not Allowed).

". Do you have any ideas on what permissions to check or what else I can do?
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.