Has anyone had luck getting a scanner to scan to an Azure file share? This is becoming a reoccuring issue for several of our clients as we move them fully to the cloud.
Scan to folder Azure files
0
As long as you have a Site to Site VPN (with ports 445/139 open), I can't think of any reason it wouldn't work.
I did find a few references to ISPs blocking port 445 (see Azure: Summary of ISPs that Allow / Disallow Access from Port 445 | Microsoft Learn), which may be causing a problem.
Are you getting some kind of error or just general inconsistent problems?
when we go to set it up on the scanners it cannot figure out how to reach the share. It doesn't recognize the path. We can access the shares from windows machines on the same network as the scanners. this has been an issue at multiple clients so it's not a fluke. It just fails to connect. different scanner brands provide different errors but they all boil down to "cannot connect".
Interesting.
I don't have a device to test with, but I'd be curious if Scan to folder works to a server or AVD hosts?
That could help determine if it's a problem with the VPN or some kind of networking issue related to Azure Files.
I haven't had the issue in the past, though admittedly, most of my customers end up with a windows file share on a server, rather than Azure files for this type of purpose. No architectural reason, just customer specific scenarios. If there is a technical blocker, I would be interested to know. That said, if the Azure Files Share is Traditional AD or Entra ID joined, I would expect there is some inconsistency to how the credentials need to be entered on the device. I would recommend simplifying the approach (For testing) as much as possible. My gut says it should work (with appropriate VPN connectivity). Find methods to eliminate parts of the problem (Like Chuck M used to say, troubleshoot or verify 1 problem condition at a time). I like Dave's idea - put a test share on a session host or AD joined server. Good Luck!
Great point, John!
I used to have a lot of inconsistencies when setting-up scan to folder depending on the make/model where I needed to change-up the user format (i.e. DOMAIN\User, user@domain, etc.) for local file servers.
It could be a similar issue in Azure Files depending on your identity provider.
Please sign in to leave a comment.
Comments (5 comments)