Azure Blob is great at holding files. Files.com is for working with them: partners sign in to exactly their folders, your team shares files with links, and everything anyone does through Files.com lands in one audit trail. It works on top of any Blob container, yours or a partner's. You don't even have to be an Azure customer.
No credit card required · 7-day free trial · Live in minutes
Real companies. Real file flows. Real results.
Azure Blob stores files cheaply and at huge scale. Files.com handles everyone who needs to work with those files — partners, apps, and auditors — without the files leaving your container.
The container can be yours, or it can belong to a partner, a vendor, or a customer. Pull files out of someone else's container, drop files into theirs, or do both at once. Either way, every move is controlled and logged from your Files.com site.
Most tools can’t touch a locked-down Blob container. Files.com can. Either add Files.com’s published IP addresses to the container’s firewall allow-list, or run a small Files.com Agent inside your network that reaches the container from the inside, so the container never gets exposed publicly at all. On Azure, where storage is usually locked down, that’s often the deciding factor.
Work on AWS, Google Cloud, or your own servers and still connect to a partner's Blob container. All Files.com needs is the storage account name and a key or SAS token from the container's owner. You never sign up for an Azure subscription of your own.
Blob's native endpoint speaks SFTP and nothing else. Files.com puts SFTP, FTPS, FTP, and WebDAV on the same container from one place: every way partners and apps actually connect. There are no proxy servers to build and no firewall haggling for each new partner.
Move, copy, sync, or delete files between Azure and anywhere else. Run it on a schedule, or when a file arrives, with simple if-this-then-that rules. There are no Power Automate flows to build and babysit.
Show the container as a Files.com folder. Reads and writes pass straight through to Blob, with no copy and no sync to wait on. Your team works with the files through the browser, a desktop drive, mobile, or the command line. Use this when you want Files.com to be the place people go to reach the files.
Copy files between Files.com and a Blob container on a schedule, one direction or both. Good for backups, data pipelines, moving cold files to cheaper storage, and shuffling data between clouds.
Kick off a Files.com Automation when a file arrives, on a timer, or when a rule is met. The Blob container can be where files come from, where they go, or both. Files.com treats it like its own storage.
Azure's controls are built for the storage: which apps, keys, and networks can reach the container. Files.com adds the people layer: which partner sees which folder, a log of everything anyone did through the platform, and the same company logins your team already uses.
Hand each person or partner the exact folders they need, and nothing else.
Every upload, download, permission change, and workflow run through Files.com is logged and exportable: the evidence a SOC 2 review or a partner dispute asks for.
People sign in with Microsoft Entra ID or any SAML provider, backed by MFA, with group-based permissions driven from your directory. When someone leaves, you cut their access in one place.
Files.com can PGP-encrypt and decrypt files automatically as they move, so sensitive data is protected before it lands or gets handed off. Nobody has to remember to do it.
Give partners a Files.com SFTP or FTPS endpoint whose folder is your mounted Blob container. Their uploads land in Blob, get logged, and can kick off PGP decryption, renaming, or routing the moment each transfer completes. Your partners install nothing, and you write no custom code to glue it together.
Run a scheduled sync that moves big or rarely-touched files off pricey SharePoint and onto much cheaper Azure Blob. Files.com still serves them back when someone needs them, over SFTP or a share link.
Send files out of Blob with share links you can password-protect and set to expire. Your own team can open and edit Blob documents right in Files.com, while the container stays the system of record.
A partner drops data into their Blob container, or wants you to put files into theirs. Files.com syncs with that container on a schedule, pulling their files in or pushing yours out, and logs every transfer on your Files.com site.
The engine behind every Blob workflow: if-this-then-that rules that route, rename, and clean up files, with no scripts to write and nothing to host.
Learn More
People sign in with the same Entra ID account they already use, and provisioning sets up new users automatically and shuts them off the day they leave.
Learn MoreA per-user record of every action across every protocol, not a storage log: who did what, when, and over which connection.
Learn MoreGive every partner its own scoped credential on a hosted SFTP endpoint, with files up to 5 TB and no server for you to run.
Learn More
Send the Files.com activity record straight into Microsoft Sentinel, the security tool your team already watches.
Learn More
The SMB and NFS file-share side of Azure, in the same account. Move cold data between the two on a schedule.
Learn MoreNovember 17–20, 2026 · San Francisco, CA
Files.com builds deeply on SharePoint, OneDrive, Azure, and Microsoft Entra ID, so of course we’ll be on the floor at Microsoft Ignite telling our File Orchestration story. The legacy MFT vendors won’t be there.
See Files.com At Microsoft Ignite
The shift had to satisfy an Azure hosting constraint while handling partially written files, partner endpoints, and growing system-to-system traffic without custom code.
Read The Story
The team staged the cutover before its seasonal freeze, with Files.com handling API transfers, alerts, and code-free archiving behind the existing partner interface.
Read The Story
The team built one repeatable Files.com pattern for a 150-plus partner population, spanning browser, SFTP, and AS2 traffic into Azure and SAP.
Read The Story
Vendors kept familiar SFTP access while each file landed in Gopuff's own storage for unattended processing.
Read The Story
“Files.com's strengths are simplicity, ease of use, and the cloud connectors. We don't have to invent custom infrastructure for every partner.”
“Files.com is versatile — it can manage many different situations from a single platform. We've consolidated multiple tools onto it.”
“Files.com is robust and scales to a large enterprise. We get multiple files per minute, per second — and we're a 24/7 organization, so everything has to always be up.”
How Files.com connects to Azure Blob, what the native endpoint does and doesn’t do, and where your data actually lives.
Yes. Files.com connects to any Azure Blob container you hold credentials for, whether it's your own, a partner's, a vendor's, or a customer's, and can pull files from it or push files to it. The container does not have to live in your Azure subscription.
No. Many Files.com customers run on AWS, Google Cloud, or on-prem and use the Blob integration only to exchange with a partner or vendor who standardized on Azure. You connect with the storage account name plus an Access Key or SAS Token; no Azure subscription of your own is required.
Yes. Files.com is one of the few MFT options that can reach a private, firewalled Blob container. Either add Files.com’s published IP addresses to the container’s firewall allow-list, or run a small Files.com Agent inside your Azure network and let it reach the container from the inside. In that case the container is never exposed publicly at all.
Use a SAS Token whenever you can: it is the least-privilege option, scoped to a single container or folder with exactly the permissions Files.com needs. An Access Key grants root-level access to the whole storage account and cannot be narrowed, so reserve it for storage used solely by Files.com and rotate it on your normal schedule. Either credential type works. Whichever you choose, make the credential long-lived: the Azure Portal's default 8-hour SAS expiration will lapse mid-workload and stop every mount, sync, and automation that depends on it.
Yes. Files.com supports ADLS Gen2 storage accounts with hierarchical namespace enabled, using directory-aware semantics: folder renames and deletes execute at directory scope, and directory-level permissions follow Azure's ACL behavior.
Yes. Files.com supports the Azure public cloud (default), Azure Government, and Azure operated by 21Vianet in China as connection targets, and automatically uses the correct service endpoints for the selected cloud environment.
No. OneLake exposes ADLS-Gen2-compatible APIs, but its differences prevent the Files.com Azure Blob integration from working with it.
Azure Blob stays the system of record with a Remote Server Mount: Files.com keeps no second copy, and file data passes through Files.com only as needed to serve each request. If you’d rather Files.com keep a copy, for backup, a faster tier, or as the primary store, use a Sync and choose the destination. Files.com has its own high-performance storage, and where the data lives is your call.
Yes. Azure Blob Storage can serve SFTP natively: a setting on any storage account with hierarchical namespace enabled, billed at about $0.30 per hour (~$216 per month) while enabled. The native endpoint speaks SFTP only, caps files at 500 GB, and manages partners as Azure local users outside your RBAC. Files.com adds FTPS, WebDAV, web access, and share links on the same container, takes files to 5 TB, and gives every partner a scoped credential inside one audit trail.
Yes. One mounted container can be reached over SFTP, FTPS, FTP, WebDAV, the web interface, share links, and the Files.com API at the same time. Each partner connects with whatever their system speaks, and every path writes to the same Azure Blob storage and the same audit trail.
Files.com mounts the container in place; the data stays in Azure and every protocol, automation, and permission works against it there. When the job is a one-time move of the contents of the container to S3, Google Cloud Storage, or a flat-rate object store, that is what Mover, the one-time migration tool from Files.com, is for: a free dry run counts the blobs and prices the move, including the Azure egress, before anything leaves the container.
Connect your container, public or firewalled, and run a test transfer to prove the integration on your own workload.
No credit card required • 7-day free trial • Live in minutes