Answered

Power Automate Service Account Setup for On‑Prem SQL to SharePoint

(0) Share

Report

Posted on by CU28031555-0

Hello

We are planning to import data from an on‑premises SQL Server into a SharePoint List using Power Automate. An On‑Premises Data Gateway is already installed and configured.

We are trying to understand the best practice for creating and using a service account for the Power Automate flow and have the following questions:

Should the Power Automate service account be created as a domain account synchronized to Azure Entra ID?
Should the power automate premium license be assigned to the service account as we would need SQL connector?
Should the service account be used as the flow owner, including logging in to https://make.powerautomate.com to build and manage the Power Automate flows?
If the service account is required to sign in to the Power Automate portal, should it be created as an interactive or non‑interactive account?

Thanks in advance.

Categories:

Building flows

Using flows

I have the same question (0)

All responses (2)

Answers (1)

Sort by

Verified answer

chiaraalina 2,036 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hi

1. Yes. The service account should be a normal domain user that’s synchronized to Microsoft Entra ID. Power Automate requires a work/school Azure AD identity to sign in and run flows. In a hybrid environment, creating it as an on-prem AD account and syncing it via Azure AD Connect is a common practice.

2. Yes. You will need to license the service account for premium connectors (or license the flow itself) in order to use the SQL Server connector through the on-premises data gateway. The SQL connector is a premium connector.

3. Yes. It’s a best practice for longevity and manageability. You should either build the flow under the service account (by logging in as that account when creating the flow) or transfer ownership of existing flows to that account. By having a dedicated service account own the flow, you ensure the flow won’t be tied to an individual’s personal account, so the automation won’t break if that person leaves or changes roles. I would add an additional owner as well.

4. If the service account needs to log in to the Power Automate portal (make.powerautomate.com) to create or manage flows, it must be a regular interactive user account. In other words, it should have a password and the ability to sign in like any normal user.

Hope it helps!

Was this reply helpful? Yes No
Suggested answer

CU28031555-0 4 on at

Like (0)

Report
Copy link

Link copied!

Appreciate your response. Thank you.

Was this reply helpful? Yes No