Microsoft Lists explained — what it is and how to start

Microsoft Lists is a lightweight app for tracking structured information (items with typed columns, views and simple rules) that stores its data as SharePoint list items. You can use Lists from the Lists web app, a Teams tab, a SharePoint site or the Lists mobile app; permissions, versioning and storage are handled by SharePoint.

What exactly is Microsoft Lists and where does it live

Microsoft Lists is a user-facing layer on top of SharePoint lists that puts column-based records, views and simple rules into an easy interface for teams. Think of a list as a table with pre-built templates, typed column types (choice, person, date, number, lookup, etc.), configurable views, conditional formatting and simple column rules. The actual items, permissions and storage are SharePoint list items.

You can open and manage Lists from several places:

• The Lists web app in Microsoft 365, where you create and manage lists directly.
• A Lists tab inside a Microsoft Teams channel, which embeds the same SharePoint list for team collaboration.
• Directly in SharePoint sites; a SharePoint "list" and a Lists list are the same object.
• The Lists mobile app for viewing and editing items on the go.

Because Lists uses SharePoint for storage, you get SharePoint permissions, versioning and tenant storage limits. Adding a list as a Teams tab does not copy or move data; it shows the same SharePoint-backed list inside Teams.

How Lists commonly integrates with other Microsoft 365 services:

• Teams: Embed a list as a tab so channel members can view and edit items alongside chats, files and other tabs.
• Power Automate: Trigger flows when items are created or changed to run approvals, send notifications, copy items, update other systems or connect to third-party services.
• Power Apps: Replace the default list form with a custom Power Apps form for richer data entry and UI logic, then keep the same list as the data source.

Practical benefits of those integrations include running approvals from list items, pushing changes to other systems automatically, and building tailored entry screens without changing where the data lives.

When should I use Lists instead of Excel, Planner, or a SharePoint document library

Use Lists when you need structured records with typed columns, multiple saved views, item-level permissions and reliable concurrent editing. Below are concrete scenarios showing when Lists is the better choice.

For example: inventory or asset tracking

Say you track equipment across locations. Use typed columns for serial number, status, location and last service date, create filtered views by location or status and add indexes for performance. Compared with Excel, Lists avoids file locking and handles many users editing items at once while enforcing SharePoint permissions on items.

For example: simple CRM or issue tracker

If you need a light CRM for leads or a small issue tracker, Lists gives choice fields for status, person fields for owner and simple rules/alerts for status changes. Planner is better when you need Kanban-style task boards and execution tracking; Lists is better when you need a queryable record set and item metadata.

For example: event or equipment booking

For room or equipment bookings where each booking is a record with date/time and attendee fields, Lists supports calendar views, filters and validation. A document library stores files, not structured booking records, so Lists is the right place for scheduling metadata.

For example: approvals and sign-offs

Track approval requests as list items and use Power Automate to route approvals and record decisions and timestamps. Excel lacks built-in approval flows and item-level versioning; Planner lacks fields for capturing decision details.

Deciding factors to choose Lists over others:

• You need typed columns and consistent data entry.
• Multiple people will edit records concurrently.
• You want saved views and filters rather than a free-form spreadsheet.
• You need item-level metadata and SharePoint permission controls.

When not to use Lists: heavy calculations, large relational datasets, primary file storage or advanced project boards with complex timelines are better handled by Excel, Dataverse/SQL, a document library, or Planner/Project.

