Generate one Word document through Power Automate and four separate meters start running before the file lands anywhere. A connector licence, a daily request allowance, the flow run itself, and storage for whatever comes out the other end all bill on their own. Microsoft's connector reference classifies the Word Online Business connector as premium tier, and that one classification decides most of what follows. Anyone asking whether the Word Online connector is premium already has the answer. It is, and that status pulls in a chain of licensing most project budgets never itemise.
The connector exposes two actions, populating a Word template and converting a Word document to PDF, per Microsoft's documentation. Neither runs without a qualifying licence on the account that triggers the flow.
Why the Word Online connector needs a premium licence
Because Word Online Business sits in the premium tier, Microsoft requires either a Power Automate Premium licence or a Power Apps Premium licence to use it in a flow. Power Automate Premium currently lists at $15.00 per user per month, billed yearly, per Microsoft's Power Automate pricing page. List prices vary by agreement, so treat that figure as a starting point rather than a quote.
The detail that trips up most rollouts is who needs that licence. Microsoft's licensing guidance states that premium licences are required for every user who triggers a document generation flow through a premium connector, regardless of who built it. Build a flow that fires when any of two hundred sales reps submits a form, and all two hundred need a qualifying licence, unless you license the flow itself instead.
That's the alternative. A Power Automate Process licence, priced at $150.00 per bot per month billed yearly, attaches to the flow rather than to each person who triggers it, and it carries a far larger request allowance than an individual Premium licence. Deciding between licensing every trigger identity or licensing the flow itself is usually the biggest lever in the whole cost picture, and it gets set in the first sprint.
One path skips premium connector cost entirely. Teams already running Dynamics 365 Sales, Customer Service, Field Service, Marketing or Project Service Automation get a built-in Word template feature with five templates included by default, at no additional licence cost beyond the base app, per Microsoft. It's a distinct feature from the Power Automate Word Online connector and doesn't trigger the premium connector requirement when used inside a Dynamics 365 app. Creating or managing templates just needs a System Administrator role. Worth checking before anyone builds a custom flow to do the same job.
What each licence buys you in Power Platform requests
Every licence type carries a daily Power Platform request allowance, and a document generation process spends against it with every action. Microsoft's request limits documentation puts a Power Automate Premium licence at 40,000 requests per user per 24-hour period. A Process licence carries 250,000 requests per 24 hours. Users covered only by an Office 365 licence with Power Platform access get 6,000 requests per day, the smallest of the three tiers.
Populating a Word template counts as at least one action against that allowance, more if the template pulls from multiple data sources. Converting a document to PDF counts as one action per document converted, and retries and pagination requests both count separately too. A flow run itself counts as a minimum of one action regardless of how many internal steps it contains, all per Microsoft. None of that matters much at a hundred documents a month. At ten thousand, with retries and multi-source templates in the mix, it adds up fast.
For high-volume document processes, Process licences stack. Microsoft allows up to ten on a single cloud flow, each adding its own 250,000-request allowance, for a ceiling of 2.5 million requests a day on one flow. A separate Power Platform requests add-on adds 50,000 requests per 24 hours per add-on, but it can't attach to an individual flow, so stacking Process licences is the only lever that raises one flow's ceiling. A five-minute limit of 100,000 requests applies independent of licence type too, and it's the one most likely to bite a batch job that fires thousands of document generations in a short window.
What a flow run costs outside a per-user licence
Not every trigger identity needs a per-user licence. Flows triggered by unlicensed users or by service principals get billed instead to pay-as-you-go metering, per Microsoft's pay-as-you-go documentation. A cloud flow run costs $0.60 in that model, and an attended desktop flow run also costs $0.60. Unattended desktop automation costs $3.00 per run. Runs triggered by a user who already holds a qualifying per-user licence aren't charged again to pay-as-you-go, provided the run stays inside that licence's entitlements, so the two models don't stack on the same execution. Testing a flow in the designer costs nothing, and resubmitting a failed run doesn't get billed twice.
The crossover with per-user licensing is simple arithmetic. A Premium licence costs $15 a month. At $0.60 a run, that buys the equivalent of twenty-five flow runs. A service account triggering fewer than twenty-five document generation runs a month costs less on pay-as-you-go than on a dedicated Premium licence. Cross twenty-five runs and the licence wins, since it covers unlimited runs within its request entitlement rather than billing per execution.
Where storage costs land once the document exists
A generated document has to live somewhere, and Dataverse bills three separate storage types at three separate rates in the pay-as-you-go model. Database storage costs $48 per GB per month once you exceed the 1 GB included allowance. File storage costs $2.40 per GB per month past its own 1 GB allowance. Log storage costs $12 per GB per month with no included capacity at all, per Microsoft's pay-as-you-go meters documentation. Usage gets measured once a day, thirty times a month, and prorated across the billing period.
What matters more than file size is which meter it lands in. A generated PDF sitting in a Dataverse file column costs a fraction of that same file's metadata sitting in a database table, and a process that dumps its errors into log storage pays six times the file rate for them, with no free gigabyte to absorb it. The full breakdown of which meter generated documents should land in covers that decision properly.
There's some flexibility in how overages get absorbed. Unused database capacity can offset file or log overages, and unused log capacity can offset file overages, per Microsoft's capacity documentation. Database overages are the exception, fixed only by freeing space or buying more database capacity outright. None of this cares whether anyone ever opens the document again. Retaining generated output indefinitely is one of the costs that keeps accumulating long after the process that created it stops mattering to anyone.
How the three commercial models behave as volume grows
Third-party document generation tools tend to sell on one of three structures. Per-document or credit consumption charges accumulate for every document generated, with credits typically recharging monthly or requiring an overage purchase once they run out. Per-user subscription charges a fixed monthly fee per user regardless of volume, so cost per document falls as a heavy user generates more. Flat in-tenant licensing charges one upfront or annual fee for unlimited generation with no metering at all, so cost per document approaches zero as volume climbs. A fourth pattern combines a base subscription with usage-based overage once a bundled allowance runs out, which puts a floor under the cost and leaves the ceiling open.
The crossover between these models matters more than the headline rate. Say a credit model charges $0.75 per document and a flat licence runs $3,000 a month. At two thousand documents a month, credits cost $1,500 against the flat fee's $3,000, and credits win comfortably. At four thousand documents, both land at $3,000, the exact breakeven. Past that point the gap opens fast. Eight thousand documents costs $6,000 on credits and still $3,000 on the flat licence, double the price for the same output. A per-user subscription lands between those two. Ten users at $50 a month is $500 fixed, and once that group generates more than 667 documents between them, the per-document cost already beats the $0.75 credit rate. These are illustrative figures to show the mechanic, not quoted prices from any specific product. For real numbers against actual products, the vendor-by-vendor document generation comparison lays those out directly.
None of these figures say what your own estate will pay. That number depends on how many people actually trigger the flow, how many documents that group generates in a working month, which licence tier covers them today, and which storage meter the output ends up in. Feed those specifics into a document automation ROI calculation rather than borrowing a vendor's published rate and hoping it maps onto your volume.