Forum Discussion
Cannot save a Dynamic per-recipient subscription for a paginated report.
Hi spehe,
Thanks for reaching out to the Microsoft Fabric Community forum. and thanks to ShivekMaharaj & tayloramy for sharing valuable insights.I reviewed Microsoft's documentation for Dynamic per-recipient subscriptions for paginated reports. Based on the documented prerequisites, your configuration appears to align with the requirements.
Most importantly, Microsoft explicitly lists Microsoft Fabric trial as a supported capacity for paginated reports with dynamic per-recipient subscriptions.
The documentation also requires:
• Build permission to a semantic model containing recipient email addresses and the parameter values.
• Contributor, Member, or Admin access to the workspace.
• Recipient data containing email addresses and the parameters assigned to each recipient.It further explains that the recipient semantic model is used to map recipients to their parameters, with email addresses being the key recipient data used for this mapping.
Given that Fabric trial is explicitly listed as a supported capacity, the reported error may require further investigation. I would first verify the remaining configuration details against the documented prerequisites before drawing any conclusion about the capacity or licensing requirement.
For more details, please refer to the below official Microsoft documentation:
Create a dynamic subscription for a paginated report - Power BI | Microsoft Learn
I hope this helps. Please feel free to reach out if you have any further questions.
Thank you.
Hi spehe,
I think the key distinction here is between your PPU user license and the capacity assigned to the workspace.
Microsoft’s PPU FAQ states that subscriptions which provide different data views to different recipients require Premium capacity. So having PPU personally does not, by itself, satisfy the requirement for a dynamic per-recipient subscription.
The dynamic subscription documentation for paginated reports also treats the workspace capacity as a separate prerequisite.
Since your workspace is currently on Fabric Trial, I would test the same report in a workspace backed by a paid Fabric/Premium capacity if you have access to one. If it saves there, that would strongly point to the trial capacity being the limiting factor rather than the recipient address or report configuration.
Given that you are already getting the Premium-capacity-specific validation message during save, I would focus on the workspace capacity first.
AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.
Hello Shivek and thank you for taking time for this. The main goal of my report is to see what configuration will work for this function before I report back to management about the costs. It is hard for me to understand Microsofts licensing model, but as far as I understand, the cost for a paid Fabric workspace will be hard to justify if I can't show a working model, and unfortunately I do not have any other paid Fabric/Premium capacity.
Hi spehe,
Thanks, and after seeing the workspace confirmation and the clarification from Community Support, I would revise my earlier suggestion about testing this on a paid capacity.
The feature-specific dynamic subscription documentation explicitly lists Microsoft Fabric trial as a supported capacity, so your current workspace should satisfy that prerequisite.
I therefore wouldn't purchase a paid capacity just to validate this scenario. Since the documented requirements appear to be met, I would follow the remaining validation steps Community Support mentioned and, if the same Premium-capacity error persists, have Microsoft investigate it using the Activity, Request and Correlation IDs you already captured.
Thanks for clarifying the setup.
