Fabric Capacity Optimization

[ssrinath]

Hello,

I currently have an F4 capacity where the only consumption at the moment is the VNET. Our primary use case for Fabric is the Power BI workload. We have abour 5-7 reports currently.

Yesterday, we changed the storage modes from Direct Query to Import. 

The semantic model sizes are all fairly small, less than 50 MB.

The VNET currently has 5 members.

I was expecting to see a fall in the CU utlization since the change but so far, it looks unchanged. 

At this point, I am not sure why the VNET consumption is eating up the entirety of the F4 capacity.

Any help would be greatly appreciated.

[wardy912]

Hi @ssrinath 

 We have the same issue! VNET gateways continue to use CU the whole time it is up, so depending on how often your datasets refresh, it could be on indefinitely.

Virtual network data gateways capacity consumption | Microsoft Learn

Firstly, minimise data refresh schedule or coordinate so they give the VNET gateway chance to release CU (30 mins inactivity minimum).

Next, make sure surge protection has been configured in the admin portal to prevent capacity limits being reached.

Then, check if you really need the VNET. I can only speak for our use case. We were using it to access storage accounts. We have swapped that out for shortcuts with a private connection.

Private ADLS Gen2 access made easy with OneLake Shortcuts: a step-by-step guide | Microsoft Fabric B...

Hope this helps, please give a thumbs up and mark as solved if it does. Thanks

[ssrinath]

Thanks so much for your response!

We have about 2 or 3 reports that need to be refreshed hourly. All semantic model refreshes are under 10 minutes.

The issue for us is that our source is a data warehouse in Databricks - so we need the VNET unfortunetly. 

I'll definetly check out the Surge Protection though!