Change publisher for Flow

(2) Share

Report

Posted on by Greg Prickril

157

Create several Solutions before I understood concept of publisher. They each have their own!

Will be providing solutions to clients so want all out stuff to have same publisher. Created new solutions with new publisher. Can add flows, but they'll still show original publisher.

Gemini tells me only way to change publisher at Flow level is to edit the JSON (import/export). That is freaking crazy but not surprising on this platform.

Can anyone confirm? Maybe unzip and do a global search/replace on prefix?

Wouldn't surprise me if GenAI and I don't understand all the wrinkles.

Categories:

Building flows

I have the same question (0)

All responses (3)

Answers (1)

Sort by

Suggested answer

Robu1 1,671 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi Greg Prickril ,

Thank you for choosing Microsoft Community.

You instincts are right. Microsoft does not support changing a Flow’s publisher or prefix. You cannot change the publisher of an existing flow inside a solution.

The only way is to export the solution, edit the JSON, and re‑import it — or recreate the flow inside a solution that already uses the correct publisher.

I hope this helps resolve the issue! If you need more specific guidance, feel free to ask.

🏷️ Please tag me @Robu1 if you still have any queries related to the solution or issue persists.

✅ Please click Accept as solution if my post helped you solve your issue and help others who will face the similar issue in future. ❤️ Please consider giving it a Like, If the approach was useful in other ways.

Happy to help

Robu 1👩‍💻

Was this reply helpful? Yes No
Verified answer

Greg Prickril 157 on at

Like (0)

Report
Copy link

Link copied!
Thanks @Robu1 (is there some trick to tagging?),
Claude just told me this:

Corrected process:

Create a solution under the desired publisher

Add the flow to that solution

Export that solution (.zip)

Import the .zip into the target environment

The flow arrives in the target environment associated with whatever publisher owned the solution in the .zip. There's no nesting of solutions — it's one solution, one publisher, imported into one environment.

Is this true? Would also like insight as to whether I should care about this for distributing Solutions to clients. Seems a very trivial thing for Flows. However, would like to fix it now rather than later (when I discover some obscure show-stopper).

Was this reply helpful? Yes No
Robu1 1,671 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Claude is correct Greg Prickril — importing into a new environment applies the solution’s publisher. Your dev environment will NOT change unless you rebuild or JSON‑edit. Clients will receive clean, consistent publishers if you export from the right solution. Flows are low‑risk, but it’s smart to fix this early for long‑term ALM best practice.

No trick to tagging -I simply copied and pasted your hyperlinked name directly from your message.

Tagging you the usual way @Greg Prickril has not worked as it should (doesn't save)- This is a known issue/bug.

Was this reply helpful? Yes No