Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes! Register now.

Reply
Anonymous
Not applicable

Dataflow refresh Failed AzureBlobs failed to get the response:The remote name could not be resolved

 

Dataflow refresh Failed  "DataSource.Error: AzureBlobs failed to get the response: The remote name could not be resolved 'wabiindcenapcdsa.blob.core.windows.net''.

 

data Source connects on-premises through Gateway M/c.

 

After manual Refresh, It Refreshes but why this problem Occur

 

1 ACCEPTED SOLUTION
Anonymous
Not applicable

Hi @Anonymous ,

 

In the past, users have opened support tickets for this issue with Microsoft's dedicated support team.
After investigation and troubleshooting, the support team found that this was due to the gateway/virtual machine not being able to access several IPs.

 

You can use Telnet or ping commands on the server machine where the gateway is installed to test some ip.
From the gateway machine, try to establish a telnet connection to port 443 on each host.
Troubleshoot the gateway as suggested above and ask your Network admin team to whitelist IPs.

 

You can check the OP shared solution at that time in this thread.

 

Hope it helps,


Community Support Team _ Caitlyn

If this post helps then please consider Accept it as the solution to help the other members find it more quickly.

 

View solution in original post

3 REPLIES 3
Anonymous
Not applicable

Hi @Anonymous ,

 

In the past, users have opened support tickets for this issue with Microsoft's dedicated support team.
After investigation and troubleshooting, the support team found that this was due to the gateway/virtual machine not being able to access several IPs.

 

You can use Telnet or ping commands on the server machine where the gateway is installed to test some ip.
From the gateway machine, try to establish a telnet connection to port 443 on each host.
Troubleshoot the gateway as suggested above and ask your Network admin team to whitelist IPs.

 

You can check the OP shared solution at that time in this thread.

 

Hope it helps,


Community Support Team _ Caitlyn

If this post helps then please consider Accept it as the solution to help the other members find it more quickly.

 

Anonymous
Not applicable

"@Gilb"@GilbertQ

 

 

Hi @Anonymous 

 

Just to confirm it works when you do a manual refresh in Power BI Desktop but not via the Gateway?





Did I answer your question? Mark my post as a solution!

Proud to be a Super User!







Power BI Blog

Helpful resources

Announcements
September Power BI Update Carousel

Power BI Monthly Update - September 2025

Check out the September 2025 Power BI update to learn about new features.

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.

Top Solution Authors