web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Ownership Best Practices
Power Automate
Unanswered

Ownership Best Practices

(0) ShareShare
ReportReport
Posted on by

Hello,

 

So currently we're encountering an issue where the person who creates the Power Automate Workflow or is the person who deploys the workflow into a specific environment is the person who shows up in email steps, in dynamics etc. For instance if the flow sends an email out, the email will be as if the person who deployed the flow in the environment sent the email. Or if the flow updates a field in Dynamics, it will show the person who deployed the flow has updated the field in dynamics even though it was the flow that did it not the person. Is there a best practice to get around this? I've talked to people about using Service accounts but our network/security guys have pushed back on using service accounts because they don't want multiple people to have access to an account. Is there a way to get around the Power Automate workflows taking the creator or deployer of the flow and using them in email steps etc?

 

Thanks for your help

Categories:
I have the same question (0)
  • Masa_ Profile Picture
    48 on at

    Hi, @naflosi 
    The account connected to the flow action can only be selected from the flow edit screen and cannot be changed to the user who dynamically triggered the flow.

    One workaround is that if the number of people who perform the flow is small and fixed, the person who created the flow sends the flow to the person who executes the flow with [Send Copy], and then the flow is executed. There is a way to have the flow of the executor's account imported and change the account that connects to the action to the executor of the flow.

    2021-02-27_11h12_15.png

     

    However, I don't think this workaround is suitable for this scenario.
    --------------------------------
    Another workaround is to leave the account connected to the flow action as it is, but triggers such as Forms, SharePoint, PowerApps can get the name of the user who triggered it, so put that user's name in the body of the email It is a method to output to the column to be added by or dynamics.
    (The default updater column for email senders and dynamics is not the user who triggered the flow I need guidance to the user)


    I used google translate.
    Regards,
    --------------------------------
    If I have answered your question, please mark your post as Solved.
    If you like my response, please give it a Thumbs Up.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Leaderboard > Power Automate

#1
trice602 Profile Picture

trice602 398 Super User 2025 Season 2

#2
David_MA Profile Picture

David_MA 323 Super User 2025 Season 2

#3
Expiscornovus Profile Picture

Expiscornovus 183 Most Valuable Professional

Last 30 days Overall leaderboard