Microsoft Lists Complete Guide: Add, Configure & Build Mobile Apps on SharePoin
Everything You Need to Know About Microsoft Lists
From embedding lists in SharePoint sites to building mobile Power Apps — a complete walkthrough for developers and power users alike.
Microsoft Lists has quietly become one of the most powerful collaboration tools in the Microsoft 365 ecosystem. Whether you are tracking project assets, managing support queues, or building lightweight databases for small teams, Lists delivers a surprisingly deep feature set — one that many organizations have only scratched the surface of.
This guide walks through every major concept, from embedding a list in a SharePoint site to building a mobile app that surfaces your data on the go. We will also address one of the most commonly misunderstood decisions in SharePoint development: when not to embed a modern list as a web part.
Adding a Microsoft List to Your SharePoint Site
The most common entry point for Lists is adding one directly to a SharePoint site page as a web part. Navigate to your SharePoint site, enter Edit mode on a page, click the + to insert a web part, and search for List. You can surface any existing list from the current site or, with appropriate permissions, from another site in your tenant.
Open the page in Edit mode
Click Edit in the top-right corner of your SharePoint page. The page toolbar appears with a pencil icon.
Insert the List web part
Click the + section separator or the canvas toolbar, search for List, and select it from the panel.
Select the source list
Choose a list from the current site. The web part renders a live, interactive view — users can sort, filter, and add items directly from the page without leaving.
Configure the view
Select a specific view (All Items, Calendar, Gallery, etc.) and toggle whether to show the command bar, filters, or search inside the embedded list.
Pinning a list to a page gives stakeholders a single URL they can bookmark. Combine this with audience targeting in SharePoint to show role-specific lists to different groups — all from the same page template.
Why You Should Not Add a Modern List as a Web Part
This is the nuanced decision that many developers get wrong. While embedding a list on a page feels convenient, there are real performance and UX trade-offs that matter at scale.
“A list embedded in a page is never the primary UI — it is an accessory. If users spend more than 60 seconds interacting with it, send them to the list’s own URL instead.”
SharePoint Engineering Guidance, 2024
Consider the following before adding a list as a web part:
| Scenario | Embed as web part? | Reasoning |
|---|---|---|
| Status dashboard showing 10–20 items | Yes | Low item count, read-heavy, at-a-glance consumption. |
| Full data entry form with 500+ rows | No | Performance degrades; link to the list directly instead. |
| Team homepage with a “My Tasks” snippet | Yes | Filtered personal view, minimal interaction required. |
| Document register needing column sorting and editing | No | Users need the full list experience — web part limits the UI surface. |
Creating a New List from Scratch or from a Template
Microsoft Lists offers two creation paths. From lists.microsoft.com or from within SharePoint, click New list. You are presented with a choice:
Blank list
Start with a single Title column and add every field manually. This is the most flexible path — ideal when your schema does not map to any existing template.
From an existing list
Clone the schema (columns, views, and optionally content) of another list in your tenant. This is a significant time-saver when you need multiple lists with consistent structure — for example, a per-project issue tracker deployed across dozens of project sites.
# Using PnP PowerShell to provision a list from a schema template
Import-Module PnP.PowerShell
Connect-PnPOnline -Url "https://contoso.sharepoint.com/sites/projects" -Interactive
# Export schema from source list
Get-PnPList -Identity "Issue Tracker" | Export-PnPListToSiteTemplate -Out "issue-tracker-schema.xml"
# Provision to a new site
Connect-PnPOnline -Url "https://contoso.sharepoint.com/sites/project-alpha" -Interactive
Invoke-PnPSiteTemplate -Path "issue-tracker-schema.xml"The Microsoft Lists UI wraps this into a point-and-click experience, but understanding the underlying schema export is valuable when deploying at scale through Azure DevOps pipelines or site provisioning engines.
Adding a Column to a List
Columns are the heart of any list. Every piece of structured data — dates, choices, people, lookups, calculated values — lives in a column. To add one, open the list, scroll to the rightmost column header, and click the + icon (or use Add column from the column header menu).
Column types worth knowing deeply:
| Column type | Best used for |
|---|---|
Choice | Status fields, categories — renders as a dropdown or radio buttons. |
Person or Group | Owner, assignee, or reviewer — links to Azure AD and supports multiple values. |
Lookup | Foreign-key style reference to another list in the same site. Use to normalize data. |
Calculated | Derived values using Excel-like formulas (=TEXT([Due Date],"yyyy-MM-dd")). |
Managed Metadata | Taxonomy-backed tagging — keeps terminology consistent across the tenant. |
Column internal names are set at creation and cannot be changed without PowerShell or REST API calls. Use clean, concise internal names from the start — avoid spaces and special characters. The display name can always be updated freely.
Working with Views
A view is a saved combination of columns, filters, sort orders, groupings, and a layout (grid, gallery, calendar, board). Views are per-list and per-user — personal views are visible only to you, while standard views are shared with anyone who has list access.
Some view configurations worth knowing:
Board view (Kanban)
Requires a Choice column with defined stages. Items render as cards that can be dragged between columns. This view is surfaced automatically when the list has a column named Stage or Status.
Calendar view
Requires at least one Date and Time column. Map a start and optional end date, and items appear as calendar events. Combine with the Person column to build team availability grids.
Gallery view
A card-based layout ideal for lists with image columns. Each item renders as a visual tile, making it appropriate for product catalogues, asset libraries, or photo registers.
Building a Basic Mobile App for a List
Microsoft Power Apps integrates directly with SharePoint Lists. From any list, click Integrate > Power Apps > Create an app. Power Apps Studio generates a three-screen canvas app — browse, detail, and edit — wired to your list automatically.
Launch the app generator
From the list command bar, select Integrate → Power Apps → Create an app. Name your app and click Create.
Review the auto-generated screens
Power Apps creates BrowseScreen1, DetailScreen1, and EditScreen1. Each is wired to your list’s SharePoint data source via a Patch() and Filter() formula pattern.
Customize and publish
Adjust the gallery template, card layout, and form fields. Publish and share via the Power Apps portal or embed in a Teams channel tab for mobile-first access.
The generated app is fully functional out of the box, but the real power comes from composing it with Power Automate flows — trigger notifications when items change, enforce approval workflows, or sync data to external systems automatically.
Power Apps inherits SharePoint permissions by default. A user who cannot view a list item in SharePoint also cannot view it in the generated app. Always validate item-level permissions before deploying apps to broad audiences.
Closing Thoughts
Microsoft Lists occupies a sweet spot between a spreadsheet and a relational database. Its deep integration with SharePoint, Power Apps, and Power Automate makes it a genuine platform rather than a standalone tool. The developers who get the most out of it are those who understand when to use it — and equally, when to reach for something else.
The decision to embed a list as a web part, build a Power App on top of it, or expose it directly via its own URL is architectural. Make that decision deliberately, based on how your users will actually interact with the data, and Lists will reward you with a flexible, low-maintenance data tier that scales well into the thousands of items.
