Forum Discussion
Flow - System Account?
- Jan 21, 2019
Hi,
Unfortunately it´s requiring a license but Flow-license is free to use.
If you don´t want it to be on your account you need to have a licensed system-account.
It also depends on what you want to do, if you need to have connections towards sharepoint, mail etc you´ll also need a license for Exchange, sharepoint etc.
This is a good question. What would Microsoft recommend as a best practice? In my situation I have a Flow that I created. It's basically scheduled to run about 4 or 5 times a day that will grab an excel document and email that document. Not a document that I really care about but a business process that needed to be set up to send the spreadsheet out to a client through out the day. The issue I have is that that document shows up in my Most Recommended Documents section on the Office.com site and the site always shows up as a frequent site. Which then kind of takes away from documents or sites that I really care about. What would be a good way to handle that so that it's not showing up in my recent docs or frequent sites? Anyone have the same issue?
Yes Rich Koneval that's my point. I can setup flows but they're not necessarily personal to me and should be able to run even if was to leave the company.
If they're designed for personal use that's fine but it leaves a gap for other automation/data collection.
- sbuccimsftJun 17, 2019
Microsoft
DaithiG as far as the "what if I leave the company" scenario, these are Flows you should share with someone else so they move under Team Flows.
- Robin NilssonFeb 01, 2019Bronze Contributor
This is my exact frustration with Flow as well. I'm coming from a SharePoint background, and I'm used to having workflows run in the context of the user that sets them off. I can create them but everyone uses them and any activity shows under their name.
Flow wasn't designed that way I guess, since it's more of a cloud-y product and keeps all of it's diverse connectors internal to itself. It authenticates with those internal connections - It doesn't 'run' under a 'Flow Service Account' that just automatically exists and authenticate with the current user.