Forum Discussion
Power BI Vnetgateway
HI I have a power bi dataset which is connected to databricks Sql warehouse as souce behind firewall so we use VNET gateway for the same , but when i enruch that data with an excel sheet on sharepoint i get wierd error even though i dont use gateway for that
Which means Power BI (via the Gateway) tried to access SharePoint through a Web request and failed.
If we use gateway for connection does the other source can go direct web cred or it also automatically use gateway
Hi. By default when you use a gateway for at least one source of the semantic model. Then all sources will try to use it. You can configure the gateway at service to allow using both connections on premise + cloud. That will allow the semantic model to run gateway if necessary and use cloud when they can.
You can check these special settings at "Manage gateways and connections". This spanish article shows the hibrid setting:
If you want both at the gateway, then share with us some code and we can think how to make it work. If you want sharepoint to go online and keep databricks at gateway you will need to check that.
I'm not sure the vnet involvement here.
I hope that helps,
Hey olaamigo ,
In Microsoft Power BI, when a dataset uses an Power BI VNet Data Gateway for one source (like your Azure Databricks SQL warehouse behind a firewall), Power BI may try to route all data source queries through the same gateway during refresh. This can happen even if another source such as an Excel file stored in Microsoft SharePoint normally supports direct cloud access.
When the refresh runs in the service, Power BI evaluates the queries together. If the dataset is configured to use a gateway for one source, the service may attempt to execute the entire query pipeline through the gateway environment. In that case, the gateway tries to access SharePoint via a web request. If the gateway network cannot reach SharePoint or the credentials are not configured correctly in the gateway settings, the refresh can fail with the type of error you described.
In general, cloud sources like SharePoint do not require a gateway. However, when a dataset combines private sources (through a gateway) and cloud sources, Power BI sometimes routes the requests through the gateway depending on the privacy levels and query folding behavior. To resolve this, you can try a few things: ensure the SharePoint source has valid credentials configured in the dataset settings, verify that the gateway machine/network can reach SharePoint URLs, and check the privacy levels of both sources so Power BI does not block or reroute the query unnecessarily.
In short, once a gateway is involved for one data source, other sources in the same dataset may also be accessed through the gateway during refresh, which is why your SharePoint request appears to go through it.
If this explanation helped, please mark it as the solution so others can find it easily.
If it helped, a quick Kudos is always appreciated it highlights useful answers for the community.
Thanks for being part of the discussion!!!
5 Replies
Hi. By default when you use a gateway for at least one source of the semantic model. Then all sources will try to use it. You can configure the gateway at service to allow using both connections on premise + cloud. That will allow the semantic model to run gateway if necessary and use cloud when they can.
You can check these special settings at "Manage gateways and connections". This spanish article shows the hibrid setting:
If you want both at the gateway, then share with us some code and we can think how to make it work. If you want sharepoint to go online and keep databricks at gateway you will need to check that.
I'm not sure the vnet involvement here.
I hope that helps,
Hey olaamigo ,
In Microsoft Power BI, when a dataset uses an Power BI VNet Data Gateway for one source (like your Azure Databricks SQL warehouse behind a firewall), Power BI may try to route all data source queries through the same gateway during refresh. This can happen even if another source such as an Excel file stored in Microsoft SharePoint normally supports direct cloud access.
When the refresh runs in the service, Power BI evaluates the queries together. If the dataset is configured to use a gateway for one source, the service may attempt to execute the entire query pipeline through the gateway environment. In that case, the gateway tries to access SharePoint via a web request. If the gateway network cannot reach SharePoint or the credentials are not configured correctly in the gateway settings, the refresh can fail with the type of error you described.
In general, cloud sources like SharePoint do not require a gateway. However, when a dataset combines private sources (through a gateway) and cloud sources, Power BI sometimes routes the requests through the gateway depending on the privacy levels and query folding behavior. To resolve this, you can try a few things: ensure the SharePoint source has valid credentials configured in the dataset settings, verify that the gateway machine/network can reach SharePoint URLs, and check the privacy levels of both sources so Power BI does not block or reroute the query unnecessarily.
In short, once a gateway is involved for one data source, other sources in the same dataset may also be accessed through the gateway during refresh, which is why your SharePoint request appears to go through it.
If this explanation helped, please mark it as the solution so others can find it easily.
If it helped, a quick Kudos is always appreciated it highlights useful answers for the community.
Thanks for being part of the discussion!!!
- If you are combining (merging) an on-premise data source with a cloud data source then the cloud data source MUST use the same gateway.
- If you then remove the merge, or even remove the on-premise data source, the cloud data source will continue to require the gateway
- the only way to now make the cloud data source not require the gateway is to start from scratch.