How to create a working list in five minutes (the hands-on example you'll actually try)

Follow these steps to create a usable list from a built-in template, add a choice and date column, make a filtered view, and share it.

1. Create a new list from a template

Open the Microsoft 365 app launcher > Lists > New list > Choose a template (e.g., "Issue tracker")

2. Name it and choose where it lives

Choose a name, description and the SharePoint site to store the list. If you add it inside Teams, pick the channel where others will access it.

3. Add a choice column
4. Open the list, select + Add column > Choice.
5. Enter the column name, for example Priority, and the choice values Low, Medium, High.
6. Save the column.
7. Add a date column
8. Select + Add column > Date and time.
9. Name it Due date and choose date only or date and time.
10. Save the column.
11. Create a filtered view
12. From the view menu, select Create new view.
13. Pick a view type (List or Grid), name it Next 7 days, and add a filter where Due date is in the next 7 days.
14. Save the view.
15. Share and set permissions
16. Click Share or Settings > List settings > Permissions for this list.
17. Grant members the level you want: Read, Edit, or Full control.
18. If inside Teams, adding the tab makes the list visible to channel members, who still require the SharePoint permissions you set.

Adding a list to a Teams tab does not move its storage; it uses the same SharePoint list behind the scenes.

After these steps you'll have a list with typed columns, a view for near-term items and permissions set for your team. From here you can add rules, format columns or start a Power Automate flow.

Where Lists breaks down: scale, relationships and advanced workflows to watch for

Lists is not a full relational database or a replacement for Dataverse. Use Dataverse or a database when you need multi-table relational integrity, complex joins, or transactional guarantees.

Specific limitations to watch for:

• Large relational datasets: Lookup columns let lists reference other lists, but Lists isn't designed for complex foreign-key relationships across many tables.
• List thresholds and performance: SharePoint has practical thresholds; views that return very large numbers of items can be slow or blocked. Test performance before relying on very large lists.
• Advanced reporting and analytics: For heavy reporting, complex aggregations or BI, export to Power BI or use a backend built for analytics rather than relying on list views.
• Attachment handling: Attachments are supported but not ideal for many or large files—use a document library when files are the primary content.
• Complex workflows and state machines: Lists support simple rules and alerts, but multi-stage workflows with advanced branching and error handling belong in Power Automate or a custom app.

When to migrate away from Lists:

• The list grows into tens of thousands of items with frequent aggregated queries.
• You need transactional consistency and complex relationships across datasets.
• You require advanced reporting that will run regularly against the source.

In those cases consider Dataverse, SQL-backed services or a purpose-built app using Power Apps with a proper backend.

Common misconceptions that cause bad decisions

Mistakes around Lists often push teams to the wrong tool. Correct these common misunderstandings.

List items are not files. A list item is structured data (fields/columns). If you need to manage documents, versions of files, or rich file metadata, use a SharePoint document library.

Lists aren’t a full no-code database replacement for Dataverse. Lists handle many tracking use cases, but they lack strong relational integrity, complex business rules, and transactional guarantees that Dataverse provides.

Workflow automation still needs Power Automate for advanced logic. Lists include simple column rules and alerts, but branching approvals, conditional steps and integrations require Power Automate flows.

Adding a list as a Teams tab doesn’t change storage. The list stays in SharePoint; Teams only embeds the view. Permissions and storage limits are controlled by SharePoint.

Assuming Lists scales like a SQL database leads to performance surprises. Test list size and view filters early if you expect many items or frequent queries.

Quick answers to the practical questions people always ask next

Q: Which Microsoft 365 plans include Lists?

A: Lists is built on SharePoint and is available where SharePoint Online is included. Many Microsoft 365 business and enterprise plans include SharePoint Online and therefore Lists, but plan details can vary. Check your subscription or tenant admin to confirm.

Q: Can I use Lists offline or on mobile?

A: There’s a Lists mobile app for viewing and editing items when online; offline editing support is limited. Expect to be online for full functionality.

Q: How do I export or back up a list?

A: Export list data to Excel from the view menu. You can also use Power Automate or SharePoint APIs to copy items for backup. Because data is in SharePoint, tenant backup and retention policies apply.

Q: What about security and sharing?

A: List permissions follow SharePoint permissions. You can set list-level permissions and item-level permissions in SharePoint. Adding a list to Teams does not grant extra permissions; Teams users still need the appropriate SharePoint access.

Conclusion

If you need a straightforward way to track items, statuses and dates with typed columns, saved views and light automation, start with Microsoft Lists. Begin from a template, add the columns you need, share the list with the right permissions and add a Power Automate flow for one approval or notification. If your data model or reporting needs become complex or you hit scale limits, plan a migration to Dataverse, a database or a SharePoint-based architecture.

Frequently Asked Questions

Can I link one list to another?

Yes, with lookup columns you can reference items in another list, but this is not the same as full relational database joins and can become hard to manage at scale.

Will list data count against my SharePoint storage?

Yes. Lists store items in SharePoint, so list data and attachments consume SharePoint storage and are subject to tenant storage policies.

Can I build a custom form for a list?

You can customize list forms using Power Apps for richer input experiences. Basic column formatting and rules are available directly in Lists for simple customizations.