Embedded Reports getting rendered despite embedded capacity being paused.

[RamRaut]

I want to embed powerBI reports onto the power page portal and display based on assigned web roles to the User. The required configuration to enable this like enabling powerBI integration in admin centre, creating a new security group in azure and assigning portalId to it is also done. I've setup a new Embedded Capacity with A1 SKU which is been assigned to powerBI workspace which would be serving the reports on the portal.

But despite capcity being paused, reports are getting rendered onto the power page portal.

The configuration with added RLS to access reports is as following

{% assign outputVar = "formattedUserWebRoles" %}
{% powerbi authentication_type:"powerbiembedded" path:"reportURL;roles:{{formattedUserWebRoles}} %}

What other steps are ndded to make sure report rendering is stopped when capacity is paused and How does capacity consumption works in such cases??

[RamRaut · Accepted solution]

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.

[v-veshwara-msft]

Hi @RamRaut ,

We just wanted to check in again regarding your issue. If you’ve found a solution, marking the reply as the solution and leaving a kudos would be greatly appreciated--it helps the community and others with similar questions.

If you’re still facing challenges or have further questions, please let us know.

Thank you.

[Poojara_D12]

Hi @v-veshwara-msft 

Thanks for the kind words.

If possible, please visit my Youtube channel, I upload videos around Power BI, SQL and related things, it will be really helpful and gives motivation to work more on that.

The link to my channel is given below.

[Poojara_D12]

Hi @RamRaut 

If your Power BI reports are still rendering on the Power Pages portal despite pausing the A1 Embedded Capacity, it is likely due to fallback mechanisms such as Power BI Pro licenses or an alternative authentication setup. When Power BI Embedded Capacity is paused, reports should not load unless users have a Pro license, which allows access through the Power BI Service. To confirm this, check if users accessing the reports have Pro licenses and temporarily remove them to see if the reports stop rendering. Also, ensure that the Power BI workspace is explicitly assigned to the Embedded Capacity and not linked to any Premium or Pro environments. Additionally, verify the Power Pages authentication settings to ensure there is no fallback to the Power BI Service, which could still render reports even without Embedded Capacity. Testing by pausing the capacity and restricting access can help determine if another connection method is being used. If reports continue to load, review the workspace settings and Power Pages configuration to eliminate any unintended fallback mechanisms.

 

[v-veshwara-msft]

Hi @RamRaut ,
We haven't heard from you since last response and just wanted to check whether the solutions provided met your needs. If yes, please mark the helpful reply as 'accept as solution' to help others with similar queries. If not, please reach out.
Thank you.

[v-veshwara-msft]

Hi @RamRaut ,
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:

1. Verify workspace assignment in the Power BI Admin Portal under Capacity Settings to ensure reports are not running under another active capacity.
2. Disable Persistent Cache for Embedded Reports in the Admin Portal > Tenant Settings to prevent reports loading from cache.
3. 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.

[rohit1991]

Hi @RamRaut ,

Why Do Reports Still Render? Cached Data → Reports may be loading from previous sessions or browser cache. Power BI Service Backup Mode → Some reports may still load temporarily after pausing capacity. Incorrect Capacity Assignment → Check if the report is using another active capacity.

How to Stop Rendering When Capacity is Paused?

1. Verify Capacity Assignment:

   • Go to Power BI Service > Workspaces and confirm reports are under the paused Embedded Capacity (A1 SKU).
   • Check Admin Portal > Capacity Settings for active assignments.

2. Disable Caching:

   • In Power BI Admin Portal, go to Tenant Settings → Disable Persistent Cache for Embedded Reports.

3. Force Capacity Enforcement:

   • Stop the Azure Resource (Embedded Capacity) in Azure Portal to fully restrict access.

How Does Capacity Consumption Work?

• When paused, the capacity should stop processing reports.
• However, user sessions & cached reports might still render for a short period.

[nilendraFabric]

hi @RamRaut 

When using Power BI Embedded with an A SKU capacity, pausing the capacity should prevent report rendering in embedded applications like Power Pages.

Paused capacities with assigned workspaces may still allow access through cached credentials or fallback mechanisms

Unassign workspaces before pausing.

Use powershell:

Set-PowerBIWorkspace -Id "WorkspaceID" -CapacityId $null


Your current authentication snippet lacks capacity-state checks.try do insert a logic for capacity_status .

Thanks

Thanks

[RamRaut]

What might be the potencial reason for the reports still getting rendered issue, I tried loading reports in new browser instances they are still getting rendered despite capacity being paused.

[RamRaut]

1. What would be the expected scenario incase capacity is paused. Does the report rendering fails with an error displayed on page or it would load blank page?

2. Is capacity state param necessary while using embed query, I don't see it gettting used anywhere.