Microsoft Lists forms: collect responses without list access

Key insights

• A Lists form saves submitted answers as an item in its underlying SharePoint list.
• Respondents do not need list access, but they must sign in; anonymous responses are not supported.
• Create the form from a list and choose which existing columns to include.
• Forms can have a title, description, logo, theme, visibility conditions, and branching.
• The SharePoint trigger “When a form is submitted” is identified as a preview in the demonstration.

Microsoft Lists forms let you collect information and save each response directly as an item in the backing SharePoint list, without granting respondents access to that list. This suits teams that need authenticated users to submit structured requests or reports while keeping the list itself restricted. Dhruvin Shah [MVP] demonstrates creating a form from a list and connecting its submissions to a Power Automate flow.

What's new

A Lists form is a form experience built around the columns in a Microsoft List. The list remains the place where the submitted data is stored; the form gives people a way to enter that data without opening the list and using its regular item-entry interface.

This can remove a step from a familiar alternative: create a Microsoft Forms survey, share it, then use Power Automate to copy the response into SharePoint. With a list form, the submission goes directly into the list, so that separate transfer flow is not needed just to save the answers there.

That is different from saying a list form replaces every other form option. The demonstration compares it with the built-in list form, a Power Apps-customized form, and Microsoft Forms, but does not provide a full feature-by-feature comparison. The practical distinction it emphasizes is direct list storage combined with respondents not needing list access.

Who it is for and what you need

This approach is aimed at list owners and makers who need to collect information from people who should not have permission to browse or edit the list. Examples in the demonstration include issue reporting and a request for a replacement keyboard. The respondent still needs to be an authenticated user: the form does not support anonymous submissions.

The form is created from an existing list, so its available questions are based on that list’s columns. Shah’s example uses an Issue Tracker list with fields including Title, Issue Description, Status, Assigned To, Priority, and Associated File. You can choose which fields to put on a form, but the demonstration does not specify a required license, tenant configuration, or regional requirement.

Power Automate is optional if the goal is only to store form submissions in the list. It is relevant when a submission should trigger follow-up work. The SharePoint connector trigger named “When a form is submitted” is described in the demonstration as being in preview; the material does not establish its current rollout or availability beyond that demonstration.

How it works

Start from the Microsoft List that will hold the responses. The demonstration opens the list’s form option, creates a form, and uses fields from the list’s existing structure. Form configuration includes a name, title or description, optional logo, and theme, as well as controls for which columns appear.

1. Open the list and choose its form option, then create a new form or open an existing one.
2. Choose the list columns to include and configure the form’s title, description, logo, or theme as needed.
3. Use conditional logic to show a field only when a condition is met, or to route a respondent to a next field based on an answer.
4. Preview the form. When it is ready, share it using the copy-link option or QR code.
5. After a respondent submits the form, check the list for the new item. The demonstration shows the record appearing in the underlying list.

Form settings shown in the demonstration include an option to receive an email notification for each response and a custom thank-you message. Those are configuration options, not requirements for saving a response. The form also records the signed-in submitter as the Created By user in the example.

For automation, create an automated flow in Power Automate and select SharePoint’s “When a form is submitted” trigger. Configure the site, list, and form, then add the actions needed for the process. Shah uses a Compose action to inspect dynamic content and reports seeing more than 53 properties, including submitted fields such as Title, Issue Description, and Priority.

The trigger is presented as a way to start work when a specific form is submitted, rather than simply reacting to a list item event. The demonstration tests a submission and checks that the flow runs. Possible follow-up actions such as sending an email or generating a document are mentioned as examples, not as preconfigured behavior.

Limitations and open questions

The clearest limitation is authentication: respondents cannot submit anonymously. If anonymous responses are a requirement, the demonstrated list form is not suitable; the material identifies Microsoft Forms as an alternative that can support anonymous submissions in the scenario described.

Do not assume the form makes the list public or changes list permissions. The demonstrated benefit is that a respondent can submit without being granted access to the list itself. The material does not explain how link sharing is governed, whether external guests can respond, or which tenant policies affect access, so check those details in your environment before distributing a form.

The “When a form is submitted” trigger is labeled preview in the demonstration. It does not provide a rollout schedule, licensing details, or confirmation of general availability. It also does not explain how the trigger behaves for every form type or how it compares in detail with the standard “When an item is created” trigger.

Shah’s example establishes the basic list-form path and shows a flow test, but it does not document error handling, permissions for flow owners, or production deployment considerations. Treat the trigger’s preview status and the exact options in your environment as items to verify before relying on it for a business-critical process.

Sources

• Dhruvin Shah [MVP] demonstration of Forms in Microsoft Lists

Frequently asked questions

Do respondents need access to the SharePoint list?

The demonstrated form lets users submit without list access. They must still sign in to submit.

Can a Microsoft Lists form accept anonymous responses?

No. The material says respondents must be authenticated. It names Microsoft Forms as an alternative when anonymous responses are required.

How do you create a form from a Microsoft List?

Open the list’s form option, create a form, select the columns to include, and configure its appearance and logic. Preview it, then share its link or QR code.

Is the Power Automate form-submission trigger generally available?

The demonstration labels SharePoint’s “When a form is submitted” trigger as preview. It does not confirm broader availability or licensing requirements.