Here's a scenario that plays out in pretty much every enterprise. Your team is working on the quarterly forecast. Bob opens Q3-Forecast.xlsx in Excel on his desktop. Alice, working from a coffee shop, opens the same file in her web browser. Carol checks the file from her phone before a meeting.

Three different apps. Three different devices. One file.

What happens?

It depends on how files are coordinated, and the answer is often not good. People edit independently, save over each other, and someone discovers hours later that two days of forecasting work just vanished.

What you want is real coordination across desktop Office apps and the web at the same time, on the same shared file, with the locking handled cleanly enough that nobody loses their work.

Why "Just Use the Web Editor" Fails Microsoft Office Teams

The standard advice from cloud collaboration vendors is simple and opinionated. Stop using desktop Office apps. Move everything to the web. Let the platform handle the merging.

Google Docs is the clearest example. Multiple people can edit a Google document at the same time, and the platform merges their changes dynamically. It works well, mostly because everyone is using the same web editor against the same web-native file format.

But here's the catch. Google Docs can open and even edit Microsoft Office files, but it doesn't enforce file locking on those files.

If Bob is editing the spreadsheet in Excel desktop, and Alice opens the same file via Google's web editor, Google doesn't coordinate with Excel desktop to manage the multiple edits. They're operating in different worlds.

For enterprises that have standardized on Microsoft Office, that's a real problem. Most enterprises still run on Word, Excel, and PowerPoint. The forecasting model is an .xlsx file.

The contract template is a .docx file. The board deck is a .pptx file. These files have macros, formulas, formatting, and pivot tables that don't always survive a round trip through a web-only editor.

This leaves you with two unappealing options. Force everyone to use a web editor that may not support what your files actually do. Or accept that collaboration doesn't really exist outside the basic "one person at a time, please" model that came straight from the days of floppy-disk sharing.

How Files.com Handles Co-Authoring and Collaboration

Files.com supports proper Microsoft Office file locking across both the desktop Office applications and our online Office editor. Locking means that while one person has a file open for editing, the platform reserves it so a second person can't overwrite their work.

When Bob opens Q3-Forecast.xlsx in Excel desktop from his Files.com mounted drive, the file gets locked. When Alice tries to open the same file from the web, she sees that Bob has it open. She can view it read-only or wait. When Bob saves and closes, the next person in line gets the lock.

That part is table stakes for any shared drive. The interesting part is the other direction. When Alice opens the file in our online Office editor in her browser, the file gets locked the same way. If Bob then opens Excel desktop and tries to access the file, he sees that Alice has it open.

This sounds simple, but it isn't. Most platforms either support locking for desktop apps (the legacy SMB shared-drive model) or they support web-based collaboration (the SaaS model), but not both coordinated against the same underlying state. Files.com coordinates locking across both worlds.

Cross-channel coordination is what makes this work. The same lock state is enforced whether the file is opened from Office on Windows, Office on Mac, the Files.com web editor, the mobile app, or a mounted drive over WebDAV (the protocol that lets a remote folder show up as a local drive). Whoever opens it first owns the lock until they're done with it.

I'm not aware of another vendor that handles this the way Files.com does. Google's approach removes the lock requirement by using its own editor exclusively, which works well inside Google's editor but breaks down the moment desktop Office is also in the mix. Microsoft's own approach works well within OneDrive and SharePoint but doesn't extend cleanly to non-Microsoft storage. Files.com works across the desktop apps people actually use, on the storage you actually have, with the file formats you actually need to keep.

You can see the same coordination at work in the Microsoft Teams integration.

What Microsoft Office File Orchestration Actually Unlocks for Your Team

The outcome is that your team can use the tools they're already comfortable with, on the files you've already standardized on, without losing work to overwrites.

Bob keeps using Excel desktop because that's where his macros and pivot tables work. Alice uses the web editor because she's traveling and doesn't want to install Office on a borrowed laptop. Carol checks the file on her phone before a meeting. They're all working on the same authoritative copy, and they take turns automatically because the platform coordinates the locks for them.

For administrators, this means you don't have to choose between requiring everyone to use the desktop apps and forcing everyone to a web-based editor. You get both.

For end users, it means collaboration that just works. The file you opened is the file other people see. The changes you save are the changes that survive.

Co-Authoring on a File Orchestration Platform

Most teams that hit the "one person at a time" wall on Microsoft Office files have moved to a single platform that holds the file and coordinates every way of opening it. Files.com is the cloud-native File Orchestration Platform: one platform that replaces the stack of tools IT teams run to move and share files — SFTP and FTP servers, MFT suites, file-sharing apps, and the scripts holding them together. It speaks every protocol, connects 50+ cloud and on-prem systems, automates every transfer, and keeps a complete audit trail.

Co-authoring is one piece of that. The same lock state is enforced across the desktop Office apps, the online Office editor, the mobile app, and a mounted drive, fronting storage you already own — your own S3, Azure, or Google Cloud bucket, or storage reached on-prem over the Files.com Agent. Every open, edit, and save is recorded in the audit log, which is the same record an auditor asks to see for SOC 2 or HIPAA.

To see it in practice, explore Files.com's Microsoft Office for the Web integration or start a free trial — no credit card, live in minutes.