Forum Discussion
Embedded Reports getting rendered despite embedded capacity being paused.
- Anonymous1 year ago
Hi Everyone,
I was able to fix this issue and reports are getting rendered based on capacity status. it was an issue with reports present in the workspace and embedded into portal before assigning the workspace with premium capacity. All the new reports published are getting rendered correctly based on capacity status.
Hi Anonymous ,
Thanks for reaching out in Microsoft Fabric Cmmunity,
When Power BI Embedded (A SKU) capacity is paused, reports should fail to render, typically returning a 403 Forbidden error. However, if the workspace is still assigned to the paused capacity, users may temporarily see cached data before seeing an error. In some cases, the page may appear blank instead of displaying a error message.
As suggested by nilendraFabric , to fully prevent report rendering when capacity is paused, it is recommended to unassign the workspace before pausing. This can be done using the following PowerShell command:
Set-PowerBIWorkspace -Id "WorkspaceID" -CapacityId $null
This ensures that reports don't attempt to load from a paused capacity, preventing any unexpected behavior.
Regarding the capacity status check,
While it is not mandatory, but implementing a capacity status check before embedding can prevent blank pages or errors.
As mentioned by nilendraFabric , one way to handle this is by using the Power BI REST API (GET /capacities) to check the status of the assigned capacity.
You can modify your authentication logic accordingly:
{% assign capacity_status = GetPowerBICapacityStatus() %}
{% if capacity_status == "Active" %}
{% powerbi authentication_type:"powerbiembedded" path:"reportURL;roles:{{formattedUserWebRoles}}" %}
{% else %}
<p>Reports are unavailable because the Power BI capacity is paused.</p>
{% endif %}
This ensures that reports are only embedded when the assigned capacity is active.
Additionally, rohit1991 pointed out some other possible reasons why reports might still render despite the capacity being paused. These include cached credentials, where users with active sessions may still be able to access reports temporarily, and users with a Power BI Pro license might still be able to load reports. Another possibility is that the reports are running on a different active capacity instead of the paused one.
To make sure reports don't load when the capacity is paused, follow these best practices:
- Verify workspace assignment in the Power BI Admin Portal under Capacity Settings to ensure reports are not running under another active capacity.
- Disable Persistent Cache for Embedded Reports in the Admin Portal > Tenant Settings to prevent reports loading from cache.
- Stop the Azure Embedded Resource to restrict access when the capacity is paused.
Hope this helps. Please reach out for further assistance.
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and a kudos would be appreciated.
Thank you.