SharePoint vs. OneDrive vs. Teams: Where Should Your Utah Business Store Files?

The Problem We See in Every Utah Office

When we onboard a new client at Brivy IT, one of the first things we audit is file storage. The pattern is remarkably consistent: thousands of files scattered across individual OneDrive accounts, no shared document libraries, critical company files accessible to only one person, and Teams channels full of uploaded attachments with no logical organization. This is not a technology failure. Microsoft 365 provides excellent file storage and collaboration tools. It is a configuration and training failure. Most businesses activate Microsoft 365, hand out licenses, and never set up the underlying structure. Employees figure it out on their own — and “on their own” means everyone does it differently. The result is predictable: people cannot find files, version control is nonexistent, departing employees take institutional knowledge with them (or their files become inaccessible), and collaboration means emailing attachments back and forth despite paying for tools that eliminate that workflow. Let us fix that. Here is how each storage tool works and when to use it.

OneDrive: Your Personal Work Drive

What it is: OneDrive for Business is cloud storage tied to an individual user’s Microsoft 365 account. Each user gets 1 TB of storage by default. Think of it as your personal “My Documents” folder — but in the cloud, backed up, synced across devices, and protected by your organization’s security policies. When to use it: – Drafts and works in progress that are not ready to share – Personal reference documents – Individual project files before they move to a shared location – Files you need to access from multiple devices (laptop, phone, tablet) When NOT to use it: – Company-wide templates, policies, or procedures – Shared project files that multiple people need to access – Department resources – Anything that another employee would need if you left the company The biggest OneDrive mistake: Using it as your company file server. We regularly encounter businesses where the office manager has 400 GB of company documents on their personal OneDrive, shared via links with various coworkers. When that person leaves, IT scrambles to recover access. When files are shared this way, there is no consistent permissions model, no audit trail, and no organizational structure.

SharePoint: Your Company’s Structured File System

What it is: SharePoint Online provides team sites and document libraries that belong to the organization — not to any individual. Files stored in SharePoint persist regardless of employee turnover. SharePoint supports metadata, custom views, version history, granular permissions, and workflow automation. When to use it: – Department document libraries (HR policies, accounting records, marketing assets) – Company-wide resources (employee handbook, brand guidelines, templates) – Project documentation that spans teams – Compliance-related documents that require audit trails and retention policies – Any file that answers the question: “Where does the company keep [X]?” How to structure it: We recommend creating SharePoint team sites by department or function: – Company Hub — Organization-wide documents, policies, templates – HR — Employee records, onboarding documents, benefits information – Finance — Budgets, reports, invoices (with restricted permissions) – Marketing — Brand assets, campaign files, content calendars – Operations — SOPs, vendor contracts, facility documentation – Projects — Active project sites (can be created and archived as projects begin and end) Each site gets its own permissions. Not everyone needs access to Finance. Not everyone needs access to HR. SharePoint makes this granular control straightforward — if it is set up correctly from the start.

Microsoft Teams: The Collaboration Layer (That Happens to Store Files)

What it is: Teams is a collaboration platform — chat, video calls, meetings, and yes, file sharing. But here is the detail that confuses most users: every Teams channel has a SharePoint folder behind it. When you upload a file to a Teams channel, it goes to a SharePoint document library associated with that team. Teams is a window into SharePoint, not a separate storage system. When to use Teams for files: – Files actively being discussed or collaborated on within a specific team or project – Documents that need real-time co-authoring during a conversation – Quick file sharing within a working group context When NOT to use Teams for files: – Long-term document storage (use the underlying SharePoint site directly) – Files that need to be discoverable by people outside the team – Organized document libraries with metadata and custom views (manage these in SharePoint) The biggest Teams file mistake: Uploading files to chat instead of channels. Files shared in a Teams chat go to the sender’s OneDrive in a “Microsoft Teams Chat Files” folder. They are not in SharePoint. They are not organized. They are not easily searchable. If you need to share a file in Teams, post it in the relevant channel — not in a private chat.

Permissions: Getting This Right From the Start

One of the most common configuration failures is permissions. Here is the framework we implement for our Microsoft 365 clients: Use Microsoft 365 Groups and security groups to manage access. Do not assign permissions to individual users. When you add someone to the “Marketing” group, they automatically get access to the Marketing SharePoint site, the Marketing Teams team, and the shared Marketing mailbox. When they leave the department, remove them from the group and all access revokes cleanly. Apply the principle of least privilege. Not everyone needs edit access to everything. SharePoint supports viewer, editor, and owner permission levels. Give most users edit access to their department’s files and view access (or no access) to other departments. Restrict external sharing. By default, SharePoint allows users to share files externally via links. For most Utah businesses, this should be restricted to specific sites or disabled entirely, with exceptions managed by IT. Unrestricted external sharing is a data leak waiting to happen.

Version History: The Feature Nobody Uses Until They Need It

SharePoint and OneDrive both maintain version history for every file. By default, SharePoint keeps up to 500 versions. This means if someone accidentally overwrites a document, deletes critical content, or a file becomes corrupted, you can restore any previous version with two clicks. We configure version history settings based on the document library’s purpose. For active collaboration libraries, we keep major versions only and set a reasonable limit. For compliance-sensitive libraries, we enable both major and minor versions with approval workflows. This feature alone justifies the move from a traditional file server to SharePoint. No more “Final_v2_REVISED_actual_final.docx” naming conventions. One file, full history, always recoverable.

Common Migration Mistakes to Avoid

When Utah businesses move from a local file server or unstructured cloud storage to a properly configured Microsoft 365 environment, these are the mistakes we help them avoid: Lifting and shifting without restructuring. Moving your chaotic folder structure to SharePoint just gives you chaos in the cloud. Take the opportunity to reorganize, remove duplicates, and archive outdated content. Not training employees. The tools work well, but only if people understand the “where does this file go?” decision tree. We run brief, practical training sessions — not hour-long webinars — focused on the three to four decisions users make daily. Ignoring sync settings. OneDrive sync lets users access SharePoint files directly from File Explorer. This is powerful but needs to be configured correctly. Selective sync, Files On-Demand, and known folder redirection should all be set up by IT — not left to individual users. Forgetting about retention and compliance. If your industry has document retention requirements (healthcare, legal, financial services), SharePoint retention policies should be configured from day one. Retroactive compliance is always harder and more expensive.

How Brivy IT Sets This Up for Clients

When we configure Microsoft 365 file storage for a Utah business, the process looks like this: First, we audit the current state — where files live, who has access, what is duplicated, and what is missing. Then we design a SharePoint site architecture based on the company’s departments, workflows, and compliance requirements. We build the sites, configure permissions via groups, set up sync clients on all workstations, and migrate files from existing locations. Finally, we train the team — brief, role-specific sessions that focus on daily workflows, not feature overviews. The result is a file environment where every employee knows exactly where to save and find documents, permissions are consistent and manageable, and the company’s institutional knowledge is protected regardless of employee turnover.