Forum Discussion
Connector Creation not working for Azure Storage Table
- 1 year ago
Hi KevinDavison
The issue occurs because Power BI Desktop can connect to your Azure Storage Account (since it runs locally with VPN access), but Power BI Service cannot due to network restrictions. When publishing the report, Power BI Service operates from Microsoft’s cloud, which lacks direct access to your storage account behind a VPN. Even after whitelisting Power BI IPs, the service may still be unable to reach the data source. To resolve this, you can set up an On-Premises Data Gateway, which acts as a bridge between Power BI Service and your VPN-protected storage. Alternatively, you can configure Azure Private Endpoints to allow Power BI Service to securely connect without needing a public IP. Another option is using Azure Active Directory (AAD) authentication instead of an account key for a more secure and reliable connection. Lastly, ensure that data source credentials in Power BI Service are correctly set up with OAuth2 or the appropriate authentication method. Since Microsoft confirmed no errors on the storage account side, the issue is likely due to Power BI Service being unable to establish a direct connection.
Hi KevinDavison
The issue occurs because Power BI Desktop can connect to your Azure Storage Account (since it runs locally with VPN access), but Power BI Service cannot due to network restrictions. When publishing the report, Power BI Service operates from Microsoft’s cloud, which lacks direct access to your storage account behind a VPN. Even after whitelisting Power BI IPs, the service may still be unable to reach the data source. To resolve this, you can set up an On-Premises Data Gateway, which acts as a bridge between Power BI Service and your VPN-protected storage. Alternatively, you can configure Azure Private Endpoints to allow Power BI Service to securely connect without needing a public IP. Another option is using Azure Active Directory (AAD) authentication instead of an account key for a more secure and reliable connection. Lastly, ensure that data source credentials in Power BI Service are correctly set up with OAuth2 or the appropriate authentication method. Since Microsoft confirmed no errors on the storage account side, the issue is likely due to Power BI Service being unable to establish a direct connection.
Yes, this was the reason. Thanks for the explanation!