Ability to publish flow wtih SERVICE ACCOUNT and Run with ELEVATED permisisons.

[Office365Guy]

If MS is promoting FLOW as successor of SharePoint Designer workflows, then it should have following capabilities

1. Allow FLOWS to be published by service account and to be consumed by all users. [Off-course this approach has drawback with current 50 flow limitation but I assume this would increase]
2. Allow certain action to be executed in context of the service account [which is used to publish the flow]

Hope this is considered!!

[Stephen]

It has always been possible run a flow with any type of account -- user account or service account. When you log into the Flow portal simply log in with the service account instead of the user account. This is common for enterprises that have the requirements you call out. Can you please specify the gap in the product that needs to be fixed to support your scenario?

[Dudditz]

Hi Stephan, does that mean the process to run a team flow as a  service account means to log into flow with the service account and create the flow under this account?  Also, is it possible to tranfer existing flows  to a service account?

Thanks

[Anonymous]

Even when my service account owns the flow, it still appears to come from
Microsoft Flow <maccount@microsoft.com>

[anka]

Hello,

I am seeking advice on the best practice on which account to use for building enterprise level Flow and Power BI apps. 

Scenario: We have a Flow that sends outbound emails using the account of the user who created the flow. What would happen if the person leaves the organization, how will the outbound emails o when the mailbox is no longer active? I know that in the 'Send Email' action a "From" account can be specified for sending an email, but is it a good practice to do so or should we have a dedicated account(with an attached mailbox) for flows?

The information I am seeking- 

1. In terms of best practice, should we be creating a dedicated service account for flows? If yes, should the flows created by users be shared with this service account so they can be managed using one account?

2. What license should be assigned to the service account, E3 or E5? Example,  I want to use the flow in conjunction with PowerBI.

3.  Should this account be assigned the global admin privileges? Example: If I want to use flow for provisioning teams, setting DLP and ADG governance policies through flow at the Azure level

Thank you,

[Brice235i]

Not sure why the status is "need info"... pretty obvious isn't it?  

Approval email notifications should have a sender address as your company...   e.g. "My Company - workflow"... not maccount@microsoft.com which doesn't look all that professional for an enterprise level workflow

[JSK]

---

I have the same questions as @anka 

1. In terms of best practice, should we be creating a dedicated service account for flows? If yes, should the flows created by users be shared with this service account so they can be managed using one account?

2. What license should be assigned to the service account, E3 or E5? Example,  I want to use the flow in conjunction with PowerBI.

Seems very expensive to have to license a service account at the E3 or E5 level to perform basic functions.

[rodmiddleton]

Having a flow run as a service account against Sharepoint would provide us with a security mechanism protecting items in that list from being modified via the web.  Right now we have to hide with a view that can be worked around or set permissions at an item level taking us to premium. 

[PamelaBeaudoin]

Is there any way to not have to log in as that account in order to "sign" the flow with the service account.

[Fumi]

I think this feature must be there for pro-development!

[ONYXJas]

Perhaps one solution would be the ability to designate a service account as the "Owner" or "Run-as user"?