Skip to content

Starting blob event trigger results in Resource cannot be updated during provisioning #474

@mikkosulonen

Description

@mikkosulonen

Describe the bug
A clear and concise description of what the bug is.
Starting an event based trigger as a part of GitHub action deploying results in:

STEP: Starting triggers...
TriggerStartMethod = BasedOnSourceCode
The number of triggers to start: 9
Starting triggers:
- Enabling trigger: Event_source_system_file_name
   Tenant: ***
SubscriptionName SubscriptionId                       Account
---------------- --------------                       -------                  
<subscription_name>     *** <subcription/tenant/ids>-…
Start-AzDataFactoryV2Trigger: /home/runner/.local/share/powershell/Modules/azure.datafactory.tools/1.14.0/private/Start-Trigger.ps1:17
Line |
  17 |              Start-AzDataFactoryV2Trigger `
     |              ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | HTTP Status Code: BadRequest Error Code: BadRequest Error Message:
     | Resource cannot be updated during provisioning Request Id:
     | <id> Timestamp (Utc):12/17/2025 11:10:47

To Reproduce
Your script to reproduce the behaviour:

Create a "on blob created" event trigger.
Deploy it.
(try to) Start it.

Expected behaviour
A clear and concise description of what you expected to happen.
Defined and deployed event trigger is BOTH deployed AND started succesfully.

Screenshots
If applicable, add screenshots to help explain your problem.

Version of PowerShell module of:

  • 1.14.0

Provide all files to reproduce the issue

  • Attach at least log file (you can wipe out any potentially sensitive info)
  • Attach files of objects which are involved in the process

Metadata

Metadata

Assignees

No one assigned

    Labels

    triageIssue is under investigation

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions