Unanswered

How to move a personal flow into production

(0) Share

Report

Posted on by RickCloud

I've created two flows for end-users. When my password needed to be changed, the flows were no longer available to them, until I reset my connections within Power Automate. How do I modify this, such that the flows will no longer require my credentials in order to be available?

Categories:

Process mining

I have the same question (0)

All responses (9)

Answers (1)

Vaibhav S Jadhav 92 on at

Like (1)

Report

Re: How to move a personal flow into production

If you are using MS Dynamics CRM then follow below steps:
1)Create new solution
2)Add Flow into that solution.
3)Export the solution
4)Login to production CRM and Import the Exported solution there.
5)Make it active.

Another way is give access permissions to specific users with their user ID's might resolves the issue.

Thanks,
Vaibhav

Was this reply helpful? Yes No
ScottShearer 25,268 Most Valuable Professional on at

Like (1)

Report

Re: How to move a personal flow into production

@RickCloud

I agree with the solution provided by @VSJadhav but would like to add that you can simply use the "Send a Copy" feature as well. The users will be required to supply their own credentials.

Was this reply helpful? Yes No
RickCloud 13 on at

Like (0)

Report

Re: How to move a personal flow into production

We don't use Dynamics, I'm in Power Automate of Office 365. Also, as far as I know we only have one(1) environment. Should I talk with IT management to see about getting a production environment?

Was this reply helpful? Yes No
Jcook 7,781 Most Valuable Professional on at

Like (0)

Report

Re: How to move a personal flow into production

Hello @RickCloud

if you’re worried about the connections being tied to your account. I would get IT to create a Service account for those connections, obviously depending on the connections. But I use Service accounts for anything I can.

Was this reply helpful? Yes No
RickCloud 13 on at

Like (0)

Report

Re: How to move a personal flow into production

JCook, I think a service account is just what I need. I'll still be the only one who can edit it, right? Unless I give edit permissions to someone else. That would be the best I think.

Was this reply helpful? Yes No
RickCloud 13 on at

Like (0)

Report

Re: How to move a personal flow into production

Josh, once I have the service-account, how do I reassign my permissions to it? Also, when I deployed it, by sharing it with others, I used the option for the flow to use the individuals permissions.

Was this reply helpful? Yes No
Verified answer

Jcook 7,781 Most Valuable Professional on at

Like (1)

Report

Re: How to move a personal flow into production

Hi @RickCloud

To change the connections, you can go into edit flow, click the 3 dots on the connector and click create new connection. Also you will want to click on Run only users and choose which connection you would want everyone to use (service account)

Only people that are an owner of that flow will have access to use the connection.

Was this reply helpful? Yes No
RickCloud 13 on at

Like (0)

Report

Re: How to move a personal flow into production

Josh, yes that is what I'll do. Although, I'll have it set so that each user, will use their own connections, as the flow utilizes the users credentials to determine to whom to send an email(their manager).

My biggest worry was that, every time my password changes, I'd have to log in to PA and reset it. If I were to ever leave then they'd only be able to use the flow until my creds were deactivated. So, by assigning the beginning creds to a service account that never expires, that won't happen.

Thank you very much for your help.

Was this reply helpful? Yes No
Jcook 7,781 Most Valuable Professional on at

Like (0)

Report

Re: How to move a personal flow into production

Hey @RickCloud ,

Glad you found a solution!

Another note on connection password changes:

If your password changes, your connection will still work.

The token will expire if the connection is not used for 60 or 90 days consecutively. So as long as that connection is being used.

(unless your Azure AD is set to revoke all tokens when password is changed)

More details found here:

https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-configurable-token-lifetimes#token-lifetime-policies-for-refresh-tokens-and-session-tokens

Was this reply helpful? Yes No