In short
Review Microsoft 365 around actual work: where shared records live, how people collaborate, who controls access and what happens when staff or projects change. Agree the working structure before moving files or adding automation, then test it with users and the existing administrator.
In this guide
Start with the work that creates confusion
The problem is rarely that a business has too few places to put a document. It is that the approved version is unclear, a key file belongs to somebody who has left, or a team uses email attachments because the shared location is difficult to navigate.
Choose a recurring activity such as preparing a management pack, onboarding an employee or working with an external project team. Ask staff to find the current record, explain who can change it and show how a decision is recorded. Those observations give the review a practical purpose.
Understand what Teams, SharePoint and OneDrive are doing
Microsoft documents the relationship between Teams and SharePoint: standard channel files use the team's parent site, while private and shared channels have their own sites. Changing membership or adding channels therefore affects more than the chat interface.
Microsoft's file-collaboration guidance also distinguishes shared libraries from individual OneDrive libraries. Review where continuing team records belong and how personal working files become accepted shared records. Do not move an active library simply because another folder structure looks tidier.
Review ownership and access alongside the content
| Review area | What to inspect | Useful decision |
|---|---|---|
| Working locations | Active teams, sites, libraries and duplicate stores | Where each recurring process keeps its accepted record |
| Ownership | Business owner, administrator and backup contact | Who approves access and structural changes |
| Sharing | Guests, groups, shared links and sensitive material | Which collaboration boundaries are appropriate |
| Lifecycle | Completed projects, leavers and retention needs | What remains active, what is archived and who accepts it |
Check the actual subscriptions and configuration before promising labels, retention, access reviews or other advanced controls. Product names do not establish licensing entitlement. Any administrator change should have a defined owner and a way to test the effect on real users.
Make the agreed way of working easy to follow
Give teams a small set of practical conventions: where a shared record starts, how its status is indicated, how an external party gets access and where an approval is recorded. Test these with a staff member who was not involved in the design.
Before migrating, sample permissions, file versions, links, sync behaviour and dependent workflows. Move a bounded set first and retain a recovery option. A library can appear complete while a spreadsheet link or an approval process still points to the old location.
Copilot or another AI assistant should come after the information and access review. Do not assume that adding AI will distinguish an obsolete procedure from the approved one. Decide which material is suitable for retrieval and who keeps it current.
What Advery can help deliver
Advery brings workplace-systems experience to the business review, site and library structure, documented ownership, provider coordination and a tested transition. Our management visibility work also shows how governed sources and review routines make information more dependable for the people using it.
The first output should be a prioritised review of the current setup and the working practices it needs to support. Your administrators retain control of the environment, with changes made only within an agreed scope.
Sources and guidance
- Microsoft: Plan and deploy a file collaboration environment
- Microsoft: Teams and SharePoint integration
- Advery: Management visibility and operating controls