A Property Manager Routed Scans From 200 Copier Models Without Relaxing Microsoft Security

A US residential property management and apartment operating company serves more than a hundred communities across a multi-state footprint.

An operation like that runs on documents. Across that footprint, leases, invoices, and property paperwork get scanned on site and have to reach the business systems that process them: six destinations in all, from third-party hosted applications to SharePoint. And the company runs a hardened, all-Microsoft environment, with a security team that holds the line on it. A distributed, paper-heavy operation on one side and a serious security posture on the other: that is exactly where this problem was always going to appear.

The company resolved it with a Files.com gateway that accepted FTP, FTPS, or SFTP from every copier while keeping those devices outside its protected systems. The company could route scans without replacing its mixed-age fleet or relaxing its Microsoft security controls.

Two Hundred Copier Models With Nowhere They Were Allowed to Send

The devices doing the scanning were a long-lived, heterogeneous fleet: about 200 different copier makes and models across those communities, of widely varying ages. None of them could meet the authentication bar the company set for its own systems.

So the copiers were locked out of email and SharePoint entirely. It went further than that: several of the third-party applications the scans needed to reach had no capability to receive files from a copy machine at all. The cost landed on daily work. Staff at every community scanned documents that six systems depended on, and there was no permitted path from the device to any of them.

The obvious fixes were both unacceptable. The security department would not relax the email and SharePoint controls, and even the best copier add-ons could not authenticate their way in. Replacing a distributed fleet of copiers to solve a file-delivery problem was not a serious option either. The company had a device problem, not a document problem: the perimeter was doing its job, and the fleet simply could not follow security requirements upward.

The Fix Had to Speak the One Protocol Family Every Copier Shares

What the company needed was a governed place the copiers could send to, so the documents could keep moving while the devices stayed outside the perimeter. That place had to speak the one capability shared by every copier the company owned, regardless of make, model, or age: FTP and its secure descendants, FTPS and SFTP. It had to keep more than a hundred communities’ worth of devices separated from each other. And it could not become a pile of resident paperwork sitting at rest in the cloud.

The protocol requirement was the hard one. Most modern cloud services have dropped plain FTP, and the oldest devices in the fleet spoke nothing else. The company selected Files.com to be that intake point, in large part because it still covered the whole family.

One Account per Copier, Six Buttons per Device, Seconds on the Platform

Files.com became the gateway between the fleet and everything downstream, and the design was simple enough to describe in one breath.

Every copier got its own Files.com account, locked to its own directory the moment it logged in, all reachable at the company’s own branded scan domain. Each device connected over whichever of FTP, FTPS, or SFTP it could manage, so make, model, and age stopped mattering. The six physical buttons on each copier mapped to six folders. A Files.com on-premise Agent delivered the uploads to a local Windows server, where the sync utility mirrored the directory structure and handled its subdirectories automatically. A PowerShell routing script the company’s team wrote then sorted the files by folder and forwarded each one to the destination that folder meant: a third-party application, a SharePoint site, or an internal inbox. The hardened systems still receive every document. They just receive it from an authenticated internal process instead of from a copier.

The Agent-based design replaced repeated polling, dramatically reduced daily API calls, and eliminated the need to traverse more than a hundred folders manually. It also moved delivery from a delayed schedule to near real time, while the customer-written PowerShell script continued to own the sorting and downstream routing.

Nothing lingers on the platform. A scanned document dwells on Files.com for only seconds before pickup, then Files.com purges it automatically, so sensitive property paperwork never accumulates. And the per-copier accounts double as an audit trail: when the team needs to know when a document was uploaded, they look up activity under that business unit’s username and read the answer off the log.

Six Destinations Fed Without Opening Email or SharePoint

With the gateway in production, the company replaced a deadlock with a standing pattern: legacy devices on one side, hardened or copier-incompatible systems on the other, and Files.com in between.

• Scans from more than a hundred communities reach all six downstream systems, and not one copier connects to email or SharePoint. The existing Microsoft security controls remain in place.
• All 200 or so copier models are covered, and none had to be replaced. Any device that speaks FTP, SFTP, or FTPS is in, which is all of them.
• No scanned document remains on the platform: seconds of dwell, then automatic purge.
• Every upload is attributable to a business unit and a time, a level of accountability a direct device-to-service connection would never have offered.

The pattern also absorbs growth. When a community joins the portfolio, its copiers get accounts locked to their own directories, pointed at the same domain, and the six buttons mean the same six things. The security question never has to be reopened.

The Perimeter Never Opened and the Fleet Never Changed

An employee at any of the communities presses a button on whatever copier happens to be in the office, and the document lands in the system where it belongs.

The lesson travels well beyond apartment management. A legacy device fleet does not have to be replaced, and a hardened perimeter does not have to be relaxed, when the devices are given a Files.com gateway that speaks the one protocol family they all share.