title: Trigger status update at the time of ADF deployment
body: <p>I am deploying the ADF ARM template from DEV instance to PROD using Azure DevOps pipelines.</p>
  <p>For the deployment below are the steps I followed.
  <a href="https://i.stack.imgur.com/OOhSM.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/OOhSM.png" alt="enter image description here" /></a></p>
  <ol>
  <li>Scripts provided by Microsoft to stop the triggers before deployment</li>
  <li>ARM template deployment</li>
  <li>Scripts provided by Microsoft to start the triggers and delete the resources not in the JSON file.
  under the header <strong>Sample pre- and post-deployment script</strong> in below page
  <a href="https://docs.microsoft.com/en-us/azure/data-factory/continuous-integration-deployment" rel="nofollow noreferrer">https://docs.microsoft.com/en-us/azure/data-factory/continuous-integration-deployment</a></li>
  </ol>
  <p>I do have around 20 triggers in which 15 are in running state and 5 are stopped for a while in PROD.
  In my DEV instance all triggers are in stopped status in order to avoid unnecessary pipeline runs.
  But at the time of deployment into PROD I need to set status of 15 out of 20 triggers as Started.</p>
  <p>To achieve this I have added the runtimeState of triggers in template parameterization and now I could select the trigger status from Override Parameters Option in the ARM Template Deployment task as below.
  <a href="https://i.stack.imgur.com/y77cA.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/y77cA.png" alt="enter image description here" /></a></p>
  <p>Now the issue is after PROD deployment, All triggers are in <strong>Stopped</strong> status only as in DEV instance.</p>
  <p>Eventhough the runtimeState is overwritten at the time of deployment, it is not reflecting in the PROD instance after deployment.</p>
  <p>After my analysis, I suspect the issue is with start trigger script from Microsoft is referring the <strong>ARMTemplateForFactory.json</strong> file from DEV where status of all triggers are stopped.
  <a href="https://i.stack.imgur.com/jhn5P.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/jhn5P.png" alt="enter image description here" /></a></p>
  <p>How to resolve this? I have to update the trigger status of each trigger job at the time of deployment from DEV to PROD.</p>
  <p>In the script to STOP/START triggers from Microsoft, it is getting list of triggers to be started from Json file which we get from DEV instance through build pipeline. The overwritten pipeline status will not be taken to start the triggers.
  <a href="https://i.stack.imgur.com/9b41T.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/9b41T.png" alt="enter image description here" /></a></p>
  <p>One of the solution I found was to <strong>start</strong> the triggers explicitly after the ARM deployment. For that I found an agent job as shown below.
  <a href="https://i.stack.imgur.com/55XSh.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/55XSh.png" alt="enter image description here" /></a></p>
  <p>But the Issue with this job is I am not able to provide name of multiple triggers at a time. I am able to provide name of a single trigger as shown below.<a href="https://i.stack.imgur.com/kxgOH.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/kxgOH.png" alt="enter image description here" /></a></p>
  <p>Is there any way to add multiple trigger name in this job?</p>