Every business we take on has, at some point, been through a "Reply All storm." Someone sends a message to a distribution list. Someone replies to all. Someone else replies to all asking to be taken off. Then five more people reply to all telling everyone to stop replying to all. By lunchtime, 300 emails.
It's funny. Once. Except it's a symptom, and the symptom shows up everywhere.
The symptom is: your Microsoft 365 tenant is messy. Groups nobody remembers creating. Permissions that were set as a favour and never reviewed. Shared mailboxes with more members than the company has staff. Guest access that should have been revoked a year ago.
Messy tenants don't just cause funny stories. They cause avoidable security exposure, avoidable licensing waste, and staff time lost to bad structure that quietly compounds.
Where mess turns into problems
- Broad permissions. Site collections shared with "everyone" that shouldn't be. Files anyone in the tenant can find and access.
- Guest sprawl. Users from long-ended projects who still have live access.
- Group nesting that nobody understands. Where a change to one group cascades in ways nobody expected.
- Shared mailboxes without MFA enforcement paths.
- Sensitivity labels missing. So sensitive files travel around unmarked.
- Distribution lists that behave like security groups (or vice versa).
What a Microsoft 365 tidy-up actually involves
- An audit of every group, permission and access level.
- A short workshop with your leadership to agree the target structure — what should be broadly accessible, what shouldn't.
- Cleanup by phases. Not "everything at once, hope nothing breaks." Small changes, review, iterate.
- Guest access review. Anyone who shouldn't be there gets removed.
- Sensitivity labels rolled out. For the categories that matter.
- Documentation. So the tenant stays clean between reviews.
Why it's worth doing even if nothing's on fire
Because the productivity uplift alone is real. People find files. Collaboration works. Nobody's guessing whether they're allowed to open something. Nobody's re-sharing things because sharing broke.
And when Copilot arrives
If Copilot is on your roadmap, tidying the tenant first isn't optional — it's the difference between Copilot being useful and Copilot being confidently wrong. Because Copilot inherits your permissions and structure, and shows people things they might not realise they could see.
Book a Microsoft 365 tidy-up. We'll scope the phased approach before quoting a single hour.
Book a tidy-up