Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Join us at FabCon Vienna from September 15-18, 2025, for the ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM. Get registered

Reply
ShreyaSrinath
Frequent Visitor

Fabric Capacity - VNET Gateway Uptime

Hello,

 

I am trying to understand the VNET billing structure. Based on the documentation I saw, it looks like the VNET Data Gateway Charge is as follows for the time which the Gateway is on - 

  • CU consumption rate: 2x
  • Price: 2x (CU Consumption rate) * 2 cores (per VNET Data Gateway) * $0.18 (Pay as You Go price for one CU per hour) = $0.72 per VNET / hour 

My question is, what is the capacity usage - 2x what? Is it based on your FSKU? For example, if you have an F4 SKU would it be 4 CU *2? or is it a flat CU rate?

 

And is there any way I can see this broken out by item? Currently, the metrics app only displays the VNET Gateway Uptime as a single row.

 

Thank You!

6 REPLIES 6
v-ssriganesh
Community Support
Community Support

Hello @ShreyaSrinath,

Could you please confirm if your query have been resolved? If they have, kindly mark the helpful response and accept it as the solution. This will assist other community members in resolving similar issues more efficiently.

Thank you.

v-ssriganesh
Community Support
Community Support

Hi @ShreyaSrinath,

May I ask if you have resolved this issue? If so, please mark it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you.

burakkaragoz
Community Champion
Community Champion

Hi @ShreyaSrinath ,

 

Let me break down how VNET Gateway billing works in Microsoft Fabric as simply as possible.

The VNET Data Gateway is billed at a fixed rate: each active gateway member (node) is charged 4 Capacity Units (CUs) per hour, no matter which SKU you’re using. So, if you have three members running for an hour, that’s 12 CUs total. The price per CU depends on your region—for example, in US West it’s $0.18 per CU per hour, so three members for one hour would be $2.16.

You don’t need to worry about “2x” multipliers or your SKU’s core count; the billing is always 4 CUs per gateway node per hour. This is independent of your main Fabric SKU.

To check your usage, go to “Manage connections and gateways” in Fabric and count the number of active gateway members. Multiply that by 4 to get your hourly CU consumption.

Currently, the metrics app only shows the overall VNET Gateway Uptime as a single line. If you want a more detailed breakdown by item, you’ll need to map usage manually or use workspace filters as suggested in the community.

Billing itself appears under “Data Warehouse Capacity Usage CU meter” in your Azure bill and as “VNET Data Gateway Uptime” in Fabric’s Capacity Metrics.

If you have any more questions or need tips on managing costs, just let me know. This topic trips a lot of people up, so you’re definitely not alone.

ShreyaSrinath
Frequent Visitor

Thanks @nilendraFabric for the explaination.

 

Where and how is this billed?

Hi @ShreyaSrinath,
Thank you for reaching out to the Microsoft fabric community forum.

VNET Data Gateway charges are tied to your Fabric capacity (e.g: F4) and appear in your Azure bill under “Data Warehouse Capacity Usage CU meter” and in the Fabric Capacity Metrics app as “VNET Data Gateway Uptime” . Each member consumes 4 CUs/hour ($0.72/hour at $0.18/CU-hour in US West), billed per minute.

Example: 3 members for 30 min = 6 CUs ($1.08). The “2x” formula is outdated; it’s a flat 4 CUs/hour per member.

To track usage, check member count in Manage connections and gateways in fabric and calculate members * 4 CUs/hour.

Thank you, @nilendraFabric for sharing valuable insights.

If this information is helpful, please “Accept as solution” and give a "kudos" to assist other community members in resolving similar issues more efficiently.
Thank you.

nilendraFabric
Community Champion
Community Champion

Hi @ShreyaSrinath 

 

The VNET Data Gateway’s billing structure is based on a fixed CU consumption rate per gateway member (node), independent of your Fabric SKU.

 

Try Use virtualized workspaces/items  to map usage to specific capacities or artifacts

https://blog.fabric.microsoft.com/hr-hr/blog/capacity-platform-updates-for-pause-resume-and-capacity...

 

 

Helpful resources

Announcements
May FBC25 Carousel

Fabric Monthly Update - May 2025

Check out the May 2025 Fabric update to learn about new features.

June 2025 community update carousel

Fabric Community Update - June 2025

Find out what's new and trending in the Fabric community.