Flow Owner Manager

A Power Platform ToolBox tool that updates the primary owner of cloud flows within a named solution — in one click. Flows can optionally be limited to those currently owned by a specified user.

What it does

1. Looks up a solution by its unique name in the active Dataverse connection
2. Finds all cloud flows (category 5 workflows) that belong to that solution
3. Optionally filters those flows by their current owner's Azure AD Object ID
4. Resolves the new owner by their Azure AD Object ID
5. PATCHes each workflow's ownerid field in Dataverse — correctly changing the primary owner, not just adding a co-owner

Why this is better than PowerShell

Power Automate's PowerShell modules don't expose a way to change the primary owner directly (Set-AdminFlowOwnerRole only adds co-owners). This tool bypasses that limitation by updating the Dataverse workflow record directly — the same operation the Power Platform admin centre uses internally — via the ToolBox's built-in Dataverse API.

Usage

1. Select your Dataverse connection in the ToolBox sidebar
2. Enter the Solution Unique Name (e.g. CSAT) — this is the Name field in the solution details, not the Display Name
3. Optionally enter the Azure AD Object ID of the current owner to limit the results to that user's flows, then click its Verify button to confirm the user
4. Enter the Azure AD Object ID of the new owner — found in Azure Portal → Microsoft Entra ID → Users → [user] → Object ID
5. Click Verify to confirm the new owner exists in this environment (optional but recommended)
6. Click Find flows to preview the flows that will be updated
7. Review the list, then click Update owners

After either user is successfully verified, its Verify button turns green and displays ✓ Verified. The indicator clears if the Object ID is edited or the active connection changes.

Prerequisites

• Power Platform ToolBox v1.2.0 or higher
• The new owner must have a Power Platform licence and must have logged into the target environment at least once (so their Dataverse systemuser record exists)
• Your ToolBox connection must have sufficient privileges to update workflow records (System Administrator or System Customizer role)

Development

# No build step required — plain HTML/CSS/JS
# Load directly in ToolBox via Debug → Load Local Tool

To use TypeScript and a build step:

npm install --save-dev @pptb/types typescript vite

Publishing

npm login
npm publish --access public

Then submit at powerplatformtoolbox.com/submit-tool.

License

MIT