Power BI Dynamic Subscriptions and Data Driven Report Delivery

The first request sounds straightforward: send every customer their monthly service report. Then the account managers explain what “send” means. Some customers need their finance contact copied. Others want a different message, a named worksheet or delivery into their own secure folder. A few need an invoice summary and an outstanding-jobs report alongside the service figures.

That is where PBRS data-driven scheduling becomes useful. Your delivery records can describe what each customer should receive and how it should arrive. PBRS reads those instructions, generates the appropriate output and delivers it. When a contact or folder changes, you update the driving data instead of rebuilding a separate schedule.

What a Power BI dynamic subscription does

A native dynamic subscription personalizes a report using a recipient semantic model: a Power BI model containing email addresses and the values to map to report filters. It can also take the subject and attachment choice from data. For a team that needs a different view of one report in each inbox, that can be a useful fit.

Native dynamic subscriptions for standard Power BI reports require a Premium- or Fabric-capacity workspace. A PPU license alone does not meet that requirement. The creator also needs Build permission on the recipient model and an appropriate workspace role. Microsoft documents a 1,000-recipient-row limit and single-value dynamic filters in its dynamic subscription guide.

What changes with PBRS

PBRS extends the instructions beyond the recipient and filtered report. A SQL or JSON data driver can supply the information used to name, format, secure, assemble and route the delivery. You do not need to buy capacity just to make that business process possible: PBRS supports applicable Pro and PPU configurations using alternative report-generation methods.

You still need the appropriate Power BI access and a PBRS license. Choose a supported rendering method for your report type; PBRS does not remove Microsoft’s limits from a workflow that explicitly uses Microsoft’s native export API. The practical benefit is that capacity is not a blanket prerequisite for PBRS personalized distribution.

Imagine a customer record that contains an account number, the finance contact, the reporting month and an agreed delivery location. In PBRS, Inserts lets you place those values into the relevant schedule fields. You choose the field from the Inserts panel rather than writing a separate script to substitute it each time.

The same customer number can filter the report, appear in the filename and identify the destination folder. The contact’s name can turn a generic notification into a helpful message: “Hello Sam, your September service pack is attached, including the open jobs we discussed.”

What the data driver can control

• The report and its contents. Supply report selections, Power BI filters and supported paginated-report parameters, so each customer receives the information intended for them.
• The files people open. Drive filenames, supported output formats and Excel worksheet tab names. A workbook can arrive with meaningful tabs rather than names someone has to tidy up afterward.
• The conversation around the report. Populate To, CC and BCC separately, along with the subject, greeting and email body. The customer’s finance team can receive the file while their account manager gets the appropriate copy.
• The delivery route. Use the records to drive configured destination types and their final locations: email for one customer, an FTP or SFTP folder for another, or an agreed storage location.
• The connection behind that route. Supported insert-enabled fields can take mail-server details and credentials, FTP/SFTP credentials and destination paths from the driving data. A customer-specific connection can therefore be part of the delivery instructions, not an extra script maintained elsewhere.
• The protection applied to the output. Use recipient-specific passwords and supported security settings where the selected format allows them. The customer’s workbook or PDF can be protected before delivery.

These are configured PBRS capabilities. Inserts works across supported fields throughout the scheduling workflow; it is not confined to replacing an email address. Set up the destinations and their mappings first, and check the available Inserts options for each field and report type.

Inserts can supply more than a customer record

The PBRS Inserts guide also covers built-in dates and schedule values, user-defined constants, database lookups through Data Items, and reusable message or signature defaults. Supported report-parameter values and event data are available in their relevant schedule types. Custom constants can include formulas and optional JavaScript when a calculated value is needed.

For the monthly pack, that means you can combine the customer’s account number with the reporting period and a consistent signature. Routine personalization does not require custom code. Keep connection credentials in a restricted source and out of filenames, messages and diagnostic output.

Now the customer asks for the service summary, outstanding jobs and invoice detail together. Three separate emails leave them to decide whether the pack is complete. A PBRS data-driven package lets you define the reports as one delivery process.

