Microsoft 365 governance

Microsoft 365 doesn't get messy on its own. It gets messy without an owner.

Too many admins, Teams nobody remembers creating, guests from old projects, sites without owners and files shared far too widely. Here is why it happens, the fixes in the order that matters, the routines that keep it tidy, and a 10-point check of your tenant.

Microsoft details from Microsoft Learn, checked 31 October 2026.

  • Root causes
  • Fixes in order
  • 10-point tenant check

Reviewed by Blake Bath, General Manager, on 31 October 2026.

An IT manager and an office manager sort sticky notes on a whiteboard into tasks, priorities and completed work.
Name a tenant ownerOne accountable person. Everything else follows.

What it looks like

Five signs a tenant needs governance.

Each one makes everyday work slower and riskier.

Can't find anything

Files in dozens of Teams and sites, with no obvious home.

  • Structure
  • Owners
  • Naming

Microsoft 365 tenant check

How tidy is your tenant?

Tick what is true today. The gaps come back in the order we would fix them.

Tick what is true for your tenant today.

Where you stand

0of 10 controls in place

10 gaps to close.

  • Few Global Admins, plus two break-glass accountsEach extra Global Admin is another way to lose the whole tenant.
  • Conditional Access in placeWithout it, security depends on each user's settings.
  • Leavers disabled on their last dayOld accounts are a common way in and a quiet licence cost.
  • Guests reviewed and expiredGuests from finished projects keep their access.
  • Every Team and site has two ownersOwnerless spaces can't be tidied or approved.
  • Teams creation is controlledUnrestricted creation is how sprawl starts.
  • External sharing set deliberatelyBroad links travel further than anyone intends.
  • Inactive Teams and groups expire or archiveOld spaces clutter search and hold forgotten data.
  • Audit logging on, with alertsYou can't investigate what wasn't recorded.
  • Someone owns the tenantWithout an owner, nothing stays tidy.
Fix the gaps

Why it happens

Why tenants get messy.

  • Self-service everythingAnyone can create a Team, site or group from day one.
  • No structureSharePoint shaped by whoever clicked New first.
  • No offboarding disciplineAccounts, licences and access outlive the person.
  • Admin creepGlobal Admin given to fix one problem, never taken back.
  • No Conditional AccessSecurity depends on individual settings.
  • Sharing never reviewedSettings left as they were when the tenant was created.

In this order

The fixes, in the order that matters.

StepWhat to doWhy first
1. AdminsCut Global Admins, add break-glass, use specific rolesProtects everything else
2. Sign-inConditional Access baselineStops account takeover
3. PeopleDisable leavers, remove stale guests, reclaim licencesCloses forgotten doors, saves money
4. Teams and sitesArchive inactive, appoint two owners for the restMakes the rest manageable
5. SharingSpecific people by default, link expiryLimits what leaks
6. Audit and alertsAudit on, alerts on risky changesSo you know when it drifts
7. StructureHub sites, naming, templatesA longer programme

Ongoing

The routines that keep it tidy.

  • Quarterly admin reviewWho has which role, and why.
  • Licence reconciliationLeavers removed, plans matched to roles.
  • Group expirationOwners renew Teams and groups or they expire. Needs Entra ID P1.
  • Guest and access reviewsAutomated access reviews need Entra ID P2 or ID Governance; a manual review works too.
  • Sensitivity labelsOn confidential content, so sharing rules follow the file.
  • Alerts acted onForwarding rules, admin changes and risky sign-ins.

What to avoid

Common clean-up mistakes.

  • Fixing everything at onceAdmins and sign-in first; structure is a longer programme.
  • Deleting without warningArchive, tell people, then delete after a cooling-off period.
  • Locking down overnightPhase controls in, with communication, so work doesn't stop.
  • No named ownerWithout one, the tenant drifts back.

Our view

Governance is a few habits, not a big project.

Most of the mess we see comes from a few defaults never being decided and nobody owning the tenant. The fix starts with security, because that's where the risk is, then works through people, spaces and sharing.

After the clean-up, a handful of routines keep it tidy: quarterly admin and guest reviews, group expiry, licence reconciliation and alerts someone actually reads.

How we work

A tenant clean-up in five steps.

  1. Step 1Review

    Admins, sign-in, accounts, Teams, sharing.

  2. Step 2Secure

    Admins and Conditional Access first.

  3. Step 3Clean up

    Leavers, guests, licences, inactive spaces.

  4. Step 4Set the rules

    Creation, sharing, expiry, naming.

  5. Step 5Keep it tidy

    Quarterly reviews and alerts.

Questions

What people ask about Microsoft 365 governance.

Why does our Microsoft 365 feel messy?

Usually because anyone could create Teams and sites, nobody owned the tenant, leavers and guests were never cleaned up, and admin rights spread over time. It still works, but every task gets slower and riskier.

Where should we start?

Admins and sign-in first: cut Global Admins down and put Conditional Access in place. Then leavers and guests, then Teams and SharePoint, then sharing and lifecycle. Information architecture is a longer piece of work.

Should we stop staff creating Teams?

Not necessarily. Many businesses use a simple request process, a naming convention and two owners per Team. The aim is that every space has an owner and a purpose.

Can old Teams and groups expire automatically?

Yes. A Microsoft 365 group expiration policy renews groups that are in use and asks owners to renew the rest. Groups that aren't renewed are deleted and can be restored within 30 days. It needs Entra ID P1, which is in Business Premium.

Should we just delete old Teams?

Archive first and tell people, then delete after a cooling-off period. Check retention needs before deleting anything that holds business records.

How long are audit logs kept?

Audit (Standard) keeps 180 days. Longer retention needs Audit (Premium) or sending logs elsewhere.

Next step

Want your tenant cleaned up and kept that way?

We review admins, sign-in, accounts, Teams, SharePoint and sharing, fix them in the right order, and set up the routines that stop the mess coming back.

Chip, the Real Bytes support assistant

Cookie Preferences

We use cookies to improve your experience, analyse site traffic, and personalise content. By clicking "Accept All", you consent to our use of cookies. Privacy Policy

Privacy Act 1988 compliant. Your data is never sold.