Azure Files is where teams move a Windows file server when they want the cloud but their apps still expect a real file system. What it can't do: let a partner connect over SFTP, hand someone a share link, or tell you who touched what. And it costs a lot per gigabyte. Files.com connects to any Azure file share and adds the outside access, the cheap-storage hand-off, and the controls it was never built for.
The share can be yours, or it can belong to a partner, a vendor, or a customer. Read files from someone else's share, write files into theirs, or do both at once — all controlled and logged on your side.
Azure Files is pricey storage that acts like a network drive; Azure Blob is much cheaper storage in the same account. Files.com is one of the cleanest ways to shuffle files between the two on a schedule — keep the old app running on its file share, push files it rarely touches down into Blob — and connect either one to the rest of your systems.
Let partners reach the Azure file share over SFTP, FTP, FTPS, and WebDAV through Files.com — the ways outsiders connect that Azure Files doesn't offer — while your own people keep using it as a network drive, exactly as before.
Edit documents stored in Azure together online, and send or request files from partners using share links and drop-off folders — with no VPN, no mapped drives, and no Azure access handed to outsiders.
Azure file shares are often locked down so nothing outside the network can reach them. Files.com can still connect — either add Files.com to the firewall allow-list, or run a small Files.com Agent inside your network that reaches the share for you. The share never has to be opened to the internet.
Azure Files handles network-drive access for people inside your company. It has no way to manage the partners and outsiders who reach the share from elsewhere. Files.com adds that part: who can see what, a record of everything, and company logins through Entra ID — all without changing how your own people use the share.
Every action on the share is logged for compliance and for answering questions later — the record Azure Files doesn't keep when you're exchanging files with outsiders.
Decide what each person can do on the share — from read-only to full edit and share — by folder, group, and user, sitting on top of the storage account.
Put Entra ID in front of the connection so people sign in with their company account, and MFA and access rules apply everywhere. Your own staff sign in; outside parties use share links and drop-off folders with no Azure access at all.
Files.com can encrypt and decrypt files automatically as they move on and off the share. Nobody has to remember to do it, and there’s no separate tool to run.
Your own people keep reaching the share as a network drive over SMB and NFS, exactly as before. At the same time, Files.com makes the same share reachable over the web, SFTP, FTP, WebDAV, the desktop app, and the command line — internal access untouched, outside access added.
Connect to Azure US, Azure US Government, or Azure China the same way, so a government or region-restricted workload sets up just like a regular one.
Show the Azure file share as a Files.com folder. Every action goes straight through with no copy and no delay. Use this when you want Files.com to be the way outsiders reach a share that your own people keep using over SMB and NFS.
Copy files between an Azure file share and other Files.com storage on a schedule — one direction or both. Good for backups, getting files out to people, or moving cold files down to cheaper Azure Blob.
Kick off a Files.com Automation when a file arrives, on a timer, or when a rule is met. The Azure file share can be where files come from, where they go, or both — Files.com treats it exactly like its own storage.
A vendor sends files over SFTP, and they land in the Azure file share your own apps already read as a network drive. One share, two ways in, everything logged. No mapped drives and no VPN for the outside party.
Use a drop-off folder to collect documents from outside collaborators — signed forms, finished work — straight into the Azure file share. They get no Azure access, and every action is logged.
A team that grew by acquisition inherits a pile of old Windows file servers and moves them into Azure Files so the old apps keep working — then needs that data connected to the rest of its systems and partners. Files.com serves the share over SFTP and share links, moves cold files down to cheaper Azure Blob, and keeps a record of all of it.
You run on AWS, Google Cloud, or your own servers, but a partner uses Azure Files and wants the exchange on their share. Files.com syncs with that share on a schedule, pulling their files in or pushing yours out. You get a full record of it all, and you never have to sign up for Azure.
The cheaper storage side of Azure, in the same account — move cold files down from the file share to Blob on a schedule.
Learn More
People sign in with their company Entra ID account, get set up automatically, and follow your access rules — from the same tenant that owns the storage.
Learn MoreSchedule and trigger file moves on and off the share — the part that runs the Blob hand-off and partner intake.
Learn MoreLet partners and apps reach the share over SFTP, FTP, FTPS, and WebDAV — the outside-access ways Azure Files doesn't offer.
Learn MoreEvery access, download, and permission change on the share is recorded and exportable for compliance.
Learn MoreSend files out of the share with links you can brand, track, and set to expire — without handing out Azure access.
Learn MoreWhat buyers ask about how Files.com connects to Azure Files, what it costs, and what the integration actually does.
Start a free 7-day trial. Mount your share, run a test transfer, prove the integration works on your workload. No credit card required.
No credit card required • 7-day free trial • Setup in minutes