Why the built-in options make this hard
The obvious move is to embed a Microsoft List form or a Microsoft Form on the page. Both work for staff, and both run into the same wall for public visitors.
A form created from a SharePoint list is bound to that site's permissions, so it is not built for anonymous external submitters. Microsoft Forms can take responses from anyone with the link, but those answers go into Microsoft Forms storage, not your list. To move them into a SharePoint list you add a Power Automate flow, and that flow tends to map most fields as plain text and can break when questions are added or removed. You end up maintaining a survey tool, a flow, and a list instead of one form.
The direct way with Forms 365 Web
Forms 365 Web is built for exactly this. You design the form, publish it to a public URL, and every submission is written directly into a SharePoint list in your own Microsoft 365 tenant. No respondent sign-in, no intermediate flow. You can point the form at an existing list or let Forms 365 create the list for you when you publish.
To put it on your own site rather than the hosted URL, drop in the embed snippet. The form renders inside your page in an iframe that resizes to fit its content, so it reads as part of the site rather than a boxed-in widget.
Putting it on your page, step by step
- 1
Build the form
Drag your fields onto the canvas. Add the conditional logic you need, so a field only shows when it is relevant, and mark the questions that are required.
- 2
Connect it to SharePoint
Choose the SharePoint list submissions should write to, or have a new list created on publish, and map each field to a list column.
- 3
Publish and grab the embed code
Publish the form to get its public link and the iframe embed snippet.
- 4
Paste it into your site
Add the snippet to the page in your CMS. The embedded form auto-resizes, so it fits the space without an awkward scrollbar.
- 5
Test a real submission
Fill it in as an outside visitor would and confirm the new item appears in your list with the fields in the right columns.
What you can collect
An embedded Forms 365 Web form is a full form, not a cut-down survey. On a public submission you can gather:
- Text, choice, date, number, and currency fields, with required and validation rules.
- File uploads, so a visitor can attach a document or photo that lands with the record.
- Conditional sections that appear based on earlier answers, without any code.
- A confirmation email to the person who submitted, plus a notification to your team.
If another system needs to know about a submission, Forms 365 Web can send a signed webhook on submit, and there is a REST API for pulling submissions out. Those are the integration points to reach into tools like Make or Zapier. There is no one-click native connector, so treat the webhook as the join.
The data stays yours
Because submissions become SharePoint list items in your tenant, the data sits where your governance already applies. Your list views, column permissions, and any Power Automate flow already watching that list keep working, because a Forms 365 submission is an ordinary new item as far as SharePoint is concerned. You are not exporting customer data into a separate silo to get a nicer form.
Try it on one of your own forms.
14-day free trial. No credit card required.
Common questions
Can a form on my public website save to a SharePoint list?
Yes. Forms 365 Web publishes a form to a public URL and can also be embedded on any website with an iframe snippet. Every submission is written into a SharePoint Online list in your own Microsoft 365 tenant, and the person filling it in does not need a Microsoft account.
Do people need to sign in to submit the embedded form?
No. A Forms 365 Web form is public, so anyone with the page can complete it without a Microsoft or Entra sign-in. That is the main difference from embedding the built-in Microsoft List form, which is tied to your SharePoint site permissions.
Where is the submitted data stored?
Submissions land in a SharePoint list in your Microsoft 365 tenant. Point the form at an existing list or have a new list created when you publish. Because the data is real list items, your existing views, permissions, and any Power Automate flow on that list keep working.