Microsoft Lists: latest updates for your team

Microsoft Lists' latest update refreshes the Lists UX across the Lists web app, SharePoint lists and Lists tabs in Teams, adding a drag-and-drop form designer, new view templates (grid and card styles), and suggested rules that surface automations. These are UI-layer improvements that sit on top of the existing SharePoint list engine and connector surface used by Power Platform; they make common form and view tasks easier for non-developers but do not replace Power Apps or change SharePoint list storage limits.

What exactly is changing in Microsoft Lists right now

The update refines how people build forms, pick views and create simple automations. It focuses on the UI and productivity features rather than backend API changes.

• Updated form designer: A refreshed drag-and-drop form editor with grouping controls and conditional visibility rules.

For example: you can hide a field in the form when a status column equals Complete without writing JSON or building a Power App.

• New view types and layout options: Additional grid and card-style view templates and improved previews for column formatting in the UI.

For example: a compact cards view that shows key metadata and a preview image for items in a task list.

• Smart rules and suggestions: The Lists UI surfaces suggested rules and simple automated actions when it detects patterns (for example, suggesting a reminder rule when many items have a due date).

For example: the UI might suggest a rule to send a notification when an item’s Priority column is set to High.

• Improved integration controls for Teams and SharePoint: Clearer choices when adding a list tab in Teams and better handling of links that open the Lists app or SharePoint depending on context.

For example: when you add a list tab to a channel you'll be prompted to open the list in Teams or in the full Lists app; the new form designer is available in both surfaces where supported.

• Performance and scalability tweaks: Background optimizations intended to reduce rendering load for large lists; availability and impact depend on tenant rollout.

For example: views that include many calculated columns should feel more responsive in the updated UI.

These changes are a productivity layer: they reuse the existing list storage, column types and connectors rather than introducing new storage or API surfaces.

How these new features actually work in Teams, SharePoint and the Lists app

The Lists web app and SharePoint lists share the same underlying storage, so forms and views you create in one surface appear in the other once the tenant update is present.

Lists web app and SharePoint site lists

The new form designer and view templates appear in the Lists web app and in SharePoint list pages when the tenant has received the update. A form edited in the Lists app is used by the same list in SharePoint.

For example: create a project intake list in the Lists web app, design a conditional form that hides budget fields until Approved is checked, then open the same list on the SharePoint site and see the same conditional behavior.

Teams

When a list is added as a Teams channel tab you get a Teams-optimized hosting surface. The new form designer and suggested rules show inside Teams, but some advanced actions still redirect to the Lists app or the SharePoint site (for example, advanced JSON column formatting editing).

For example: add a list tab, configure the compact cards view, and channel members will see the cards and the same conditional form behavior when they create or edit items in Teams.

Power Platform and Power Automate

Power Apps and Power Automate continue to use the same connectors and list schema. The new form designer is a non-developer tool for entry forms; it does not replace Power Apps for complex logic or custom UI.

For example: use the new form designer for basic data entry while keeping existing Power Automate flows; if a flow references internal column names or expects specific JSON payloads, test it after changing the list schema or forms.

Migration and compatibility notes

• Existing lists keep working; the UI changes do not rewrite list data.
• If you replace a Power Apps customized form with the new form designer, the Power Apps form remains available but will not be used unless you explicitly switch back to it.
• Column internal names, column types and lookup relationships are unchanged. Any Power Automate flows or Power Apps that reference those should continue to work, but test flows that depend on calculated columns or precise formatting.

These updates are a productivity layer for common scenarios while complex customizations still rely on Power Platform or direct SharePoint configuration.

Which tenants and licenses get the updates and what admins must do

Which plans include the features

• The UI updates are included with Microsoft 365 subscriptions that include SharePoint Online (business and enterprise plans that include SharePoint). There is no separate license for the updated Lists UX.

Rollout timing and release rings

• Microsoft rolls UI updates gradually; availability can vary by release ring (Targeted Release vs Standard). If some users in your tenant see the update and others don’t, that usually means a staged rollout.

Admin controls and tenant settings to check

1. Check release preferences in the Microsoft 365 admin center.

Settings > Org settings > Release preferences

2. Review SharePoint admin center settings for modern experience and any site-level policies that could block modern UI features.

SharePoint admin center > Settings > Site permissions and Experience settings

3. Check Message Center and Service health for feature-specific notes and timing.

