Other Users Unable to Run My Flow

[Wake90]

Hello,

I've created a cloud flow that is pretty simple that it checks the OneDrive's Recordings folder for any new mp4 files, and recreates them on a SharePoint page that is linked to a Teams channel. I added other members as owners, and it never ran for them despite them having access to their own source OneDrive site and the SharePoint destination. During testing documented no signs that it attempted to trigger at all. There doesn't appear to be an option to give permission to Run As type membership that I see many talking about giving.

I checked, and the problem persisted despite being on a production type environment. I believe the connections are supposed to allow for full access and capabilities if others are given access to the resource, and even when I tried to make it a Service Principle App it I couldn't search for it to share it that way.

I believe this may be a licensing issue. My company has a great deal of licenses named Microsoft Power Automate Free. I've read about a free trial, but I don't know how that applies to me in my situation. I've never seen anything about trial from Power Automate in my search for an answer to this issue.

The other possibility is that I've configured the program to only work for me, but the template that I adjusted to make this flow to move created files from OneDrive to a SharePoint page should apply to all the same way and not only work for me.

Any input is appreciated.

[ScottShearer · Accepted solution]

@Wake90 

I suggest that you use the "Send a copy" feature and send each potential user a copy of the Flow.  They can then use the template to create the same Flow for themselves using their connection info and OneDrive.

Your base issue is that even though you have made other people owners, your connection info is still being used.

[Wake90]

Thanks for making me aware of this. I was successful at having users use the Save function on the flow to copy it to their personal Cloud Flows section instead of trying to use mine in the Shared With Me section, then having them specify their own OneDrive folder within the flow.

I think this is close to what you were advising in your response. I didn't want to have users having to program their own flow. Things would get pretty confusing for them. 

It's in working order on all of my testing. I appreciate your help.