Views:

Applies to Product – Microsoft Dataverse


What’s happening?
Cloud flows are not triggering as expected when initiated from users in child business units, despite the users being the owners of the cloud flows.


Reason:
This arises due to the ownership and permissions associated with the cloud flows and the records. Users in different business units may not have the necessary security roles or permissions to trigger flows that are owned by users in another business unit.


Resolution:

  1. Confirm that the cloud flow can be triggered from the user in the parent business unit.
  2. Verify that users in the child business unit cannot trigger the cloud flow.
  3. Ensure that the appropriate security roles are assigned to users in the child business unit to allow them to trigger the cloud flow. 
  4. If applicable, set and assign permissions for the table, record, or flow to the user in the child business unit (BU) to resolve the triggering issue.
  5. If necessary, refer to the documentation on Security concepts in Microsoft Dataverse - Power Platform to set the scope access for child business units.