Skip to content
tenantcraft
( Insights)

Lock down the SharePoint list behind your Power Apps app

A Power Apps app on a SharePoint list only works if every user can open that list. So anyone can skip the app and read everyone's submissions. Send the write through a flow that uses one stored connection, and take the list away from staff.

Stage
Govern
Topic
Power Platform
Published
Written by

Tested in a live tenant,

(Short version)

Build an instant flow with the Power Apps (V2) trigger that creates the list item. Add staff as run-only users and set the SharePoint connection to Use this connection, not the default Provided by run-only user. Then remove staff from the list. Pass User().Email into the flow, because Created By will show the flow owner.

In this post

Someone in finance builds an expense app on a SharePoint list. It works, so they share it with 40 staff. A week later a site lead pastes the list’s web address into a browser and scrolls through everyone’s claims.

Nothing was misconfigured. For the app to work, every user needed rights on the list. Those rights don’t stop at the app’s edge.

The usual next idea is a service account: one login holds the SharePoint access, and staff hold none. Sometimes there’s an extra condition, like keeping the existing Power Automate email alerts working.

This confusion isn’t limited to the people who build apps. I opened a link, a SharePoint form came up as a Power App, and I couldn’t tell which list sat behind it or who else had access.

Why every app user can read the list

A canvas app talks to SharePoint as the person running it. Microsoft’s connector reference calls the SharePoint connection “not shareable”: share the app, and each user is asked to create their own connection.

That connection carries the user’s own rights. If they can’t read the list, neither can the app. So the list gets opened to everyone, and the app’s screens become a suggestion, not a boundary. Anyone with the URL can skip them.

Why a service account is the wrong fix

A service account is a real login with a password that several people end up knowing.

  • MFA and conditional access. Microsoft’s connector reference warns these policies can block the connection. A shared account either fails them or gets an exception, and an exception is a hole.
  • No audit trail. Every write looks like the same account. When someone leaves, the password changes everywhere.
  • A paid seat nobody uses. It needs a licence to hold the connection.

Power Automate already solves the real requirement. A flow can store one connection and let other people run the flow without ever holding that connection.

The fix: a run-only flow does the write

The app stops connecting to SharePoint. It calls a flow with the form values. The flow writes the item using a connection you set up once. Staff can run the flow and nothing else.

1. Build the flow

Create an Instant cloud flow with the When Power Apps calls a flow (V2) trigger. Add one input per field. The example uses Title (text), Amount (number) and SubmittedBy (email).

Add the SharePoint Create item action. Pick the site and list, and map each column to its trigger input.

Power Automate > Create item

Three values come in from the app. The flow writes them with its own SharePoint connection.

If the submitter’s identity matters, add a Condition before Create item that checks the email ends with your domain. Microsoft suggests exactly this kind of check for values passed from an app.

2. Share it as run-only and switch the connection

Save the flow and open its details page. On the Run-only user tile, select Edit.

Add a Microsoft Entra security group, not named people. New staff then get access by joining the group.

Under Connections Used, SharePoint defaults to Provided by run-only user. That makes each person sign in with their own connection, which brings back the problem you’re fixing. Change it to Use this connection and select Save. The line under SharePoint changes to “Access to this connection is provided by the owner of the flow.”

Flow details > Run-only user > Edit

The setting that matters. Use this connection makes every run write with the owner's connection.

Run-only users can trigger the flow. They can’t open it, edit it, or reuse its connection elsewhere.

3. Call the flow from the app

In Power Apps Studio, open the Power Automate pane, select Add flow, and pick the flow. Set the submit button’s OnSelect:

Submitexpenserequest.Run(
    TitleInput.Text,
    Value(AmountInput.Text),
    User().Email
);
Notify("Expense submitted", NotificationType.Success)

Remove the SharePoint list from the app’s data sources. Publish, and share the app with the same security group.

4. Take the list away from staff

On the list, go to Settings > List settings > Permissions for this list and select Stop Inheriting Permissions. Remove Members and Visitors, or whichever groups shouldn’t read the data.

The account behind the flow’s connection keeps Contribute on the list. It doesn’t need Full Control.

Every list with unique permissions is an exception someone has to remember. Finding broken permission inheritance shows how to keep track of them.

5. Test with an account that isn’t on the list

Testing as the owner proves nothing, because the owner can reach everything. Use an account that’s in the run-only group but has no rights on the site, and check four things:

  1. First launch: the app opens without asking for a SharePoint connection.
  2. Submit: the item appears in the list.
  3. Submitter: the item’s SubmittedByEmail holds the test account, not the flow owner.
  4. Direct access: the list’s URL returns You need access.

Test account > list URL

Check 4. The account that just submitted through the app can't open the list.

Record who submitted it

Because the flow writes the item, SharePoint stamps Created By with the flow’s connection owner, not the app user.

Expense Requests > All Items

Created By shows the flow owner on every row. SubmittedByEmail is the only record of who sent it.

That’s why the app passes User().Email. Microsoft notes it returns the user’s UPN, not the SMTP address. In most tenants they match. If yours don’t, look users up by UPN.

Store it in a text column. If you need a people column for views and filters, have the flow resolve the email to a user and fill both.

Keep the email alerts working

Add the email step to the same flow, after Create item. The flow already holds the values, so the email can include them.

An existing flow that fires when an item is created still fires. Items written by a flow are new items like any other. Check whether that flow sends to Created By. If it does, it now emails the flow owner every time. Point it at SubmittedByEmail.

The heavier option: Sites.Selected

You can remove the person-owned connection entirely with an app registration in Microsoft Entra ID.

The Microsoft Graph permission Sites.Selected limits an app to the SharePoint sites it’s been granted, not the whole tenant. Lists.SelectedOperations.Selected narrows that to one list. Consent alone grants nothing. Microsoft says an app consented for these scopes “would initially have no access” until someone assigns it a role on the site or list. Assigning at the site level needs Sites.FullControl.All, so it’s an admin job.

The cost is the catch. Calling Graph with an app identity from a flow takes a premium connector, such as HTTP with Microsoft Entra ID. Microsoft’s licensing FAQ says that if an instant flow has premium connectors, every user who runs it needs Power Automate Premium.

Choose Sites.Selected when a system outside Power Platform writes to the site, or when policy bans user-owned connections. For a staff form, the run-only flow does the same job on standard licences.

What this does not fix

  • Staff can’t read their own entries back. The app has no list connection. If people need their history, add a second flow that returns only rows where SubmittedByEmail matches the caller.
  • The connection owner is a single point of failure. Microsoft notes that if the person whose connection a flow uses leaves, those actions can fail. Use an IT-owned account and add a co-owner.
  • App-to-flow values can be tampered with. Microsoft warns they travel as visible network traffic. The domain check in step 1 limits the damage, but it can’t prove which user sent the request.
  • Owners and admins still see everything. This keeps staff out, not the people who manage the site.

The bottom line

List permissions decide who reads the data, whatever the app shows. Move the write into a run-only flow set to Use this connection, take staff off the list, and pass User().Email so every row still names its submitter.

(Paired checklist, 7 pages)

Permissions Cleanup & Governance Prep Checklist

You get one email with the link. That's the only email.

Read it on the site
  • Audit broken inheritance, scope sprawl, oversharing, and orphaned accounts
  • The limits that decide what migrates clean: 5,000 / 50,000 scopes, 100,000 items
  • Prepare identity so permissions survive the move to Microsoft Entra ID
  • Design and remediate a clean, group-based model before cutover
Sneak peek

Document preview

100%

Loading the document…