Forum Discussion
Fabric Capacity - VNET Gateway Uptime
- 1 year ago
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.
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