Jul 23, 2026

How to Schedule & Email Power BI Reports to External Users (Without a License)

ByPascal Kiefer

Sending a Power BI report on a schedule sounds like it should be trivial. For anyone outside your organization, it usually isn’t.

If you’ve ever tried to set up “email this report to my client every Monday at 8am,” you’ve probably hit two walls. First: the recipient generally needs a Power BI license. Second: if they’re outside your tenant — a customer, a partner, a supplier — native subscriptions often can’t reach them at all. Threads on the Microsoft Fabric Community cover this exact problem, and most end without a clean, low-cost answer.

This guide covers why that happens, the workarounds teams reach for and where each one breaks, and how the Embedsy Portal’s Report Scheduling feature approaches it differently.

Why native Power BI subscriptions fall short

Power BI’s email subscriptions are genuinely useful inside a tenant. Open a report in the Power BI service, click Subscribe, pick a cadence, and recipients get a snapshot in their inbox. The catch is who “recipients” can be.

To receive a subscription, a person generally needs a Power BI Pro (or Premium Per User) license. Reaching genuinely external recipients by email is its own hurdle on top of that — it generally requires Fabric F64 or above, or one of a handful of workarounds. That’s fine for colleagues. It falls apart the moment the audience is external: you can’t license every client, franchisee or trading partner just so they can receive a weekly email, and most of them will never log in to the Power BI service anyway. They just want their numbers, on a schedule, in their inbox.

The result is a gap: the people who most need a hands-off recurring report — the ones outside your four walls — are exactly the ones native subscriptions serve worst.

The workarounds, and where they break

Teams get creative. Here are the common ones, and their failure modes.

Manual export and send

Someone exports the report to PDF and emails it around every week. It works until that person is on holiday, the recipient list grows, or a number was wrong and now twenty inboxes have the wrong version. Manual delivery doesn’t scale and it isn’t reliable.

Power Automate flows

You can wire up a flow that exports a report and emails it. It’s a real option, but it’s a build: someone has to create and maintain the flow, handle authentication, manage the recipient list, and debug it whenever Microsoft changes something underneath. There are smart low-cost variants too — for example, this low-code method uses a PPU license to avoid Premium entirely — but you still own the flow and its upkeep, and it still leans on Power BI service licensing and permissions in ways that get awkward for external recipients.

A public “Publish to Web” link

Some teams fall back to a public link — but that’s public to the entire internet, disabled in most governed tenants for good reason, and offers no row-level security. It’s not a real answer for confidential client data.

Each workaround trades away something you care about: reliability, security, maintenance effort, or the ability to reach external users at all.

How the Embedsy Portal approaches it

The reason external delivery is hard in native Power BI is that it assumes the recipient is a licensed Power BI user. The Embedsy Portal starts from a different assumption: it’s built on Power BI Embedded and runs in your own environment — and Power BI Embedded is the reason the people you serve don’t need individual Power BI licenses. It’s Microsoft’s model for delivering analytics to external users through your app, rather than through licensed Power BI accounts. Microsoft Entra and row-level security sit on top of that to control who can log in and what each person sees.

Report Scheduling extends that same model to the inbox. It’s one of the Portal’s Premium Features, alongside Public Embed and Embedsy Studio. You pick a report, choose the recipients and a cadence, and the Portal exports it — regular reports as PDF, PowerPoint or PNG, paginated reports as PDF or Excel — and emails it on schedule, whether or not the recipient holds a Power BI license. You can also brand the emails themselves: Embedsy offers a range of email design options, so the report lands looking like it came from you, not a generic system message.

On row-level security, the short version: if a recipient already has a Portal account, they automatically get their own view. For people who’ll never log in — a client who just wants a weekly email — an admin picks the security role the schedule should use. So in practice you set up one schedule per client, or one per group that shares the same view, rather than a single blast trying to personalize data for an unlimited list.

How to set it up

Setting it up takes a few minutes inside the Portal: pick a report, a cadence and recipients, choose the row-level-security role for external recipients, and send a test. The full step-by-step is in the documentation.

Which approach is right for you?

If your audience is a handful of licensed colleagues inside your tenant, native Power BI subscriptions are fine — use them. If your audience is external — customers, partners, suppliers, franchisees — or you don’t want to license everyone who might want a report, Report Scheduling in the Embedsy Portal is built for exactly that gap.

It ships as part of Embedsy’s Premium Features bundle — together with Public Embed and Embedsy Studio — for $99/month on top of your Portal plan. See it against your own reports: book a free demo — or read the full setup walkthrough in the documentation.

Get started

Book a free demo Start free trial