The Populate a Microsoft Word template action is the first thing most makers reach for when a flow needs to produce a document, and for a simple letter it is fine. Then the template grows a table, or a logo in the header, or a checkbox, and the flow starts failing in ways the error message does not explain.
Everything below comes from Microsoft's own connector reference for Word Online (Business), read on 15 September 2026. We have grouped it by what it will actually cost you and added the workaround for each. If you already know the limits and want the alternative, skip to the end.
The ones that stop a project
It is a premium connector. In Power Automate and Power Apps, Word Online (Business) is classed Premium. Every user who runs a flow containing it needs a Power Automate Premium licence, or the flow needs a per-flow licence. A Power Apps Premium licence on its own is not enough, which is the single most common surprise in the community forums. Budget for it before you build.
The template cannot live in Dataverse. Supported storage is OneDrive for Business, SharePoint Online sites and Microsoft 365 Groups. Your Dataverse solution can carry the flow, the table and the columns, but the template it depends on sits outside the solution, in a document library someone has to remember to deploy alongside it.
Ten megabytes, in and out. The maximum input file for both actions is 10 MB. A branded template with a couple of high-resolution images gets there faster than you would expect, and the failure is on the run, not at design time.
MFA conditional access breaks it. Quoting the reference: if a multi-factor authentication conditional access policy is enabled, the Populate a Microsoft Word template action cannot be used. Most regulated tenants have exactly that policy.
The ones that limit what the document can be
Five content control types are unsupported. Rich Text, Building Block Gallery, Date Picker, Check Box and legacy form controls. That leaves Plain Text and Picture controls, so no formatted paragraphs from a rich-text column, no tick boxes, no date pickers.
No images in headers. Your letterhead goes in the body, or it goes in as a static image that is not a control.
Nested image controls are not supported, and an image placed through the action does not keep its aspect ratio. It takes the size of the control as drawn in the template, so every picture needs to be resized by hand afterwards or drawn at exactly the right proportions up front.
Every control name must be unique. A quote with "Total" in the summary and "Total" in the footer needs two differently named controls and two mappings.
Repeating sections work, with care. Repeating Section Content Controls are the supported way to render a table of line items. In practice they are fussy to set up, the Developer tab is not available in Word Online so you need the desktop client, Word for Mac cannot create the template at all, and the generated file comes back with its controls locked and greyed out.
The ones that bite in production
Two-minute conversion timeout. A document must convert in under two minutes or the request times out.
Wait a minute after creating the file. The reference recommends adding roughly a one-minute delay before follow-up actions use the file the connector just created. That is a delay in every document flow, forever.
Sensitivity labels block PDF conversion. Convert Word Document to PDF does not support files labelled Confidential or Highly Confidential, which are the labels your contracts are most likely to carry.
One hundred calls per connection per minute. Fine for a button. Not fine for the month-end batch that generates 600 invoices, which will need its own throttling logic.
DisplayBarcode field codes are ignored by the PDF action, so a barcode on a delivery note needs another approach.
What that adds up to
A flow built on this action has a Premium licence dependency, a template stored outside the solution, a hard size cap, a limited set of controls, no header images, a manual image-sizing step, an artificial delay, a throttling ceiling, and an incompatibility with the MFA policy most security teams require. Each one is documented and each one has a workaround. Together they are why "just use the Word connector" turns into a two-week build.
The alternative that removes the list
VerseDocs runs the whole thing inside Dataverse as a plug-in. Because it is not a connector, none of the above applies:
- The template is a Dataverse row, inside your solution, and moves with it between environments.
- Tokens are plain text in the document, so there are no content controls to name, nest or keep unique. Loops, conditionals, images (in headers too) and totals are all part of the template syntax.
- PDF conversion is built in, with no second action, no OneDrive hop and no sensitivity-label exclusion.
- It is called through the Dataverse connector your makers already use, or from a button on the form with no flow at all.
- It runs under the Dataverse plug-in execution model, so an MFA conditional access policy does not enter into it.
- Nothing leaves your tenant, and there is nothing to count: one flat licence covers every document in every environment.