Skip to content

A mailbox outlives the person who requested it.

Shared mailboxes, delegate access, and distribution lists tend to be created once for a specific reason and then never revisited. Recurring hygiene keeps them connected to an actual owner and an actual purpose.

Book a scoping call

Four ways a mailbox loses its owner.

  • Delegates

    Delegate access outlives the reason it was granted

    A colleague given send-as or full-access rights for a leave or a project keeps that access indefinitely.

  • Shared

    Shared mailboxes have no accountable owner

    A generic inbox like info@ or billing@ is created for convenience and never assigned to anyone by name.

  • Lists

    Distribution lists and groups blur together

    Nobody remembers whether a given list is a distribution list, a Microsoft 365 group, or a mail-enabled security group.

  • Rules

    Autoresponders and forwarding keep running

    An out-of-office or forwarding rule set for a departure or a leave stays active long after it matters.

A name, not just an address.

A shared mailbox needs a person, not just a purpose.

Shared mailboxes are useful precisely because several people can act on them—but that only works when one business owner is accountable for who has delegate access, what the mailbox is for, and when it should be retired. Without that owner, access grows by request and never shrinks.

The same applies to distribution lists and mail-enabled groups. Membership tends to be added readily and removed rarely, which quietly turns an announcement list into a stale record of everyone who ever needed to be on it.

Five recurring questions worth asking.

  • Does every shared mailbox have a named business owner on record?
  • Which delegate or send-as grants no longer match an active reason?
  • Are distribution lists, security groups, and Microsoft 365 groups still the right tool for each list?
  • Which autoresponders or forwarding rules were set for a temporary situation that has ended?
  • Do any shared mailboxes still carry a full licence when they qualify for the standard size-based exemption?

Shared mailbox, distribution list, or group.

NeedUsual fit
A shared inbox several people reply fromShared mailbox with a named owner and a small delegate list
A one-way announcement addressDistribution list, reviewed for stale membership
A team that also needs shared files and chatMicrosoft 365 group or Team, not a standalone mailbox

Mailbox hygiene meets two other recurring reviews.

Departures are the single biggest driver of mailbox hygiene work, and the same events touch access, licences, and shared work at the same time.