Power Automate PowerPoint: Populate a PowerPoint Template and Create Slides From Excel

It helps to separate two jobs that both get called "Power Automate PowerPoint", because they have different answers and only one of them is genuinely hard.

The first job is mail-merge into a fixed deck. You have a template with placeholders, you have rows of data, and you want one slide or one deck per row with the numbers swapped in. Layout never changes. This is what the third-party connectors do well, and if that is your job, buy one. The ledger higher up this page prices them honestly, including the cases where they beat us.

The second job is turning this cycle's document into a deck. The quarterly analysis is different every quarter. Sections move, findings change, the emphasis shifts. A placeholder template cannot express that, because the thing that changes is the structure, not the values. Teams try to force it anyway, and the flow grows conditionals until somebody quietly goes back to doing it by hand. That second job is the one Docslide is built for: upload the report or workbook, approve the extracted outline, and export a native .pptx with real editable text boxes, charts rebuilt as native chart objects from your tables, and speaker notes carrying the detail that did not fit on the slide.

Why Microsoft automates Word but not PowerPoint

The asymmetry is documented rather than inferred, which is why it is worth stating precisely. Microsoft's Word Online (Business) connector lists three actions: Convert Word Document to PDF, Create a Microsoft Word document with the given content, and Populate a Microsoft Word template. The connector reference names Microsoft as the publisher and lists the connector as Premium in Power Automate. The Word template mechanism is built on content controls, and Microsoft enumerates exactly which ones work: Plain Text, Combo Box, Drop-Down List, Image and Repeating Section. It also enumerates the ones that do not, including Rich Text, Date Picker and Check Box.

Nothing in that shape exists for PowerPoint. A .pptx has no content-control equivalent, no first-party populate action, and no slide-level API in Microsoft Graph. That is not an oversight anybody is likely to fix soon, because the file format itself never grew the placeholder primitive that makes the Word approach work.

The Graph enumeration that settles the argument

If you want one hard fact to end a design debate, use this one. Microsoft Graph exposes a conversion endpoint at GET /me/drive/items/{item-id}/content?format={format}, and its reference documents exactly three valid values for format: jpg, pdf and html. The supported source list for pdf runs to more than thirty extensions and includes pptx, ppt, pps, ppsx and odp. So Graph will read your PowerPoint. It will never write one, because pptx is not among the three things it can emit.

An enumeration is a stronger form of evidence than prose, because a documented list of everything a system produces proves what it does not produce. This is the same test that settles the equivalent Google question on converting Google Docs to PowerPoint, where the Drive API export-formats reference lists the eight targets a Doc can become and .pptx is not one of them.

What Power Automate Desktop can and cannot do here

Power Automate Desktop is a real answer to this problem and it deserves a fair hearing. It automates the PowerPoint application itself through UI automation, so anything you can do by clicking, it can do by clicking. That includes things no cloud connector will ever reach, like applying a corporate theme or running an add-in.

The costs are structural rather than technical. It needs a Windows machine with PowerPoint installed and, for attended flows, a signed-in session. UI automation breaks when the interface changes, and Microsoft ships interface changes on its own schedule. Running it unattended moves you onto the Process licensing, which Microsoft lists at a much higher rate per bot than a per-user plan. For a nightly job that produces one deck, that math rarely works.

The licensing arithmetic nobody puts in the flow diagram

Third-party connectors are billed on top of Power Automate, not instead of it, so you are paying two vendors for one deck. Power Automate Premium is listed at $15 per user per month on annual billing, and Encodian's own pricing page lists Free at 50 credits, Standard at $49 per month for 500 credits, Midsize at $99 for 1,200, Large at $349 for 5,000 and Enterprise at $549 for 12,000, noting that "most non-utility actions consume 1 credit per operation". A single deck usually costs more than one credit, because populating, merging and converting are separate actions. Budget by operations, not by decks, or the free tier will look far larger than it is.

One US constraint worth checking before you design anything

If you work for a federal agency, a defense contractor, or anyone else in a sovereign Microsoft cloud, check regional availability first. The Encodian PowerPoint connector reference lists it as available in all Power Automate regions except US Government (GCC High), US Department of Defense (DoD) and the China cloud operated by 21Vianet. For those tenants the third-party route is not merely expensive, it is unavailable, which leaves Power Automate Desktop or an approach that never touches the connector catalog.

Where this connects to the rest of your reporting stack

Most flows that want a deck are really recurring report pipelines, and the wider set of options is laid out on automating PowerPoint creation, which compares Paste Link, VBA, python-pptx and cell-binding add-ins such as think-cell on setup effort and what breaks. When the numbers start in a workbook, Excel to PowerPoint covers the single-file case and charts built from your data explains how a table becomes a native editable chart object instead of a pasted picture. Power BI is the one Microsoft source that genuinely does have a scheduled export connector, and its limits are measured on Power BI to PowerPoint. Where the source is a written document rather than a data source, Word to PowerPoint and turning a report into a presentation are the same workflow from the other end, and teams on a monthly cadence usually land on the QBR deck or financial report deck pattern. Anyone scripting against Microsoft 365 should also know that one common source blocks unattended service accounts outright, which is covered on OneNote to PowerPoint. Every Docslide plan exports without a watermark.