Power BI refreshes reports from source files: CSV and Excel on SharePoint, OneDrive, or cloud storage, on a schedule. Files.com collects those files from partners and systems, reshapes them, and lands them where the refresh reads, so dashboards run on data, not on somebody’s morning routine.
No credit card required · 7-day free trial · Live in minutes
Real companies. Real file flows. Real results.
Power BI is disciplined about where it reads: files on SharePoint Online and OneDrive refresh automatically about every hour, scheduled refreshes run on a fixed cadence, and anything on a local path needs a gateway. The data behind the reports is not disciplined at all: it arrives from suppliers over SFTP, from payroll systems overnight, from systems that export raw and name files badly.
Files.com turns that mess into files sitting exactly where the refresh reads. Counterparties deliver into their own scoped folders, TransformScript reshapes what needs reshaping, mounts and syncs land the result in SharePoint or Azure, and monitoring catches the feed that would have made a dashboard quietly wrong.
The same pattern delivers each client its own reports and datasets: publish once, route to per-client folders, and log every download.
Supplier feeds, overnight payroll data, and half-hour dashboard cycles all run on Files.com in production.
Counterparties push CSVs over SFTP, and Files.com routes each one into the SharePoint or Azure location a semantic model reads. Power BI’s own refresh picks the data up from there. No person in the middle, no gateway to babysit.
When dashboards track P&L, a late feed is stale data under a live decision. Counterparty files arrive on schedules as tight as every half hour, then land, validate, and route. Monitoring raises an alert when a delivery window closes without its file.
A supplier pushes a CSV over SFTP into its own scoped folder, and Files.com syncs it to the destination the Power BI dataset reads. The supplier never learns your storage layout, and the dashboard never learns the supplier changed FTP clients.
The file a system exports is rarely the file a dataset wants. TransformScript converts CSV, XML, and JSON in the flow, and Automations rename and split, so the refresh reads clean inputs, not raw exports.
Payroll and operational files that deliver overnight land in SharePoint unattended, so the reporting team finds the data waiting instead of waiting on a person. The audit log holds the record of every arrival.
When source data starts on a server inside your network, the outbound-only Agent carries it out with no inbound firewall rule. The data lands in the cloud location Power BI reads, so nobody stands up a gateway next to every source.
Where the data lands decides how fast Power BI picks it up and whether a gateway is involved at all.
Semantic models connected to files on SharePoint Online or OneDrive get OneDrive refresh: Power BI checks about hourly and syncs changes automatically. Files.com mounts or syncs into those locations, so inbound data flows straight into that cycle.
Scheduled refresh runs up to 8 times a day on shared capacity and up to 48 on Premium. Files.com lands data ahead of whichever cadence you run, so every cycle reads current data instead of yesterday’s.
The on-premises data gateway exists for local files and network shares. Files landed in SharePoint or Azure never need a gateway. The refresh reads them natively, which is exactly why the landing location matters.
Each counterparty or system feeding your reports gets its own scoped credential and folder. Nobody sees anyone else’s data, rotating one credential touches one feed, and every arrival is logged.
Files.com connected on-premises source data to external financial institutions while absorbing each partner’s naming, scheduling, delivery, and archiving requirements.
Read The Story
Files.com let the operations team honor each institution’s connection rules while meeting a one-minute market-data requirement.
Read The Story
Files.com gave global security one governed site while delegated administration kept user and folder changes with the five regional IT teams.
Read The Story
The Files.com Agent connects outbound only, so partner files still cross Defender scanning and land where downstream systems read them, while each country's IT team keeps its own users.
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.”
What BI and reporting teams ask most when wiring data feeds to Power BI.
Power BI has no SFTP data source. Files.com bridges the gap: counterparties deliver over SFTP or FTPS, and Files.com lands each file in the SharePoint, OneDrive, or Azure location the semantic model reads. Power BI’s own refresh takes over from there.
Files.com lands data through Remote Server Mounts and Syncs against SharePoint Online, OneDrive, and Azure storage. A mount writes arriving files straight into the destination. A scheduled sync moves them in batches. Either way, the file is sitting where the refresh reads before the refresh runs.
Power BI’s OneDrive refresh checks files on SharePoint Online or OneDrive about every hour and syncs changes automatically. Scheduled semantic-model refresh adds up to 8 runs a day on shared capacity and up to 48 on Premium capacity, so landing files promptly is what keeps dashboards current.
Files that Files.com lands in SharePoint, OneDrive, or Azure are cloud sources Power BI reads directly, with no gateway involved. The gateway exists for local files and network shares. Data that starts on-premises travels out through the outbound-only Agent instead.
Yes. Files.com converts CSV, XML, and JSON in the flow with TransformScript. Automations rename, split, and route on arrival, so column layouts and file names stay stable for the dataset even when senders are sloppy.
Counterparties send report data to Files.com over SFTP, FTPS, the S3-compatible API, a browser upload, or an email inbox that turns attachments into files. Each sender gets a scoped credential and folder, and PGP-encrypted feeds decrypt automatically on arrival.
Files.com delivery monitoring knows when each feed is due and raises an alert when a delivery window closes without its file. The team hears about it from an alert, not from an executive reading yesterday’s numbers off a live dashboard.
Yes. Files.com Automations pick up exported files dropped in a connected folder and deliver them to each recipient over its own protocol, renamed to its convention and encrypted under its key where required.
Yes. Files.com runs SOC 2 Type II, encrypts in transit and at rest, and records every access. A pre-approved HIPAA business associate agreement comes with Files.com Enterprise. Per-folder retention policies clear delivered files on your schedule.
Files.com replaces the person in the loop: the analyst downloading attachments into a SharePoint library, the script on a desktop moving CSVs, and the silent mornings when neither ran. One File Orchestration Platform receives, reshapes, and lands every reporting feed where Power BI already reads.
Receive, reshape, and land every reporting feed where Power BI reads, with an alert when a delivery window closes without its file.
No credit card required • Free for 7 days • Live in minutes