Micro_Ken
I don't despair. I'm frustrated with what appears to be more and more frequent half-thought-out SaaS solutions.
Done the copy back, but in my opinion, it defies the point. If "a" in the benefits you stated is the intended objective then why does:
1.) The form creator who is also both an owner and a member of the destination group where the form is associated loose access to utilise the same form in an Automate function that was previously configured and working with said form prior to the move? Where is the collaboration logic there?
2.) Not quite as restrictive, but also when attempting to share the power automate the task with the group, the task is removed from the creator's list of tasks and is listed in a "shared with" tab. Shared with yourself..... great thinking out of the box there. 😉
For comparison, when moving a document from one library/site to another, the document ID link remains functional, as do any shared links, provided the users of those have permissions to both source and destination sites/libraries. Why is this behaviour not mimicked with forms?
Anyway, I digress. My problem is solved but the solution is less than intuitive and I've learned that thinking ahead and attempting to share a resource with other accounts for future flexibility (not tied to one account/object), is more trouble than its worth in my context at least.