SharePoint forms: complete reference
Last updated · By Sean Regan
1. The four form options
Microsoft Forms is a standalone survey service. It is the only one of the four that can collect anonymous or external responses at scale.[2] Its data lives outside SharePoint until you move it.
The modern list form is the form SharePoint renders when someone clicks New on a list. You can reorder and hide fields, show a field conditionally with a formula, and style the header, body and footer with JSON. You cannot add a question that has no matching column type.
A Power Apps customized form replaces that experience with a canvas app.[3] It can do essentially anything, at the cost of a maker's time and, for many connectors, premium licensing.
An SPFx form web part runs as page-level code inside your own tenant.[1] Smart Forms is this category: a designer canvas, 24 question types, AND/OR branching, single-page or wizard layouts, and a results dashboard — writing to a SharePoint list on submit.
2. Where responses are stored
| Option | Response store | Flow required to reach a list |
|---|---|---|
| Microsoft Forms | Forms service + synced workbook | Yes |
| Modern list form | SharePoint list item | No |
| Power Apps form | SharePoint list item (or Dataverse) | No |
| Smart Forms (SPFx) | SharePoint list item, one column per question | No |
This single row — "flow required" — is what most teams underestimate. A Power Automate flow between a form and a list is a second thing to license, monitor, and fix when it silently turns off after a failure streak or an account change.
3. Permissions and who can read responses
When responses are list items, the list's permissions are the confidentiality model.[4] Two settings matter most: item-level permissions (Advanced settings → "Read items that were created by the user" / "Create items and edit items that were created by the user"), and whether the list has broken inheritance from the site.
Respondents need Add Items on the target list, nothing more. In Smart Forms the Questions and Responses tabs are gated behind Manage Lists, so a respondent holding the share link sees only the form.
After any form goes live, confirm the reality rather than the intent: run Smart Permissions against the site and check whether the response list shows as Inherited or Unique, and who resolves into each group.
4. Question types and column mapping
A list form can only render what a column can hold: single line, multiple lines, choice, number, currency, date/time, lookup, person or group, yes/no, hyperlink, image, calculated and managed metadata. Survey constructs — Likert grids, ranking, opinion scales, signatures — have no native column type.
Form layers solve this by projecting a richer question onto ordinary columns: a Likert grid becomes one column per row of the grid, a ranking becomes an ordered text value. Smart Forms provisions those columns for you when you pick the response list, which is why the resulting data is still readable in Excel, Power BI or a view — nothing is stored as opaque JSON.
5. Conditional logic and validation
Modern list forms support conditional visibility through a formula written per column (=if([$Category] == 'Other', 'true', 'false')), plus column and list validation formulas. It works, but the rules are scattered across column settings and are invisible to whoever inherits the list.
A form layer centralizes this. Smart Forms builds condition groups with AND/OR and renders the rule back in plain English, and its pre-flight check flags unreachable questions before you publish — see branching logic without formulas.
6. Attachments and storage impact
File uploads on a list form are stored as list-item attachments and count fully against the site's storage quota. So do documents generated by a flow behind the form, and every retained version of them. A busy intake form with photo uploads is a common cause of unexplained site growth — quantify it with Smart Storage Analyzer rather than guessing, and see the version-history storage calculator for how quickly retained versions add up.
7. Reporting on responses
Because list-backed responses are ordinary items, every SharePoint reporting path works: views with grouping and filters, Export to Excel, Power BI over the list connector, and search. Smart Forms adds an in-page results dashboard, a summary that can segment any question by any other question, a sortable response table and CSV export — so the common "export to Excel and build a pivot" step disappears for routine analysis.
8. How to choose
- Anonymous or external respondents at scale → Microsoft Forms.
- A handful of fields, internal, no survey constructs → the modern list form.
- Complex multi-list writes or bespoke business logic → Power Apps.
- A real form experience whose data must land in a SharePoint list with no flow → an SPFx form web part such as Smart Forms.
Side-by-side matrix: SharePoint form tools compared. Longer prose walkthrough of each option: every SharePoint forms option.
FAQ
- Where do SharePoint form responses get stored?
- It depends on the tool. Microsoft Forms stores responses in its own service and syncs a workbook to OneDrive or a SharePoint site. SharePoint list forms, Power Apps forms and Smart Forms write directly into a SharePoint list as list items, so site permissions, versioning, retention labels and search all apply immediately.
- Do I need Power Automate to get form data into a SharePoint list?
- Only with Microsoft Forms. A SharePoint list form, a Power Apps form or Smart Forms writes the item on submit, with no flow in between and no premium connector.
- How many question types can a SharePoint form have?
- A modern list form is limited to the column types you create on the list. Smart Forms adds a form layer with 24 question types, including Likert grid, ranking, opinion scale, signature and calculated fields that a plain list form cannot render.
- Can respondents fill a SharePoint form without edit rights on the list?
- They need Add Items permission on the target list. Anonymous or external response collection is not possible with an in-tenant list form — that is the one case where Microsoft Forms or a hosted builder is still the right answer.
- How do I stop a form from oversharing data?
- Set item-level permissions on the response list so users can read only the items they created, then verify with a read-only permissions report that the list has not broken inheritance in a way that exposes responses site-wide.
References
- [1] Overview of SharePoint Framework client-side web parts — Microsoft Learn
- [2] Create a form with Microsoft Forms — Microsoft Support
- [3] Customize a SharePoint list form with Power Apps — Microsoft Learn
- [4] Sharing and permissions in the modern experience — Microsoft Learn