The driver can determine which reports belong in an individual recipient’s package and supply the filters or parameters for each. PBRS generates the selected reports, collates the results and sends the customer their package. The next customer can receive a different combination, with their own data and delivery instructions.

Choose how the pack should arrive

For a customer who wants to read the results, combine the PDF outputs into one ordered document. For a finance team that needs to work with the numbers, merge compatible Excel outputs into one workbook with named tabs. You can also deliver separate attachments or a ZIP package when keeping the original files is more useful.

PBRS includes options to protect the resulting files. Apply password protection to the final merged workbook or configure the supported PDF security settings for the finished document. This keeps assembly and protection within the reporting job rather than leaving someone to complete them manually.

When several driver records belong to the same email recipient, PBRS can group their reports. Grouping can also merge supported PDF or Excel outputs. That grouping option disables embedding reports in the email body, so choose deliberately between a grouped attachment delivery and an embedded report presentation.

Why Power Automate becomes harder here

A native Power BI dynamic subscription does not provide this recipient-specific, multi-report package assembly. You can build a broader process in Power Automate, but you must design the recipient loop, generate the right reports, wait for their exports, keep each customer’s files together and assemble the final delivery.

Then come the less visible requirements: what happens if the second report fails, how to avoid sending an incomplete pack, how to merge or protect files, and how to retry without duplicating deliveries. Those requirements add actions, expressions, connectors or scripts that someone must maintain as reports and customer instructions change.

PBRS is the better fit when that reporting work is the main job. Data-driven packages, output merging and delivery settings are built into the product. For standard Power BI reports, Power Automate’s Export to File route also inherits the native API’s capacity requirement; using a flow does not make that export available to a Pro-only workspace.

The PBRS report packages overview shows the available package approaches. PBRS works with reports published to Power BI Service, Power BI Report Server and SSRS; it does not schedule exports directly from Power BI Desktop.

If your customer portal already knows who should receive the monthly pack, the PBRS API gives your application a way to manage the reporting configuration. Your application supplies the business instructions; PBRS handles the configured report production and delivery.

You can use the PBRS interface without writing code. For developers who need an integration, the example below shows how a JSON driver and a report filter connect. It deliberately keeps the customer record visible, so the relationship is easy to follow.

{
  "DataDriven": true,
  "DataDriver": {
    "DataDriverType": 1,
    "KeyField": "delivery_id",
    "ValuesJson": "[{\"delivery_id\":\"101\",\"customer_id\":\"C104\",\"recipient_email\":\"review@example.com\"}]"
  }
}

{
  "BasicFilters": [
    {
      "TargetField": "Customers.CustomerId",
      "FieldDataType": "String",
      "FilterLevel": 0,
      "Operator": "In",
      "BasicValues": [
        "<[r]customer_id>"
      ],
      "IgnoreBlankDataDrivenInserts": false
    }
  ]
}

Whether the instructions come from SQL or your application’s JSON, give every driver row a stable identifier. It provides a useful reference when someone asks which record produced a particular pack.

Start with two customers whose requirements differ. Give one an emailed PDF pack and the other an Excel workbook in a test SFTP folder. Use approved test addresses and credentials, then open the finished outputs as the recipients would.

Check the customer data in every report, not just the cover page. Confirm the filenames, worksheet tabs, To/CC/BCC recipients, message, connection and final folder. Try a missing customer identifier and a failed report, too: decide how the job should handle them before it runs unattended. Filtering is not a substitute for access control.

If all you need is one personalized report by email and you already have the required capacity, native dynamic subscriptions may be enough. When the requirement includes different destinations, connection details or a complete report pack for each person, PBRS gives you a more manageable place to keep the process—and supports appropriate Pro/PPU workflows without adding capacity.

Explore personalized Power BI report distribution with PBRS, or see how it fits into Power BI Report Automation. Use the evaluation guide to plan a test with your own customer deliveries.

Download the PBRS Internal Evaluation Guide