Globally unique resources that provide access to data management services and serve as the parent namespace for the services.
Welcome to the Microsoft Azure QnA
Yes, this works with an Azure Files SMB share. It comes down to three things your printer needs to support.
1. SMB version
From SMB security settings: “Supported protocol versions are SMB 3.1.1, SMB 3.0, and SMB 2.1.” A printer limited to SMB 1.0 will not connect.
If it uses SMB 2.1, check one setting first. The same page says “SMB 2.1 is disallowed if Require Encryption in Transit for SMB is enabled (or if the Secure transfer required setting governs SMB behavior), because SMB 2.1 doesn’t support encryption in transit.”
2. Authentication
Same page: “Supported authentication methods are NTLMv2 (storage account key only) and Kerberos.” Your printer will use NTLMv2 with the storage account key.
3. Port 445
From Azure Files networking considerations: “SMB communicates over TCP port 445. Some organizations and internet service providers block outbound traffic on this port. Clients that can’t use port 445 can connect through a VPN or ExpressRoute, or use SMB over QUIC through Azure File Sync.”
If any of these are a problem, scan to a local Windows file share instead and use Azure File Sync to copy the files into Azure Files.
Share the printer model and I can check whether direct scanning is supported.
If this helps resolve your question, please accept the answer or leave an upvote. If not, share more details in a comment so we can continue the discussion and find the right solution.