VNet data gatweway creation

[sba_ur]

Hi all,

I have a new request for creation of VNet gateway. We have a previous capacity (F2) that was being used for another workspace. For the new gateway to be created, can this capacity be reused? Or is it recommended to have a brand new capacity created and tied to the new gateway?

Any thoughts would be appreciated.

Thanks!

[v-pnaroju-msft]

Hi sba_ur,

We are following up to see if what we shared solved your issue. If you need more support, please reach out to the Microsoft Fabric community.

Thank you.

[Poojara_D12]

Hi @sba_ur 

As me my understanding a single Fabric (or Power BI) capacity, such as F2, can technically host multiple workspaces and multiple gateways (including VNet gateways) as long as the overall resource limits—CPU, memory, and concurrency—are not exceeded. So yes, you can reuse the existing F2 capacity for your new VNet gateway if it still has enough available resources and your workloads are not performance-critical. However, from a best-practice perspective, it’s often recommended to provision a dedicated capacity for a new VNet gateway when it will handle large or high-frequency data movements, or when you want to isolate workloads for governance, performance management, or cost tracking. Sharing one capacity between multiple gateways and workspaces can lead to unpredictable performance and refresh delays if one workload consumes more than its share. In summary, reuse is fine for small or related workloads, but a new capacity is advisable if the new gateway will serve a distinct or heavy-use environment.

[v-pnaroju-msft]

Thankyou, @AnalyticPulse and @tayloramy for your response.

Hi sba_ur,

We appreciate your inquiry through the Microsoft Fabric Community Forum.

We would like to inquire whether have you got the chance to check the solutions provided by @AnalyticPulse and @tayloramyto resolve the issue. We hope the information provided helps to clear the query. Should you have any further queries, kindly feel free to contact the Microsoft Fabric community.

Thank you.

[tayloramy]

Hi @sba_ur, 

Gateways aren't attached to a capacity, they're attached ot the tenant. So a gateway will work for all capacities in the tenant. 

So just for the gateway itself, the capacity does not matter. Now, for the new use case that is requiring the gateway, that depends on the usecase. If you have some CUs left in your F2 and it's a small use case, you might be able to get away with using the same capacity. If your use case is larger, you might want to look into getting a new capacity. 

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.

[AnalyticPulse · Accepted solution]

hi @sba_ur 
if there aren't many users in new workspace  then you can use existing capaacity, or else you can use new capacityfor better performance. 

My Work:
Analytic Pulse Blog 
Docynx Productivity Tools