Troubleshooting Power BI and Azure Storage Explorer Connection Issues to Data Lake Gen2 from Azure VM

Question

I rented a virtual machine (VM) and had no issues using it until I needed to integrate it with the Data Lake to optimize my processes. I subscribed to the Data Lake, but I cannot connect to it through Power BI when using the VM. My account is a Gmail account, and I can successfully connect to the Data Lake from my personal computer or other devices. However, when I try the same steps on the VM, the connection fails with the error: "Access to the resource is forbidden."

When I attempted to connect using Azure Storage Explorer, I received the following error: "This request is not authorized to perform this operation. RequestId:d1971462-a01e-0008-1dde-4771b8000000 Time:2024-12-06T12:54:35.9257472Z."

I tried connecting via both the account key and a SAS token, but I got the same error. The steps I followed on the VM are identical to those I used on my computer, but the connection still doesn’t work on the VM.

After some investigation, I discovered that this issue might be because my VM and the storage account are located in the same region (US East). It seems the connection is not using the public IP address in this case.

Does anyone know how to resolve this? Any help would be appreciated!

Answer 1

Hi Rafael CST - Thanks for reaching out over Q&A Forum.

Can you confirm if you have any kind of networking restrictions on your storage account? If yes, can you try flipping to All Network and then test ahead? If it connects that the auth appears to be getting blocked on the networking layer.

If there are no networking limitations on the storage account layer, let me know.

Answer 2

Hi @Rafael CST

Welcome to Microsoft Q&A Forum. Thanks for posting your query here!

As we see from the above provided information that there are connection issues when trying to connect to Data Lake Gen2 from Azure VM using Power BI also from Azure Storage Explorer.

As per the above error message, issue could be related to network configuration or authorization issue.

Please try checking the below suggestions to get the issue resolved.

• If there are any firewall settings made, please do check the firewall settings and make sure that the firewall settings for the storage account are properly configured to allow access from the VM. You can do this by checking the firewall settings in the Azure portal and ensuring that the IP address of the VM is added to the allowed IP addresses.
• checked if your account has the necessary permissions to access the Data Lake Gen2? check if your account has been granted the Storage Blob Data Contributor role or the Storage Blob Data Owner role.
• If you have already checked your access permissions and they seem to be in order, then the issue might be related to the VM and storage account which are located in the same region. In this case, the connection might not be using the public IP address.
• Check the region settings: If the VM and the storage account are located in the same region, it's possible that the connection is not using the public IP address. To resolve this, you can try connecting to the storage account using the private IP address of the storage account.

Later, after trying the above. Please do test the connectivity by using the Azure Storage Explorer to test connectivity from the VM. If you continue to receive authorization errors, it may indicate that the VM's network configuration is preventing access.

If the above steps don't work, please do check if there are any network security groups or virtual network service endpoints that might be blocking the connection.

For more information, please refer the below link which might be helpful.

• Troubleshooting connectivity problems between Azure VMs

Hope the above give suggestions helps in resolving the issue.

Please do let us know if there is any else or the issue still persists. We will be glad to assist you closely.

Please do consider to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

Answer 3

As I mentioned before, this happens because they are using the public IP, but since they are in the same region, the private IP works. Now, I don't know how to solve this problem.