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


Report
All responses (
Answers (