Where should business files be stored in Microsoft 365 Business Premium?

The right location depends on who owns the file, who needs to use it and how long the organisation needs to retain it. Use OneDrive for an individual’s working documents, SharePoint for information owned and managed by a team or department, and Teams for files that form part of ongoing conversations and channel collaboration. The important principle is to place shared business records in an organisational location rather than leaving them in one employee’s personal work area.

Use OneDrive for individual working content. OneDrive is appropriate for documents that an employee is drafting, reviewing privately or has not yet shared with a wider group. It can also be used to share a specific document with colleagues when broad team ownership is not required. However, a file should not remain in OneDrive merely because it began there. Once it becomes a departmental record, a customer deliverable, a standard operating procedure or a document needed by several people, it is usually better placed in the relevant SharePoint library.

OneDrive content is associated with an individual user account. That makes it unsuitable as the main repository for documents that the organisation must continue to access if the creator changes role or leaves the business. Before an account is closed, the organisation should identify any business records held there and transfer them to the appropriate SharePoint site or another approved location. A clear ownership model reduces the risk of important information becoming difficult to locate or dependent on one person.

Use SharePoint for shared business information. SharePoint is generally the better choice for departmental documents, project records, policies, procedures, templates, customer information and other content with collective ownership. A SharePoint site can provide a stable home for the files, with permissions, version history, document libraries, metadata and retention arrangements managed at an organisational level.

SharePoint is particularly suitable where several people need to work from the same set of documents, where access needs to be granted by team or role, or where the content will remain important after the original contributors have moved on. Separate sites or libraries can be used for different departments, projects or information types, but creating too many locations can make information harder to find. The structure should reflect how the organisation operates rather than mirror every individual or short-lived activity.

Use Teams as a collaboration interface, not as an alternative storage model. Teams is useful for discussing work, coordinating tasks and accessing files alongside conversations. The underlying file location and permission model still need to be understood when a team or channel is created. This matters when setting retention rules, reviewing access, moving content, investigating an incident or deciding who owns a document after a project ends.

A practical arrangement is to create a SharePoint site or library for each enduring business function, then use Teams where that group needs a conversation and collaboration space. A short-term project may have its own working area, but completed records should be reviewed and moved into the organisation’s agreed long-term location rather than allowing inactive project spaces to accumulate indefinitely.

Apply a simple decision test to each file:

• If only one person is developing the document and it is not yet an organisational record, keep it in OneDrive.
• If a team, department or the wider organisation owns the information, store it in SharePoint.
• If the document is being created and discussed through a team or channel, use the connected collaboration space while checking the underlying SharePoint location.
• If the document is a formal record, policy, procedure or reusable business asset, place it in a controlled SharePoint library with suitable ownership and permissions.
• If the document is no longer needed, follow the organisation’s retention and disposal process rather than leaving it indefinitely in an active working area.

Design permissions around groups and responsibilities. Access should be granted according to job function, project membership or business need, rather than by repeatedly sharing individual files with named users. Group-based access is easier to review when staff change roles and makes it clearer who is responsible for each location. Avoid giving broad edit access where read-only access is sufficient, and review external sharing separately from internal access.

Sharing a link is not the same as transferring ownership. Before distributing a document, check whether recipients can edit, download or reshare it, and confirm that the file contains information they are authorised to see. Sensitive material may require a restricted library, tighter membership or a different handling process. Permissions inherited from a site, library, folder or team should also be understood before a file is moved.

Plan the structure before moving large volumes of data. Start by listing the main departments, projects and information types, then decide which locations are authoritative. Use consistent site, library, folder and file naming conventions. Avoid deep folder structures and duplicate copies where possible. Metadata and views can help users find content without creating a separate folder for every variation of a document.

Before migration, identify duplicate, obsolete and personal material. Check who owns each category, what permissions it requires and whether version history or other document properties need to be retained. Moving files can alter inherited permissions, links and the way users find content, so changes should be tested with representative users before the new structure becomes the standard.

Remember that storage location is only one part of information management. Version history can consume storage, particularly when large files are edited frequently, so libraries should have sensible versioning settings for their purpose. Retention, deletion, legal or regulatory requirements and recovery arrangements should be considered separately. Synchronising a folder to a computer improves convenience but does not, by itself, create an independent backup or remove the need to control access.

For most organisations, the resulting pattern is straightforward: OneDrive for personal drafting, SharePoint for collectively owned business information, and Teams for collaboration around that information. Documenting this rule, assigning owners to each SharePoint site and reviewing permissions and inactive content regularly provides a more dependable arrangement than allowing users to choose storage locations ad hoc.