A parent cloud flow in a solution fails at its Run a Child Flow action with an error stating that the flow can't be used as a child workflow because child workflows only support embedded connections. The child flow uses the SharePoint and Office 365 Outlook connectors. What should the developer change?
Select an answer to reveal the explanation.
Short Explanation
A child flow has to bring its own keys; it can't borrow the parent's. Set its Run only users connections to Use this connection, and you'll see the embedded-connection error go away. The trap is trying to pass connections down from the parent, which just isn't supported.
Full Explanation
A child flow runs with the connections embedded in it. When a flow uses connectors other than the built-in actions and the Microsoft Dataverse connector, Microsoft's guidance is to open the child flow's properties, edit the Run only users settings, and for each connection select Use this connection rather than Provided by run-only user. If any connection is left as provided by the run-only user, the parent cannot invoke the child, and the run fails with the embedded-connections error described in the scenario. Connections cannot currently be passed from a parent flow to a child flow, so changing the parent's run-only settings has no effect on the child and does not let it inherit anything. Child flows must be in a solution for the Run a Child Flow action to list them; moving the child into My flows removes it from the action's picker entirely rather than solving the connection issue. Swapping the trigger for an HTTP request trigger abandons the child flow pattern; it introduces environment-specific URLs, a premium connector, and separate authentication without addressing why the original call failed. Exam caveat: built-in actions and the Dataverse connector do not need this change, which is why a child flow that only uses Dataverse may work without it. Operational check: after updating the run-only settings, rerun the parent flow and confirm the child flow's run appears in its own history as successful.