Power Apps SharePoint List Canvas App Guide
Real-world examples, the canvas vs model-driven choice, delegation limits you must know, and how to publish your app to Teams, SharePoint, and mobile — no code required.
Most organisations already have SharePoint lists holding business data — asset registers, helpdesk tickets, purchase requests, employee records. The problem is that SharePoint's default list view is built for information managers, not the frontline staff who need to submit and update that data. Microsoft Power Apps solves this by letting you create a canvas app from a SharePoint list, with mobile-friendly forms and galleries on top of your existing data — without writing traditional code.
Canvas Apps vs Model-Driven Apps: Which One Do You Need?
-
1Start with your SharePoint list
Go to your SharePoint site and create or identify the list you want to use as your app's data source. Make sure column names are clear and column types are set correctly (text, choice, person, date, lookup, etc.). Poor column setup here leads to bad app performance later.
-
2Open Power Apps and create a new canvas app
Go to powerapps.microsoft.com > Create > Canvas app from blank. Give it a name and choose phone or tablet layout based on your primary users. Power Apps launches in edit mode.
-
3Connect to your SharePoint list
Click 'Data' (left sidebar) > 'Add data' > search for SharePoint > select your site > select your list. Power Apps now has read/write access to your list columns.
-
4Build your form using controls
Drag text input, choice dropdown, date picker, and other controls onto your screen. For each control, set its 'Default' property to point to list columns (e.g., TextInput1.Default = ThisItem.Title). Build the form layout that suits your task.
-
5Add buttons for Save, New, and Delete
Insert buttons with OnSelect formulas: Save = Patch(ListName, ThisItem, {updated fields}); New = NewForm(FormName); Delete = Remove(ListName, ThisItem). Test each action thoroughly before sharing.
-
6Share your app with users
Publish the app. Go to Share > enter user names or groups. Each user needs a Power Apps licence (included in Microsoft 365). Test the app as an end user before full rollout.
Power Apps comes in two fundamentally different types. Choosing the wrong one is the most common Power Apps mistake. Here's the clear comparison:
| Canvas App | Model-Driven App | |
|---|---|---|
| Best for | Task-focused apps with custom UI: data entry forms, inspection checklists, approval screens | Data-rich business applications: CRM, case management, project tracking with complex relationships |
| Data sources | 400+ connectors including SharePoint, Excel, SQL, Salesforce, and more | Microsoft Dataverse (formerly CDS) — structured relational database in the Power Platform |
| UI design | Fully custom — drag and drop controls, set position and size of every element | Data-driven — generated automatically from data schema; less visual flexibility |
| Mobile experience | Excellent — design specifically for phone or tablet screens | Good but less optimised for mobile-first scenarios |
| Complexity | Lower — good for 1–3 SharePoint lists | Higher — better for multi-table relationships and business logic |
| SharePoint fit | Native — SharePoint lists are a first-class data source | Indirect — usually requires Dataverse, though SharePoint data can be synced |
For most SharePoint-based use cases, canvas apps are the right choice. Model-driven apps shine when you're building something closer to a Dynamics 365 application with complex entity relationships. If your data lives in SharePoint lists, start with canvas.
Using SharePoint as a Power Apps Data Source
SharePoint lists are one of the simplest data sources to connect in Power Apps. When you connect a SharePoint list to a canvas app, Power Apps reads the list's columns (including column types: text, choice, person, date, lookup) and uses them to generate forms automatically.
SharePoint column types and Power Apps controls
| SharePoint column type | Default Power Apps control | Notes |
|---|---|---|
| Single line of text | Text input | Simple text box; supports max length |
| Choice | Dropdown / Radio buttons | Options auto-populated from SharePoint choices |
| Person or Group | People picker | Searches Microsoft Entra ID; returns user object |
| Date and Time | Date picker | Timezone-aware; can be date-only |
| Yes/No | Toggle | Boolean; useful for approval flags |
| Lookup | Dropdown | References another SharePoint list — delegation applies |
| Managed metadata | Limited | Requires workaround; Power Automate often handles this better |
3 Real-World Power Apps + SharePoint Examples
Asset Tracking App
Operations
A canvas app that replaces a shared Excel spreadsheet used by the facilities team to track company assets — laptops, monitors, projectors, vehicles. The SharePoint list stores asset details (category, serial number, assigned user, location, condition, last-checked date). The app provides a mobile-first interface for staff to check assets in and out, log condition notes, and scan barcodes using the device camera.
- SharePoint lists used: Assets, Assignments, Locations, Categories
- Key controls: Barcode scanner control, gallery with image thumbnails, location dropdown pre-filtered by department
- Power Automate integration: Notify manager when an asset is flagged as damaged; send overdue-return reminders
IT Helpdesk Ticket App
IT
A two-screen canvas app replacing email-based IT support requests. Screen 1 is a submission form for staff to log issues — category, priority, description, and photo attachment. Screen 2 is an IT team dashboard showing all open tickets, filterable by status and assignee. Tickets are stored in a SharePoint list; Power Automate handles routing and SLA notifications.
- SharePoint lists used: Tickets, IT Staff (lookup)
- Key controls: Form with add-attachment control, gallery with conditional formatting (red for overdue, amber for due today), edit form for status updates
- Embedding: Published as a Teams tab in the IT Support team channel, so staff submit tickets without leaving Teams
Employee Expense Claims App
Finance
A mobile-first canvas app for submitting and approving expense claims. Employees photograph receipts (stored in a SharePoint document library), enter claim details, and submit. Managers receive an Adaptive Card in Teams asking them to approve or reject, with the receipt image embedded. Finance sees an aggregate view of all pending claims with export-to-Excel.
- SharePoint lists used: Expense Claims, Expense Categories, Receipts (document library)
- Key controls: Camera control for receipt capture, date picker, currency input, person lookup for manager
- Power Automate integration: Multi-level approval flow — line manager first, Finance team second for amounts over £500
The Delegation Problem: What Every Power Apps Developer Must Know
Delegation is the most misunderstood concept in Power Apps, and ignoring it causes apps to silently return wrong data in production. Here is what it means and why it matters.
What is delegation?
When Power Apps queries a SharePoint list, it can either process the query locally (loading data to the device first, then filtering) or delegate the query to SharePoint (letting SharePoint do the filtering server-side). Delegation is far more efficient — but not all functions support it.
The delegation limit
For non-delegable queries, Power Apps loads a maximum of 2,000 records to the device (this was 500 before 2019; it is now configurable up to 2,000). If your SharePoint list has 5,000 items and you use a non-delegable filter like Search() without delegation, your app only sees the first 2,000 items — and Power Apps shows a yellow delegation warning, which many developers ignore.
Delegable vs non-delegable operations on SharePoint
| Function | Delegable to SharePoint? | Notes |
|---|---|---|
Filter() with simple comparisons (=, <, >) | Yes | Most column types supported |
Sort() | Yes | Single column; multi-column sort not always delegable |
Search() | Yes (text columns only) | Searches title and text fields |
StartsWith() | Yes | Text column prefix match |
Filter() with in operator | No | Use multiple Or conditions instead |
CountIf() | No | Loads all records; use Dataverse for aggregate queries |
Filter() with lookup columns | Limited | ID field delegable; expanded fields may not be |
Delegation rule of thumb: If your SharePoint list will ever exceed 2,000 records, design around delegation from day one. For lists that genuinely need aggregate queries or complex filtering, consider migrating that list to Dataverse or using a SQL Azure backend instead.
Publishing Options: Where Your App Lives
Once your canvas app is built, you have several ways to deploy it to users — each suited to different scenarios:
Microsoft Teams tab
The most popular option for internal business apps. Users access the app directly in Teams without installing anything. Requires publishing as an app package from Power Apps and adding it to Teams via the Admin Centre or individually by users. Apps can be pinned to specific Teams channels, making them contextual to the team's work. Microsoft documentation walks through the exact steps.
📄 Embed a canvas app as a Teams tab — learn.microsoft.comSharePoint page web part
Embed your app directly into a SharePoint page using the Power Apps web part. This works well when the app is related to a specific SharePoint site — for example, embedding an asset management app in the Facilities team site. Users don't need a separate app installed; they access it while browsing SharePoint.
Standalone web app
Share a direct URL (from make.powerapps.com) with users. They open it in a browser and can pin it as a progressive web app on their desktop or home screen. Good for apps shared across departments where there's no single Teams team or SharePoint site as a home.
Power Apps mobile app
Available on iOS and Android. Users install the Microsoft Power Apps app from the App Store or Google Play, sign in with their M365 credentials, and all apps shared with them appear in the app library. Ideal for frontline workers without Windows devices — field engineers, warehouse staff, retail teams.
Governance: What Organisations Get Wrong
Power Apps makes it very easy for citizen developers to build and share apps — which is great for productivity but creates governance challenges if unmanaged.
- Environment strategy: Use Development, Test, and Production environments via the Power Platform Admin Centre. Never build directly in the production environment.
- Data Loss Prevention (DLP) policies: Define which connectors can be used in which environments. For example, block consumer connectors (Twitter, Dropbox) in the production environment to prevent data exfiltration.
- App ownership: Set a co-owner for every production app so it doesn't become orphaned when the original developer leaves.
- Licensing clarity: Canvas apps connecting to SharePoint require only a Microsoft 365 licence for users (no additional Power Apps licence needed). Connecting to premium connectors or Dataverse requires a Power Apps Per User or Per App licence.
- Power Platform Centre of Excellence (CoE) Starter Kit: Microsoft provides a free CoE Starter Kit that gives IT admins inventory, analytics, and governance tools for all Power Platform usage in the tenant.
Ready to build your first Power App?
OceanCloud can design, build, and deploy a canvas app on your existing SharePoint environment in 2–4 weeks — or train your team to build their own. Either way, we handle governance and ensure it scales.
Talk to a Power Apps SpecialistFrequently Asked Questions
Yes, SharePoint is the most common data source for Power Apps in Microsoft 365 environments.
You connect via the SharePoint connector and work with list items directly. For simple data entry and viewing scenarios it works well, but it has delegation limits — queries that can't be processed server-side are limited to 500–2000 records client-side.
In Power Apps, choose Create, select Start from data, connect to SharePoint, choose the SharePoint site, and pick the list.
Power Apps generates a canvas app with browse, detail, and edit screens. Review the generated forms, rename controls, set delegation-safe filters, and test list permissions before publishing.
Delegation means the data source (SharePoint) processes a filter or sort query on the server, returning only matching records.
Non-delegable functions (like Search() or most text functions) run client-side on a capped record set. If your list has more than 2000 items and you use non-delegable filters, users will see incomplete results without any warning.
Canvas apps give you pixel-precise control over layout and connect to any data source.
Model-driven apps are data-first: you define the data model and the app generates its UI automatically. Canvas apps suit custom interfaces; model-driven apps suit complex business data with relationships, business rules, and standard CRM-style views.
From the Power Apps portal, open the app and select Share. Enter names or groups.
Users need at least a Microsoft 365 licence to run Power Apps that connect to standard connectors. For premium connectors, each user needs a Power Apps Premium (Per User) licence. Also share the underlying SharePoint list with appropriate permissions.
Yes.
Power Apps supports hundreds of connectors including SQL Server, Dataverse, Salesforce, ServiceNow, REST APIs via custom connectors, and on-premises data sources via the on-premises data gateway. Connectors marked 'Premium' require a Power Apps Premium licence.