Turn a SharePoint form submission into a branded PDF

Why bother making a PDF at all?

Because a PDF is the version you can send outside the building. A purchase request that needs a paper trail, an incident report an auditor will read next year, an application a customer wants a copy of: all of these want a fixed, branded document, not a link to a list item behind your tenant login. The data can live in SharePoint for your team and also leave as a tidy PDF for everyone else. You do not have to choose.

Can SharePoint just do it?

Not on its own. SharePoint holds the data well, but there is no button that turns one list item into a branded PDF. The common workaround is a Power Automate flow that takes the item, drops the values into a Word template, and converts that to PDF. It works. It is also one more flow to own, a template to keep in sync with your columns, and a licence question if you lean on premium actions. When the form and the PDF come from two different tools, they drift.

How does Forms 365 Web build the PDF?

Forms 365 Web has a PDF designer built into the form. You lay out the document once, deciding what goes where, which fields show, and how it is branded, and every submission can be exported to that layout. The PDF and the form come from the same place, so a new field on the form is a field you can drop into the PDF rather than a mapping you patch in a separate flow.

The submission still saves to your SharePoint list as usual. The PDF is the presentation layer on top of the same record, not a second source of truth.

What about internal SharePoint forms?

If the form lives inside SharePoint rather than on the public web, Forms 365 Workspace covers the same ground. It generates a per-submission PDF report from the form, so the record your staff fill in has a document version without you building a template flow behind it. Same idea, different surface: Web for public forms, Workspace for the forms embedded in your SharePoint lists.

Can I get many submissions out, not just one?

Yes, and it is worth being clear about which export suits which job. A PDF is a per-record document, one submission at a time, made to be read or filed. When you want to analyse across submissions, Forms 365 Web exports a single submission to Excel and exports all submissions to CSV. Reach for the PDF when a human needs the document, and the CSV or Excel export when a spreadsheet or a report needs the numbers.

How do I actually set it up?

1. 1

   Build the form and connect it to SharePoint

   Add your fields and point the form at the list that should hold the submissions.

2. 2

   Design the PDF layout

   In the PDF designer, arrange the fields, add your logo and headings, and set the branding so the document reads as yours.

3. 3

   Submit a test entry

   Fill in the form once and confirm the item appears in your list with the right values.

4. 4

   Export the submission to PDF

   Open the submission and export it to the layout you designed. Check the fields land where you expect and the branding holds.

5. 5

   Decide who needs the document

   Keep the PDF for your records, share it with the submitter, or file it against the matching record. The list item stays the working copy for your team.