> ## Content Index > Fetch the complete content index at: https://todayfixtech.com/llms.txt > Use this file to discover other available public pages before exploring further. # Microsoft Lists installation: enable for Windows, Teams, SharePoint - URL: https://todayfixtech.com/microsoft-lists-installation/ - Published: 2026-10-30T05:48:34.000Z - Updated: 2026-10-30T05:48:34.000Z - Author: Md Sojib Mia - Tags: Microsoft [Microsoft Lists is available](https://todayfixtech.com/microsoft-365-applications-overview/) when SharePoint Online is provisioned and the Lists service is enabled in your tenant; users also need a Microsoft 365 license that includes SharePoint. As an admin, you must confirm licensing and tenant state, enable Lists in the SharePoint and Microsoft 365 admin centers (and allow the Lists app in Teams if you use Teams), deploy or let users install the Lists app on Windows, Teams and mobile, then verify list creation and permissions. This guide gives exact prerequisites, step-by-step enablement and installation actions, verification steps, and targeted fixes for common problems. ## What you must check before you start - Your tenant has SharePoint Online provisioned; Lists stores data in SharePoint sites and requires SharePoint Online. - Users have a Microsoft 365 / Office 365 plan that includes SharePoint Online (Lists is included with plans that include SharePoint Online). If a user has no SharePoint license assigned, they cannot use Lists. - Admin roles you need: Global admin or SharePoint admin to change tenant and SharePoint settings; Teams admin to manage the Lists app and setup policies in Teams. For enterprise Windows app deployment, Intune admin or access to your software distribution tool is required. Quick checks to run in your tenant: - Confirm SharePoint Online is present and not disabled in the Microsoft 365 admin center (Admin centers > SharePoint shows your SharePoint status). - Verify a sample user has an appropriate license that includes SharePoint Online. - Confirm you have an admin role that can change SharePoint and Teams settings. PowerShell check to show assigned licenses and service plans for a user (MSOnline module): ```powershell Connect-MsolService Get-MsolUser -UserPrincipalName user@domain.com | Select-Object -ExpandProperty Licenses ``` PowerShell (run as Administrator) replace `user@domain.com` with a real UPN. The output shows license SKUs and service plan states so you can confirm SharePoint Online is present. ## Enable Microsoft Lists in your tenant and SharePoint admin center Changing tenant-level SharePoint settings affects all sites. Test changes with a small pilot group before a broad rollout. 1. Sign in to Microsoft 365 admin center as a Global admin or SharePoint admin. 2. Open the SharePoint admin center. 3. In the SharePoint admin center, go to "Settings" on the left navigation. 4. Locate the setting labeled "Lists" or any setting that controls list creation and access. If you do not see a dedicated "Lists" toggle, check related settings that affect list behavior: - "Custom script" / `DenyAddAndCustomizePages` controls customizations but does not disable Lists itself. - "Create site scripts and site designs" and "Modern list and library experiences" affect list behavior and experience. 1. If Lists or list creation is disabled, switch it on and save. 2. Back in the Microsoft 365 admin center, confirm there are no conditional access or service restrictions blocking SharePoint Online: open Admin centers > Azure Active Directory > Security > Conditional Access and verify policies allow SharePoint/Lists activity for the affected users. 3. If you use Teams and want Lists visible there, open the Teams admin center (admin.teams.microsoft.com), go to Teams apps > Manage apps and ensure the Microsoft Lists app is Allowed. Then go to Teams apps > Setup policies and add Microsoft Lists to pinned apps in the Global (Org-wide default) policy or a custom policy, and assign that policy to users or groups. menu names can change slightly as admin centers update, but the settings are in SharePoint admin center > Settings and Teams admin center > Teams apps > Setup policies. ## Install or access Microsoft Lists on Windows, Teams and mobile Windows app (user install or enterprise deployment): 1. For an individual user, open Microsoft Store on Windows and search for "Microsoft Lists". 2. Click Install. 3. For enterprise-wide deployment, use Microsoft Endpoint Manager (Intune) or your software distribution tool to deploy the MSIX/package to devices. 4. In Intune, add the app package (Line-of-business or Microsoft Store for Business) and assign it to device or user groups. if your tenant uses a restricted store, coordinate with device management to allow the Lists app package. Microsoft Teams (admin and end-user steps): 1. As a Teams admin, open the Teams admin center. 2. Go to Teams apps > Manage apps and confirm "Microsoft Lists" is listed and not blocked. 3. Go to Teams apps > Setup policies, edit Global (Org-wide default) or create a custom policy, add Microsoft Lists to the pinned apps, and set its position. 4. Assign the policy to users or groups. 5. Users sign out and sign in to Teams (or wait for policy sync) to see the pinned app. To add a Lists tab to a team channel (end-user steps): 1. Open the desired team channel in Teams. 2. Click the + (plus) button to add a tab. 3. Choose "Lists" from the app list and select or create a list to show in the channel. Mobile apps (iOS and Android): 1. Users install the Microsoft Lists app from Apple App Store or Google Play Store and sign in with their work account. 2. If you use mobile device management (MDM), deploy the mobile app via your MDM solution and configure app protection/conditional access policies as needed. sign-in requires that the account has a SharePoint Online license and is not blocked by conditional access. Access via web and SharePoint: 1. Users can open the Microsoft 365 app launcher and choose Lists or navigate to a SharePoint site and choose "New > List" to create a list. ## Verify it worked and check user access Completion criteria: a test user can create a list, open it in the Lists app, add or edit items, and permissions match expected levels. 1. Use a test account (or ask a test user) to create a simple list in SharePoint or Teams. 2. In Teams, add a Lists tab to a channel and add an item to the list. 3. Open the Lists app (Windows or mobile) and confirm the new list appears and items can be viewed and edited. 4. Check permissions for the site that holds the list: - Open the SharePoint site > Settings (gear) > Site permissions. - Confirm the user or group is listed with the correct permission level (Edit or Contribute for creating/editing list items; Read prevents creating items). 1. Confirm the user has an appropriate license assigned in Microsoft 365 or Azure AD. PowerShell check (PnP PowerShell) to inspect site feature states (useful when a feature appears missing): ```powershell Connect-PnPOnline -Url https://yourtenant.sharepoint.com/sites/sitename -Interactive Get-PnPFeature -Scope Web ``` PowerShell (run as Administrator) replace `https://yourtenant.sharepoint.com/sites/sitename` with your site URL. The command lists active and available features at the Web scope. Expected result: the test user can create and edit list items in SharePoint, Teams, and the Lists app. If any step fails, the specific checks below map to the likely causes. ## Common problems and how to fix them quickly - Missing license Safest first fix: confirm the user [has a license that](https://todayfixtech.com/microsoft-365-mobile-app-features/) includes SharePoint Online and assign it if missing. Deeper troubleshooting: run the MSOnline license check and verify service plans are enabled for the SKU. ```powershell Connect-MsolService Get-MsolUser -UserPrincipalName user@domain.com | Select-Object -ExpandProperty Licenses ``` PowerShell (run as Administrator) - Lists disabled in SharePoint or tenant settings Safest first fix: in the SharePoint admin center > Settings, re-enable list and modern list features or undo the setting that blocks list creation. Deeper troubleshooting: check site policies that block creation, review `DenyAddAndCustomizePages` (NoScript) values, and use PnP to enumerate site features. - Teams app not visible or blocked Safest first fix: in Teams admin center > Manage apps, ensure Microsoft Lists is Allowed. Deeper troubleshooting: check Teams app setup policies (Teams apps > Setup policies) to ensure Lists is pinned or available, and confirm the user’s assigned policy using the Teams PowerShell module. - Conditional Access or authentication blocking sign-in Safest first fix: verify conditional access policies in Azure AD do not block SharePoint or the Lists app for the affected user. Deeper troubleshooting: check Azure AD sign-in logs (Azure AD > Sign-ins) for specific failure reasons and adjust the policy or add exceptions as appropriate. - Windows Store or device management blocking the Lists app Safest first fix: allow the Microsoft Store or make the Lists package available through your managed store. Deeper troubleshooting: deploy Lists via Intune and check installation logs on endpoint devices. - User can see a list but cannot create or edit items Safest first fix: check SharePoint site permissions (Site settings > Site permissions) and ensure the user or group has Contribute or Edit rights on the site or list. Deeper troubleshooting: check item-level permissions, unique permissions on the list, and any retention or governance policies that may prevent edits. when changing permissions or tenant settings, test with a small pilot group before applying changes broadly to avoid unexpected access problems. ## Conclusion After you confirm SharePoint Online and license assignments, enable Lists in the SharePoint admin center, allow and pin the Lists app in Teams if needed, and deploy or let users install the Lists apps on Windows and mobile. Verify with a test account by creating a list, adding items, and checking permissions. If something fails, check license assignment, SharePoint settings, Teams app policies, and Azure AD sign-in/conditional access logs. Use staged rollouts (pilot groups) and management tools such as Intune and Teams setup policies for broad deployments. ## Frequently Asked Questions ### How do I roll out Microsoft Lists to everyone in my organization? Use a staged approach. Assign licenses in batches, enable Lists in the SharePoint admin center, deploy the Windows app through Intune or your deployment tool, and add Lists to a Teams setup policy to pin it for users. Start with a pilot group, confirm functionality, then expand the assignment. ### How can I control who can create lists? Control list creation through SharePoint site permissions and site collection settings. Grant Create and Edit permissions only to the groups that should create lists. For tenant-wide control, use SharePoint admin center settings and use site scripts/site designs to standardize who can provision sites that hold lists. ### Where does Lists store data and how does it integrate with Teams? Lists stores data in SharePoint; each list is a SharePoint list on a site. A Lists tab in Teams uses the underlying SharePoint list for that channel or team, so permissions follow site and team membership. ### Where do I audit usage and troubleshoot errors? Use Microsoft 365 admin center and Azure AD sign-in logs for authentication issues. For SharePoint events, use the SharePoint admin center and audit logs in Security & Compliance to track list creation and access. For Teams app issues, use the Teams admin center and app setup policy logs.