Updated April 4, 2025: We have updated the rollout timeline below. Thank you for your patience.
In Microsoft SharePoint Online, Microsoft Lists forms are being updated to enhance your list data collection and management. These updates include subscribing to notifications, form scheduling, conditional branching, quick form creation, and additional field-type support.
This message is associated with Microsoft 365 Roadmap ID 124865.
When this will happen:
Targeted Release: We began rolling out early January 2025 and expect to complete by mid-February 2025.
General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-February 2025 and expect to complete by late April 2025 (previously late March).
How this will affect your organization:
Updates to the Microsoft Lists forms include these key improvements:
- New creation experience: Users can now create forms directly from Lists home, SharePoint, and the Lists app in Microsoft Teams. This streamlined process automatically creates the underlying list for responses, saving time and effort.
- Conditional branching: Conditional branching allows you to show or hide questions based on previous answers, ensuring respondents only see relevant questions. You can branch questions to other questions or based on choices in a Choice field.
- Add logo: Enhance your forms with a relevant logo, making them look more professional and reinforcing brand identity.
- Support for Additional Field Types Attachments, Image, Location, Lookup. Please note that for Lookup fields respondents need at least read access to the underlying source list to see and select the options.
- Get notified of new responses and Schedule form Start/End dates: Choose to be notified when someone submits a response to a form you own or have access to. Set specific start and end dates for your forms.
For more information, see Microsoft Lists forms: What’s New.
What you need to do to prepare:
This rollout will happen automatically with no admin action required. You may want to notify your users about this change and update any relevant documentation as appropriate.