How Urban One Retired Microsoft OneDrive Without Reconfiguring Wide Orbit

Urban One is the largest African-American-owned broadcasting company in the United States. Its radio division operates 74 stations across 14 major markets, its Reach Media subsidiary syndicates programming to hundreds of affiliate stations, and across radio, television, and digital the company reaches roughly 80 million consumers a month.

Radio at that scale is a production business, and production runs on files. Commercials, mixes, produced segments, and songs are made by people in one market and have to reach another market's air chain the same day. The last step is always the same: a producer or on-air talent drops finished audio into a folder, and the station's broadcast automation picks it up, assigns it a cart number, and queues it for playback. Wide Orbit, the legacy broadcast automation at the end of that chain, could collect those files only through a mapped network drive. The file layer between those two steps is effectively part of the air chain. When it fails, what fails is getting content on the air.

Two Years of OneDrive Failures With Nothing in the Logs

For about two years, that layer was Microsoft OneDrive. Engineering shared a folder per market, and the whole arrangement ran under a single service account.

It failed constantly, and it failed in ways nobody could explain. Sync broke on roughly a third of attempts, and each failure meant a user reboot and a service call to engineering, who then spent their time troubleshooting someone's desktop client instead of running stations. One episode wiped the permissions on 90% of the market folders. Travis Martin, Urban One's Chief Engineer, describes what that looked like:

“All of these folders for each market kind of just disappeared for a few minutes and then came back. The permissions were all weird, and we went through the logs. There's nothing.”

Then it got worse. One market's entire folder was deleted outright, and the root cause was never determined, because every action in the system traced back to the same shared service account. There was no way to say who did it, or whether anyone had.

That was the condition underneath every incident: Urban One was running its on-air content pipeline on a platform it could neither control nor audit.

“Microsoft is so unpredictable that we need more control over what we can do.”

The Broadcast Automation Only Connects Through a Mapped Drive

The obvious question is why a company living with those failures didn't just move. The answer was the oldest piece of the chain.

Wide Orbit, the broadcast automation that collects files after production staff drop them, is legacy software that connects to storage only through a mapped network drive. Whatever replaced OneDrive had to present itself as a drive letter on the machines Wide Orbit watches. That requirement rules out most cloud sharing tools, whose sync clients were exactly the thing that kept breaking.

The second constraint was the workforce. The population touching these folders is 150 to 200 production staff and on-air talent across the markets, up to 25 people in the larger ones, and it turns over continuously. Managing that many accounts by hand, and tying each of them to the company's Okta identity and MFA, had been a standing burden of its own.

So the replacement had a specification before it had a name: present as a mapped drive to a legacy application, give every person an individual identity from the corporate directory instead of a shared service account, keep each market's content segmented, and absorb constant turnover without per-user setup. Urban One selected Files.com to be that layer.

A Folder Per Market, Presented as the Drive Wide Orbit Expects

The structure on Files.com is simple. Each market has its own folder, with access granted through group-based permissions rather than per-user grants. Internal users sign in through Urban One's Okta SSO integration over SAML, so every action belongs to a named individual, and access follows the identity the company already manages.

On the machines feeding broadcast automation, Files.com is mounted as a network drive. Wide Orbit picks files up from a mapped drive exactly as it has for years; the software was never modified or reconfigured. Only what stands behind the drive letter changed.

The rollout started in three smaller markets and then extended across the rest of the footprint, market by market, on the same pattern.

Every File Now Carries a Name, a Time, and a Machine

With Files.com in production as the file-sharing layer, Urban One changed the operating model:

• Shared credentials are gone. Access runs on individual Okta identities, and a population of 150 to 200 people that turns over continuously is managed through group membership rather than hand-built accounts.
• The sync failures that hit roughly a third of attempts, and the reboots and service calls behind them, left with OneDrive. Engineering stopped being the help desk for the file layer.
• Wide Orbit ingests from the same mapped drive it always has. The legacy automation was never touched.

There is a compounding result behind the immediate ones: the pattern repeats. Standing up the next market is a folder, a group, and the same mounted drive, which is how the deployment spread across the company on one design instead of fourteen.

“Joe Schmo put this file in at this time from this computer.”

The Oldest Software in the Chain Never Had to Change

Today, when a commercial isn't where it belongs, an engineer at Urban One reads a log entry that names a person, a time, and a machine. Two years ago the same event meant a reboot, a service call, and a search through Microsoft's logs that turned up nothing.

The constraint that appeared to lock Urban One into aging file infrastructure turned out to constrain only the interface. Wide Orbit still sees the mapped network drive it requires; behind it now runs Files.com, with individual identity, per-market permissions, and a full record of everything that touches the air chain. A legacy application that only accepts a drive letter did not force the company to keep running file infrastructure from the same era. It only dictated how the modern platform had to present itself.