Microsoft Lists step-by-step: create, customize, share lists

Microsoft Lists is the app you use to track work items, owners, due dates and status inside Microsoft 365. This article tells you, step by step, how to create a new list from scratch, from a template, or by importing from Excel or an existing SharePoint list; how to add and configure common column types; how to build and save views and filters; how to set item-level defaults, customize forms and apply simple conditional formatting; and how to share, set permissions and add a basic Power Automate flow to notify owners. Read the short steps and examples, follow the commands in the numbered steps, and you’ll have a working list your team can use.

What you need before you start

• A Microsoft 365 account with a license that includes Lists (most business and education plans do).
• Access to the app launcher (waffle) or Teams where Lists is available.
• If you plan to import data: an Excel file with a single table or a SharePoint site URL and permission to view its lists.
• A prepared list of columns you want (column name, type, example value) and a few sample rows in Excel if you want to import quickly.
• Permission to create lists on the SharePoint site or in the Team where you want the list stored (if unsure, contact the site owner).

If you create a list inside a Team channel the list inherits Team permissions; creating in your personal Lists area keeps it private until you share.

Create a list from scratch, a template, or from Excel in exact steps

1. Open Lists from the Microsoft 365 app launcher or open the Team channel where you want the list and add a Lists tab.
2. Click New list.
3. To start from scratch, choose Blank list.

Choose name, description, and color/icon

4. Enter a name and optional description, choose where to store it (Your lists or a SharePoint site/Team), then click Create.

Expected result: the new blank list opens with a default Title column.

5. To use a template: click New list then From template.

Browse templates, e.g., Issue tracker

6. Select a template (for example Issue tracker), click Use template, adjust the name and storage location, then click Create.

Expected result: the template creates sample columns and example items you can edit.

7. To import from Excel: click New list then From Excel.

The Excel file must contain a table or a clearly delimited header row; importing maps columns and creates the list schema based on the file.

8. Upload the Excel file or pick it from OneDrive; confirm the sheet/table to import, map Excel columns to list columns if prompted, and click Create.

Expected result: a list populated with rows from the Excel table and columns matching the headers.

9. To copy a SharePoint list: open the SharePoint site, open the list you want to copy, then use Integrate > Create list or Save list as template (if available) to recreate it on another site.

When copying from SharePoint, choice and lookup columns may require review after import; lookups must point to a list on the same site to work correctly.

Add and configure the columns you'll actually use

1. Open your list and click + Add column in the header.
2. Add a single line of text column.

Choose `Single line of text`, enter name like `Short description` or `Title`, click `Save`.

Expected result: a new text column appears and accepts short text entries.

3. Add a Choice column for status.

Choose `Choice`, name it `Status`, add options `New`, `In progress`, `Blocked`, `Done`, choose display (dropdown or radio buttons), optionally assign colors, click `Save`.

Practical example: use Choice for Status so teammates can pick In progress or Done quickly.

4. Add a Person column for owners.

Choose `Person`, name it `Owner`, set whether the field is required, decide if you allow people and groups, click `Save`.

Practical example: set Owner required so every item has a responsible person.

5. Add a Date column for deadlines.

Choose `Date and time`, name it `Due date`, select `Date only` or `Date and time`, click `Save`.

Practical example: choose Date only for a delivery date, Date and time for scheduled events.

6. Add a Number column for estimates.

Choose `Number`, name it `Estimate hours`, set decimal places and min/max if needed, click `Save`.

Practical example: use Estimate hours with 1 decimal place for effort tracking.

7. Add a Lookup column to link to another list.

Ensure the source list (for example `Projects`) exists on the same site.
Choose `Lookup`, pick the source list, select which column to show (e.g., `Project name`), optionally include additional fields, click `Save`.

Lookup columns work only when the source list is on the same SharePoint site; excessive lookup columns can cause performance issues.

Expected result: a Lookup column lets you pick a value from the source list and optionally shows related fields.

8. Require values or set defaults for columns.

Edit the column settings, enable `Require that this column contains information` if you want to force completion, click `Save`.

9. Set a column-level default value (applies when creating new items).

Edit the column settings, enter the default value in the `Default value` field, click `Save`.

Practical example: set Status default to New so new items start with the correct workflow state.

Reordering columns for the form does not change their required or default settings; edit each column to adjust those.

Make views and filters so teammates see what matters

1. Click the view name dropdown (usually All items) and choose Create new view.
2. Give the view a name, pick the layout (list, compact list, or gallery), and choose Make this a public view if others should use it.
3. Add filters in the view editor.

Open `Filter` and build conditions, for example: `Status is not Done` AND `Owner is equal to [Me]`.

Practical example: create a My active items view with Filter: Owner is equal to [Me] AND Status is not Done and Sort by Due date ascending.

4. Add sorting.

Open `Sort`, pick one or two fields and direction, click `Save`.

5. Group items to create a Kanban-like view.

Open `Group by` and pick `Status`, save the view.

Expected result: the view shows grouped columns for each status value; team members can expand or collapse groups.

6. Set a public default view so teammates land on the most useful view.

Open the view dropdown, select the public view you want, choose `Set as default view` (requires permission to change public views).

Personal views appear only to the creator; public views require list design or site owner permissions to create or change.

Forms, item-level defaults, conditional formatting, and quick edits to speed data entry