There is no single on/off toggle specifically for the new Lists UI; availability depends on Microsoft's rollout and modern experience settings in SharePoint.

Steps to check basic tenant readiness

1. Open the Microsoft 365 admin center and confirm your Release preferences.
2. In the SharePoint admin center, confirm that modern experience is permitted for the site collections where your lists live.
3. Review Message Center posts and the Microsoft 365 Roadmap entries for Lists updates.

If you restrict modern experience or apply strict conditional access policies, pilot the update on a test tenant or test site before broad rollout.

Admin actions to plan

• Run a pilot with a small set of sites or a project team to validate the new form designer, view templates and suggested rules.
• Communicate to stakeholders that Power Apps custom forms remain available; switching between form systems is explicit and should be planned.
• Update internal documentation and training for list creators to include the new designer and view templates.

What the updates don’t solve and common misconceptions

The updates improve usability but do not replace Power Apps or change SharePoint list core limits.

Practical limits and what remains unchanged

• SharePoint limits: List scale and thresholds remain governed by SharePoint limits (item counts, lookup column thresholds). The UI improvements do not change those limits.
• Power Apps requirement: Power Apps is still necessary for complex form logic, custom connectors, or embedded applications that require controls beyond conditional visibility and basic layout.
• Advanced formatting: Column formatting with JSON and some site-level configurations still require the SharePoint UI or direct editing; the new form designer is not a JSON editor.

Common misconceptions

• "The new designer replaces Power Apps." No. The designer covers common entry forms and conditional visibility but not complex layouts, custom code or embedded controls that Power Apps supports.
• "Teams equals Lists web app exactly." No. Teams provides a similar experience, but some advanced actions redirect to the Lists app or SharePoint for full capabilities.
• "Automations will always adapt automatically." Most flows continue to work, but any flow that references internal names, calculated columns or specific payloads should be retested after UI changes.

Known gaps and roadmap signals

• Microsoft has signaled additional incremental improvements to views, templates and integrations via the roadmap. If your workflows need richer offline behavior or additional API hooks, expect gradual updates rather than immediate additions.

If a capability is critical, pilot it and monitor Message Center entries and the Microsoft 365 Roadmap for tenant-specific timing.

Where to verify your tenant status and follow the roadmap

Quick checks you can do now

1. Open the Microsoft 365 admin center and go to Release preferences to confirm Targeted or Standard Release.

Settings > Org settings > Release preferences

2. In the SharePoint admin center, open Service health and Message center to find rollout announcements related to Lists.
3. Test a list in the Lists web app and in a Teams channel; if you see the new form designer and view templates, the update has reached that surface.

Numbered checklist to confirm status

1. Verify release preference in the Microsoft 365 admin center.
2. Check Message center for posts mentioning Lists or SharePoint related to the update.
3. Test a list in the Lists web app and in Teams to confirm parity.

Visible differences limited to one surface usually mean staged rollout or client caching; allow 24–72 hours and re-check.

Where to follow official updates

• Microsoft 365 Roadmap: search for "Lists" entries to see planned and rolling features.
• Message Center in the Microsoft 365 admin center: tenant-targeted notices with timing and impact.
• SharePoint and Microsoft 365 admin center service health: for incidents or broader changes.

Use these sources to schedule pilots, inform stakeholders, and confirm when UI elements reach your tenant.

Conclusion

Treat these updates as a way to simplify common list entry and view scenarios while keeping Power Apps for complex requirements. Start with a pilot: confirm your tenant's release preference, run the new form designer and rule suggestions on a noncritical list, and test any Power Automate flows or Power Apps that touch those lists. If the pilot succeeds, update documentation and roll the experience out gradually.

Frequently Asked Questions

Will the new Lists form designer break my existing Power Apps custom forms?

No. Existing Power Apps custom forms remain available. Switching to the new designer is explicit; it does not delete or overwrite Power Apps forms. Still, test your solutions because users might use the new form and bypass Power Apps behavior you depend on.

Do I need to change licenses to get the updated UI?

No. No separate license is required beyond Microsoft 365 plans that include SharePoint Online. Availability is determined by Microsoft’s rollout and your tenant’s release settings.

How do I check whether the update is available in my tenant?

Check Release preferences in the Microsoft 365 admin center, review Message Center posts for Lists updates, and open a list in the Lists web app and in Teams to see whether the new designer and view templates are present.