Skip to content

The flow runs on a colleague's account, is that a problem?

Production flows on personal accounts are fragile. On departure, password change, MFA reset, or vacation the flow stalls. Service accounts are the only right route for business flows.

Try this first

  1. 1Create a dedicated service account in Microsoft 365 / Google Workspace, e.g. automation-flows@company.nl. Strong password and MFA with a shared TOTP.
  2. 2Grant only needed permissions: Mail.Send for the mail flow, Sites.Read for the SharePoint flow. Not 'global admin'.
  3. 3Migrate flows one by one to the service account: re-bind OAuth, test, then remove the old.
  4. 4Store credentials in a shared vault (1Password Business, Bitwarden). They survive a personal departure.
  5. 5Document in a sheet: which flow runs on which service account, who owns it. Audit question gets a 1-minute answer.

When to bring us in

Got flows on personal accounts and an upcoming departure, migration is priority. We can write the runbook.

See also

None of the above fits?

Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.

Who are you?

For the AI question we need your email and company, so we can follow up if the AI gets stuck, and to prevent abuse.

Limited to 2 questions per hour and 5 per day, kept lean so the AI stays useful. For more, contacting us directly works better for you and us.

Or skip the DIY entirely

Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.