This article contains a list of frequent asked questions (FAQs) about the virtual network (VNet) data gateways.
How can I secure connectivity from my network to Power BI?
Use Private links to secure this connectivity. More information: Power BI Private Links documentation
Where is my VNet data gateway?
The VNet data gateway is physically in the same region as your Azure VNet. However, the metadata (name, details, data sources, encrypted credentials, and so on) for all your VNet data gateways are stored in your tenant’s default region. You can manage all VNet data gateways when you select your tenant’s home region in Power platform admin center.
What data sources are supported on the VNet data gateway?
A complete list of supported data services:
What are the licensing requirements in Power BI to use VNet data gateways?
Virtual network data gateways are a premium-only feature, and will be available only in Power BI Premium workspaces and Premium Per User (PPU) for public preview. Licensing requirements might change when VNet data gateways become generally available.
Some of my data sources are connected to my VNet using service endpoint and some using private endpoint. Can I connect to all of them using VNet data gateways?
Why am I not able to create a service endpoint for my data source in my VNet?
Review Azure VNet documentation for restrictions (for example, region related) on VNets, endpoints, and associated Azure resources.
How do I create a private endpoint for my data sources and associate it to a VNet?
Review the corresponding Azure data service product documentation to check if private endpoints are supported and on how to enable them.
Can I use this feature if my data source is in East US and my Power BI home region is in East US2?
Yes, there's no dependency on the Power BI home region for this feature. If this feature is enabled in the region where the VNet exists, you'll be able to create a new VNet data gateway.
Can I choose the region where VNet data gateways are created?
No. The VNet data gateway is physically in the same region as your Azure VNet. Currently, you also can't choose where the metadata (name, details, data sources, encrypted credentials, and so on) for all your VNet data gateways are stored. It's stored in your tenant’s default region.
Does VNet data gateway support cross-tenant scenarios?
No. The VNet data gateway must be created in the same tenant as the Power BI tenant.
Will I be able to use this feature if my tenant is in East US (United States) and Power platform environment is in Europe?
No, VNet gateways are currently available only in your tenant’s home region.
Why can’t I connect to the data source?
Few areas to check:
- Make sure your data source is up and running.
- Make sure that the data source can be accessed from within the VNet—specifically from the subnet delegated while creating the VNet data gateway. For instance, you could deploy a VM in the subnet and check if you can connect to the data source.
- The following Azure Network Security Groups (NSGs) may be required depending on your scenario:
- Allow outbound traffic to the Azure Active Directory (Azure AD) endpoint while using OAuth authentication to connect to a data source.
- Allow outbound traffic to CA (Certificate Authority) while using HTTPS to connect to a data source.
How is the connectivity between the VNet service and your VNet secured?
The connectivity between the new VNet service and your VNet is via HTTPS and TLS 1.2.
Are there any known connectivity issues for SQL serverless with auto-pause?
For SQL serverless with auto-pause, the first request might fail if SQL is in a paused state, but the next ones will succeed.
Is there a delay when the VNet gateway is used for the first time or after a period of inactivity?
When used for the first time, the VNet gateway takes about 2 minutes to get set up. Similarly, if the VNet data gateway isn't used for 30 minutes, you could experience a delay of about a minute the next time you use it.
Is this feature supported in sovereign clouds?
No, only commercial clouds will be supported for the public preview release.
What is the hardware configuration for a VNet data gateway?
Every VNet data gateway has a maximum capacity of:
- 2 cores
- 8 GB of RAM each
At this time, this is the only available hardware configuration and it can't be scaled or changed.
Can I create multiple VNet data gateways for the same Azure data service?
Why can't I delete the subnet or the VNet that delegated to Power Platform?
Check if there are other gateways using the same VNet and subnet. To be able to delete, it would take up to 48 to 72 hours after the last gateway using this VNet and subnet was removed.
How large does the delegated subnet need to be?
Beyond the five reserved IPs, our recommendation is to have approximately 5-7 more IPs so you can add more VNet gateways to the same VNet and Subnet.
I'm a subscription owner but get an error when I try to create a subscription
Make sure you're explicitly in a role with the Microsoft.Network/virtualNetworks/subnets/join/action permission on the VNet like the Azure Network Contributor role. This permission is required for creating a VNet data gateway.
Does all of the data when using the VNet data gateway remain on Microsoft's backbone network when accessing Azure Data Sources?
How does security compare to the on-premise data gateway? Yes, all the data going through a virtual network data gateway remains on the Azure backbone. We use Swift between the virtual network and Power BI service so no public internet is ever used. On the other hand, the on-premise data gateway opens a connection to use Azure Relay to connect to the Power BI service.
Which Azure components need to be in the same region?
Considering the various resources: subscription, Microsoft.PowerPlatform resource provider, virtual network, subnet, and Power BI Service's home tenant. The virtual network and subnet should be in the same region as the data to which you're connecting. The data gateway configuration lives in the Power BI home tenant region.
Is there any way to connect from the subnet of one VNet to the data source of another VNet?
A VNet gateway can generally reach sources that are reachable within that same VNet. If there's another VNet that's completely isolated from the first, then another VNet gateway is necessary.
Any other known issues?
- The VNet's subnet's IP range can't overlap with 10.0.1.x.
- You can't delegate a subnet called
gatewaysubnetto the Power Platform admin center. This restriction is because it's a reserved word for the Azure Gateway Subnet feature.
- You can't change the region, subscription, or resource group for the VNet on which the VNet data gateway was created. This scenario isn't currently supported.
- If an OAuth refresh that takes longer that one hour is canceled with the error "Invalid Connection Credentials" or timeout, the issue is likely that the credential expired.
- VNet data gateways don't support conditional access policies. When conditional access policies are enabled, Power BI shows a "DM_GWPipeline_Client_OAuthTokenLoginFailedError" error when you try to update credentials using the OAuth authentication type.