Forum Discussion
Connection to Folder Path fails
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.
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.
v-aatheequeCommunity Support
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.