Forum Discussion
Faster Way to Send Customized Paginated Reports as Excel with RLS for ~50 Users
Thanks v-ssriganesh,really appreciate your input!
On the suggestion to chunk recipients and run parallel Power Automate flows:
We actually explored this, but it quickly became more overhead than value. These are lightweight paginated reports, filtered per Regional Manager using RLS, and they render quickly in the Power BI Service, running multiple parallel flows still hits throttling.Key limitation (per Microsoft doc):
“Only one export job per report is allowed at a time per workspace per user.”So:
Running parallel flows from the same workspace/service principal still triggers throttling.
Staggering start times doesn’t reliably avoid it.
Using multiple service principals or duplicating workspaces just to work around throttling feels overly complex for what we’re trying to do — sending 45 filtered reports weekly.
I'm hoping for a simpler, scalable approach that doesn’t require Premium Capacity or multi-principal orchestration, and can bring the total runtime below an hour.
Community SupportHello SlicerSamurai,
Thank you for reaching out to the Microsoft Fabric Community Forum and Thanks GilbertQ for sharing your valuable insights.
As mentioned, third-party tools like Power BI Robots can indeed help automate and speed up delivery of personalized paginated reports. However, since they are outside of Microsoft’s ecosystem, you’d want to review their security, compliance, and licensing before adopting them.
If you prefer to stay within the Microsoft stack, the main ways to reduce processing time on PPU are:
- Chunking recipients into smaller groups and running parallel Power Automate flows.
- Optimizing report rendering to reduce per-export processing time.
For reference: https://learn.microsoft.com/en-us/power-bi/developer/embedded/export-paginated-report#throttling
Best Regards,
Ganesh singamshetty.
Thanks v-ssriganesh,really appreciate your input!
On the suggestion to chunk recipients and run parallel Power Automate flows:
We actually explored this, but it quickly became more overhead than value. These are lightweight paginated reports, filtered per Regional Manager using RLS, and they render quickly in the Power BI Service, running multiple parallel flows still hits throttling.
Key limitation (per Microsoft doc):
“Only one export job per report is allowed at a time per workspace per user.”
So:
Running parallel flows from the same workspace/service principal still triggers throttling.
Staggering start times doesn’t reliably avoid it.
Using multiple service principals or duplicating workspaces just to work around throttling feels overly complex for what we’re trying to do — sending 45 filtered reports weekly.
I'm hoping for a simpler, scalable approach that doesn’t require Premium Capacity or multi-principal orchestration, and can bring the total runtime below an hour.
- v-ssriganesh
Hello SlicerSamurai,
Thanks for the detailed follow-up. it’s very helpful to understand that you’ve already tested parallel flows and confirmed the throttling impact.You are correct that the limitation: "Only one export job per report is allowed at a time per workspace per user" is enforced at the capacity level for PPU workspaces. This means that regardless of how many flows or service principals you use within the same PPU capacity, exports will queue and execute sequentially.
Unfortunately, on PPU there is no supported way to fully eliminate this throttling for a single report in a single workspace. The options that would meet your target runtime of under an hour are:
- Premium Per Capacity enables Dynamic Data Subscriptions which can deliver all personalized versions in parallel directly from the Power BI Service.
- Third-party orchestration tools can sometimes optimize delivery pipelines, though you’d still need to validate performance against throttling limits.
For now, with PPU and the current throttling rules, the runtime you’re seeing is in line with the product’s behaviour.
Best Regards,
Ganesh singamshetty.