You manage a SharePoint site that uses Power Automate flows. When the person who created a flow leaves your team, the flow may stop working because its connections are tied to that person’s account. Moving a flow’s connections to a service account prevents these failures and keeps your automations running.
A service account is a dedicated user identity used only for automated processes. Power Automate lets you reassign connections to a different owner without rebuilding the flow from scratch.
This article gives you a practical checklist for moving a flow connection to a service account. Each step covers the exact actions you need to take in the Power Automate interface and the SharePoint admin center.
Key Takeaways: Moving Flow Connections to a Service Account
- Power Automate > My flows > Flow details > Edit connections: Change the owner of existing connections from a user account to the service account.
- Service account must have a Power Automate license: Without a license, the flow cannot be owned or run by the service account.
- SharePoint site permissions for the service account: The service account needs at least Contribute access to any SharePoint site the flow interacts with.
Why You Need a Service Account for Flows
When a user creates a flow, Power Automate stores the connections under that user’s identity. Connections include SharePoint, Outlook, Teams, and any third-party services the flow calls. If the user’s account is disabled or deleted, the connections break and the flow fails.
A service account solves this problem because it is not tied to a single employee. The account remains active as long as your organization exists. Flows owned by the service account continue running even when the original creator leaves.
Service accounts also simplify auditing. You can track all automated actions to one identity instead of sorting through multiple user accounts.
Prerequisites Before You Start
Before you move any flow connections, confirm these three requirements are met.
Service Account Must Have a Power Automate License
Power Automate requires a license for each user who owns a flow. In the Microsoft 365 admin center, assign a Power Automate plan to the service account. The free Microsoft 365 license does not include Power Automate. Use a Power Automate per-user plan or a per-flow plan depending on your needs.
Service Account Needs SharePoint Access
If your flow reads or writes data to a SharePoint list or library, the service account must have access to that site. Add the service account to the site’s permissions with at least the Contribute level. Do not use Full Control unless the flow requires it.
Service Account Must Be a Member of the Flow’s Environment
Power Automate organizes flows into environments. The service account must be added as a member of the environment where the flow lives. Go to the Power Platform admin center, select Environments, choose your environment, and add the service account as a member with the Environment Maker or System Customizer role.
Checklist: Move a Flow Connection to a Service Account
Follow these steps in order. Do not skip any step or the flow may break.
- Sign in to Power Automate as an owner of the flow
Open https://make.powerautomate.com and sign in with an account that has co-owner or owner permissions on the flow. If you only have run-only permissions, you cannot change connections. - Locate the flow you need to move
Select My flows from the left navigation. Use the search box to find the flow by name. Click the flow name to open its details page. - Open the connections list
On the flow details page, select Edit under the Connections section. A panel opens showing every connection the flow uses, such as SharePoint, Outlook, or SQL Server. - Change the owner of each connection
For each connection listed, select the three dots (More commands) and choose Change owner. Enter the service account email address. The service account must already have a matching connection created in its own Power Automate account. If it does not, create that connection first by signing in as the service account and adding the connection manually. - Re-authenticate each connection
After changing the owner, Power Automate prompts you to sign in again. Use the service account credentials to authenticate. This step confirms the service account can access the resource. - Save the flow
Close the connections panel and select Save at the top of the flow details page. The flow now uses the service account identity for all its connections. - Test the flow
Select Test on the flow details page. Choose Manually and run the flow with a sample trigger. Check that every action executes without errors. If any step fails, review the connection permissions for that specific service.
What to Do When the Original Creator Is No Longer Available
If the flow’s creator has already left the company, you may not be able to sign in as that user. In this case, you must export the flow and import it under the service account.
Export the Flow
Open the flow details page. Select Export > Package (.zip). Choose the package type that matches your environment. Download the file to your computer.
Import the Flow Under the Service Account
Sign in to Power Automate as the service account. Select My flows > Import. Upload the package file. During import, Power Automate asks you to assign new connections. Create new connections using the service account credentials for each resource. Complete the import and test the flow.
Common Problems When Moving Flow Connections
Flow Fails After Changing the Connection Owner
This usually happens because the service account lacks permissions to the SharePoint site or other resource. Go to the SharePoint site, add the service account, and grant at least Contribute access. Then test the flow again.
Service Account Cannot Sign In to Power Automate
Check that the service account has a valid Power Automate license assigned. Also confirm the account is not blocked by conditional access policies. Work with your identity team to allow the service account to access Power Automate.
Connection Shows as Invalid After the Move
The service account may have been removed from the environment. Go to the Power Platform admin center, select Environments, choose the environment, and verify the service account is listed as a member. If not, add it again with the Environment Maker role.
Service Account vs User Account: Flow Ownership Comparison
| Item | Service Account | User Account |
|---|---|---|
| Ownership stability | Persists regardless of employee turnover | Stops working when user leaves |
| License requirement | Requires a Power Automate license | Requires a Power Automate license |
| SharePoint permissions | Must be added to each site used by the flow | Inherits permissions from the user’s group memberships |
| Audit trail | All actions attributed to one identity | Actions spread across multiple users |
| Setup effort | Requires initial configuration | Automatic when user creates the flow |
Best Practices After Moving the Connection
Document which flows are owned by the service account. Store this list in a SharePoint list or a shared workbook. Include the flow name, the service account email, and the date the connection was moved.
Set up a recurring reminder to review the service account’s permissions every quarter. Remove access to any sites the flow no longer uses. This reduces security risk.
Monitor the service account’s Power Automate usage in the Microsoft 365 admin center under Reports > Usage > Power Automate. Look for failed runs or unusual activity.
You can now move any flow connection to a service account using the checklist above. Start with one critical flow to confirm the process works in your environment. After that, move all team flows to the service account to eliminate disruptions from employee departures. For flows that use premium connectors, check that the service account also has the correct Power Automate per-flow plan assigned.