PDF from Word Template in Power Automate (With Premium Note)

An invoice, a quote, or a contract should be generated automatically as a PDF from a Word template, without anyone opening the file by hand, filling it in, and exporting it. Power Automate comes with its own connector for this: Word Online (Business). It reads a prepared Word template, fills the fields it contains with dynamic values, and then converts the result into a PDF. Before you go down this route, though, there's one thing you should clarify: the connector counts as a Premium connector, and that has a direct impact on your flow's licensing costs.

This article shows how to prepare a Word template for Power Automate, how the flow is built from the template to the finished PDF, and what the Premium classification specifically means for you. It is based on the official connector reference and the licensing documentation on Microsoft Learn. As of: July 2026.

The Word Online (Business) connector at a glance

According to the Microsoft Learn reference for the Word Online (Business) connector, you work with Word files in document libraries that Microsoft Graph supports: OneDrive for Business, SharePoint Online sites, and Microsoft 365 groups. The connector comes with three actions:

• Populate a Microsoft Word template: reads a template and fills its fields with values from the flow; the result is a new Word document.
• Convert a Word document to PDF: converts an existing Word file into a PDF version.
• Create a Microsoft Word document with the specified content: generates a simple Word file from plain text; according to the documentation, it's intended only for use from Copilot Studio.

For the classic "PDF from Word template" use case, you combine the first two actions in one flow. The connector overview also clearly notes that Word Online (Business) is classified as Premium in Power Automate, Power Apps, and Copilot Studio, while it runs as Standard in Logic Apps.

Step 1: Prepare the Word template with content controls

For Power Automate to recognize any fields in a Word file at all, the template must be built with content controls from the Developer tab. You enable this tab in Word via the options; after that, you'll find the matching building blocks in the Controls section.

According to the connector reference, the Word Online (Business) connector currently supports these controls:

• Plain text content control
• Combo box content control
• Drop-down list content control
• Picture content control
• Repeating section content control, for tables with repeating rows

In the properties of each control, you give it a unique display name. This exact name later appears in the Power Automate action as a field that you populate with dynamic values. Rich text, date picker, and checkbox content controls, however, are not supported according to the documentation, nor are older legacy form fields. Afterwards, save the finished template in one of the three supported libraries, i.e. OneDrive for Business, SharePoint Online, or a Microsoft 365 group. Without this storage location, the Power Automate action won't be able to find the file later.

Step 2: Populate the template and output it as PDF

A typical flow for this use case consists of three building blocks:

• Trigger: A manual trigger, a SharePoint list item, or another event supplies the values that should later end up in the template, such as customer name, date, or line-item data.
• Populate a Microsoft Word template: You select the location, document library, and the Word template file. Power Automate then automatically reads in all the content controls it contains and displays them as input fields, which you link to dynamic values from the trigger. The action returns a newly generated Word document.
• Convert a Word document to PDF: This action takes an existing Word file and returns a PDF version. In practice, you first save the result of the first action in the target library and then convert it to PDF in this second action.

One important note from the documentation regarding the transition between the two steps: if the file generated by the first action is used immediately in a follow-up action, Microsoft recommends a short delay of about one minute so the file is reliably available before the conversion accesses it. A delay step between the two actions therefore prevents sporadic errors that would otherwise be hard to reproduce.

Premium license requirement: what this means for you

The most important point before building a flow like this concerns the license, not the technology. According to the connector reference, Word Online (Business) is classified for Power Automate as Premium, for both the action that populates the template and the conversion to PDF. A plain Microsoft 365 license is not enough for this, because Microsoft 365 licenses, according to the Power Automate licensing FAQ, only cover standard connectors, not Premium connectors.

Who actually needs to license the flow depends on the flow type:

• Automated or scheduled flows run in the context of the flow owner. If such a flow uses a Premium connector like Word Online (Business), only the owner needs a Power Automate Premium license.
• Instant flows, which are triggered by a button or from an app, run in the context of the person invoking them. If such a flow contains a Premium connector, every person who triggers it needs their own Premium license. Alternatively, the flow can be equipped with a Process license, in which case licensing individual users is no longer necessary.

In practice, this means: a central flow that automatically generates PDFs from a SharePoint list and is owned by a service account only needs a Premium license for that one account. A flow that ten employees trigger themselves at the push of a button, on the other hand, needs either ten Premium licenses or a single Process license for the flow.

Limits and common pitfalls

Besides the licensing question, the connector documentation lists a number of concrete technical limits that regularly raise questions in practice:

• Maximum file size: For both actions of the connector, the input file may be at most 10 MB in size.
• Conversion time limit: According to the documentation, a file must be convertible within two minutes, otherwise the request times out.
• Confidentiality labels: Files labeled "Confidential" or "Highly Confidential" cannot be processed with the PDF conversion action.
• Throttling per connection: Each connection allows a maximum of 100 API calls per 60 seconds. When generating many documents in bulk one after another, a small time buffer in the flow is worthwhile.
• Multi-factor authentication: If a conditional-access MFA policy is active for the connecting identity, the action for populating the template cannot be used, according to the documentation.
• Nested images and headers: Nested picture content controls are not supported, nor are images inside the template's headers.

If you don't want to build a flow like this on your own, or want to clarify the licensing question beforehand, you'll find support in NordFlux's Power Automate consulting. You retain control over which templates get automated and which license is actually required for it, instead of being surprised by a Premium requirement afterwards.

Frequently asked questions

Do I necessarily need a Premium license for PDFs from Word templates?

Yes. The Word Online (Business) connector is classified as Premium throughout Power Automate, both for populating the template and for converting to PDF. A Standard or plain Microsoft 365 license does not cover these actions.

Is a single Premium license enough for the entire flow?

That depends on the flow type. For an automated or scheduled flow, the owner's Premium license is sufficient. For an instant flow that several people start at the push of a button, either every person triggering it needs their own Premium license, or the flow is given a Process license instead.

Which Word controls can I use in the template?

Plain text, combo box, and drop-down list content controls are supported, as well as picture content controls and the repeating section content control for tables. Rich text, date picker, and checkbox content controls, as well as older legacy form fields, are currently not supported.

Why does PDF conversion fail for some files?

Common causes are a source file that's too large, over 10 MB, a conversion time of more than two minutes, or a confidentiality label such as "Confidential" or "Highly Confidential" that is explicitly not supported by the conversion action.

Can I use a single template to dynamically populate multiple table rows?

Yes, that's what the repeating section content control is for. It lets you mark a table row or a block of text as repeatable and control the number of repetitions via an array from the flow.

Sources: Microsoft Learn – Word Online (Business) connector reference, Microsoft Learn – Power Automate licensing FAQ