Forum Discussion
Connection to Folder Path fails
Hi All,
I have create a connection to network path folder from connection manager page.
But When I am trying to use the connection in pipeline it give me error access denied to path for the Gateway IP address.
I have confirmed
Use account has access to the path
Gateway has access to Network path
Error I am getting is :
The value of the property '' is invalid: 'Access to connection is denied, resolved IP address , network type is OnPremise'. Access to connection is denied, resolved IP address, network type is OnPremise Activity ID:
Does any has any idea about this kind of issue.
Hi amishra01
This usually happens because the gateway service account doesn’t have the right permissions on the network path, even if your own user account does. When a pipeline runs, it uses the gateway’s credentials to reach the folder, not yours. I’d suggest checking that the folder is accessible directly from the gateway machine, try opening the path while logged in as the gateway service account. Also, make sure the gateway and the network share are on the same domain and you’re using Windows credentials in the connection settings. If it’s a shared folder, always use the full UNC path (like \\ServerName\FolderName) instead of a mapped drive letter. Finally, after making any permission changes, restart the gateway service, that often fixes the “access denied” error right away.
7 Replies
Hi amishra01
This usually happens because the gateway service account doesn’t have the right permissions on the network path, even if your own user account does. When a pipeline runs, it uses the gateway’s credentials to reach the folder, not yours. I’d suggest checking that the folder is accessible directly from the gateway machine, try opening the path while logged in as the gateway service account. Also, make sure the gateway and the network share are on the same domain and you’re using Windows credentials in the connection settings. If it’s a shared folder, always use the full UNC path (like \\ServerName\FolderName) instead of a mapped drive letter. Finally, after making any permission changes, restart the gateway service, that often fixes the “access denied” error right away.
Thanks , Let me try this
Hi amishra01
Just checking in to see if the previous response helped resolve your issue. If not, feel free to share your questions and we’ll be glad to assist.Hi amishra01
Have you had a chance to look through the responses shared earlier? If anything is still unclear, we’ll be happy to provide additional support.
Hi amishra01 ,
Please log into the gateway machine, open File Explorer, and try accessing or mapping the network path directly—if access fails, verify DNS resolution, firewall settings, and ensure the services runs. If non of them works you can open a ticket with Microsoft support.
Thanks,
Sai Teja
My infra team logged in to gateway machine and accessed the folder path , it has permissions.
But my fabric connection still gives the same error.
Hi amishra01
Thanks for confirming. Since your infra team was able to access the folder path and permissions are already in place, but the Fabric connection still throws the same error, this may indicate a deeper configuration or gateway service issue.
At this point, I recommend raising a support ticket with Microsoft Fabric Support and Status | Microsoft Fabric for further investigation.