1. Reorder or hide fields on the item form without Power Apps.

Open an item or click `Edit form` > `Edit columns`, drag fields into the desired order, show/hide fields, click `Save`.

Expected result: the quick edit form and the new item form follow the new field order.

2. Set item-level default values for new items (per column defaults that apply when users create items).

Open `Integrate` or list `Settings` > `List settings` > choose the column > enter a `Default value` > Save.

Practical example: set Status default to New and Owner default to your team lead to speed item creation.

3. For more advanced form logic, open Integrate > Customize forms to launch Power Apps.

Customizing forms in Power Apps replaces the default list form for that list; test changes before rolling out.

Expected result: the form can include rules, conditional visibility, and richer controls if you use Power Apps.

4. Add simple conditional formatting to highlight rows or values.

Open the view dropdown, choose `Format current view` > `Format view` or `Format columns`, use the designer to add rules, or paste JSON for complex formatting, then Save.

Practical example: highlight overdue items by setting a rule: Due date is on or before Today AND Status is not Done — set a pale red background.

Complex JSON formatting can hide fields or make rows hard to read; test rules on a copy of the view first.

5. Use Quick Edit (grid view) for bulk edits.

Click `Edit in grid view`, change cells inline or paste rows from Excel, then click `Exit grid view` to save.

Expected result: many items update quickly in a spreadsheet-like grid.

Share the list, control permissions and add basic automation

1. Share a link to the list.

Open the list, click `Share`, choose whether recipients can view or edit, copy the link and send it.

Expected result: recipients with appropriate permission can open the list and work with it.

2. Change list-level permissions.

Changing permissions breaks inheritance and can complicate future administration; note who owns the list before changing.

3. Steps to set permissions.

Go to `Settings` (gear) > `List settings` > `Permissions for this list` > `Stop inheriting permissions` if you want unique access, then add or remove users and assign `Read`, `Contribute` or `Design` roles.

Expected result: the list uses its own permissions independent from the site or Team.

4. Add the list to a Teams channel.

In Teams, click the + tab, choose `Lists`, create a new list or add an existing one, and pick the list from the site.

Expected result: the list appears as a channel tab and follows Team permissions.

5. Create a simple Power Automate flow: notify owner when a new item is created.

1. Trigger: When an item is created (SharePoint)
2. Action: Get item (optional, to read lookup fields)
3. Action: Send an email (or Teams message) to the Owner field

6. Steps to create the flow from the Lists UI.

Click `Automate` > `Power Automate` > `Create a flow`, choose `Notify manager when a new item is created`, edit the flow to use your `Owner` column in the recipient field, save the flow.

Expected result: when a new item is added the flow sends a message to the person in the Owner column.

If the flow runs but recipients don't receive messages, check owner values are valid user objects and that tenant policies allow outbound connectors.

Cautions and common problems you'll run into

• Lookup column limits: too many lookup columns or complex lookups can make list views fail to load or block certain views. If you hit limits, consider consolidating data or using a related list and Power Automate.
• Sync and refresh delays: sometimes newly added users or changes to choices take a few minutes to appear; refresh the browser after a short wait.
• Permission inheritance surprises: breaking inheritance gives fine-grained control but increases administrative work and can cause unexpected access issues later.
• Choice editing control: anyone who can edit list design can change choice options unless you restrict permissions.
• When to prefer SharePoint lists or Dataverse: if you need advanced relational data, large scale, or complex business logic, Dataverse or a full SharePoint list with site administration may be a better fit; Lists are great for light to medium tracking needs.

If you rely on Power Automate or Power Apps, check tenant policies for connector and app permissions before building production flows.

Quick FAQ for the questions people ask next

1. How do I export the list to Excel?

Use `Export` > `Export to Excel` from the view menu. That creates a downloadable query file that opens in Excel and retrieves the current list snapshot.

2. How do I restore deleted items?

Open the SharePoint site recycle bin and restore the deleted item or list if available.

3. How do I limit who can edit choice options?

Restrict users' list structure permissions: only give `Design` or higher to the small group who should change choices.

4. Where is audit history stored?

Audit logs are stored in the Microsoft 365 compliance center or the SharePoint audit logs depending on tenant settings; item versioning shows change history when enabled.

Conclusion

Start with a blank list if you want total control, use a template to get prebuilt columns and examples, or import Excel/SharePoint to move existing rows into Lists. Add the columns your team needs, set sensible defaults and required fields, and save public views so teammates land on the right subset of items. Use Quick Edit for bulk changes, apply simple formatting to flag important rows, and add a Power Automate flow to notify owners when new items appear. If you run into limits with lookups or permissions, consider moving the design to a SharePoint-managed list or Dataverse with admin support.

Frequently Asked Questions

Can I change the storage location of a list after I create it?

You cannot move a list between sites directly. Instead save the list as a template (if available) and recreate it on the target site, or export to Excel and import the data on the target site. For Teams, create the list inside the target channel instead.

Does conditional formatting work in mobile?

Some simple formatting appears in the mobile app, but complex JSON view formatting may not render the same. Test critical formatting on mobile if team members use the app.

How do I limit who can create or delete items?

Give users `Contribute` permission to allow add/edit/delete, or `Read` to prevent changes. For finer control, break permission inheritance on the list and assign roles, or use item-level permissions or Power Automate flows to flag or revert disallowed changes.