\\contosoinvoices01.file.core.windows.net\finance can be mapped as the Z: drive. The two practical problems are that home internet blocks the SMB port, and that signing in with a storage key means everyone is "the same user". Both have fixes.You, the admin: create and map a share
- Storage account › File shares › + File share, name
finance, tier Transaction optimized, quota 500 GiB. - Open the share → Connect. The portal writes a PowerShell script that creates the mapped drive using the storage key; run it on the PC.
- If it fails with a timeout, outbound TCP 445 is blocked by the ISP. Options: connect over the company VPN or ExpressRoute, or use Azure File Sync so users hit the local server instead.
Letting users sign in as themselves
Instead of the key, enable identity-based access under File shares › Active Directory: join the storage account to on-prem AD DS, to Entra Domain Services, or to Entra Kerberos for cloud-joined PCs. Then two layers decide access:
- Share level = an RBAC role on the share: Storage File Data SMB Share Reader, Contributor, or Elevated Contributor (can change NTFS permissions).
- File and folder level = normal Windows NTFS ACLs, set with Explorer or icacls from a mounted client, exactly as on a file server.
Protecting the share
- Snapshots (Share › Snapshots or scheduled by Azure Backup): read-only copies of the whole share, up to 200; users can restore a single file from Previous Versions in Windows.
- Soft delete for file shares: a deleted share survives 1 to 365 days (default 7).
Azure File Sync
Set up: create a Storage Sync Service → install the agent on the Windows server and register it → create a sync group whose cloud endpoint is the Azure share → add the server's folder as a server endpoint, optionally ticking cloud tiering with a free-space target so a 2 TB share fits a 500 GB disk.