Your practice
You decide who’s allowed to request a new Teams site or shared mailbox, what naming and ownership convention to enforce, and how often a permission cleanup should actually happen.
Collaboration platform administration Administration de la collaboration
"Mailbox and Teams admin" was always going to need its own page.
The services overview mentions mailbox and Teams admin in one line, next to accounts and licences. In practice it’s shared mailboxes, distribution lists, Teams and SharePoint site provisioning, mail-flow rules, and the permission cleanup nobody schedules until access sprawl becomes its own problem. This page names it as its own line, with the scope questions that make it quotable instead of a vague inclusion.
Delivery team
We provision what you’ve approved — a Teams site, a SharePoint library, a shared mailbox, a distribution list, a mail-flow rule — set the ownership you named, and run the permission cleanup on the schedule you set.
Teams, SharePoint, and mailbox administration
For a client whose Microsoft 365 tenant already has Teams and SharePoint in daily use, but whose site sprawl, stale permissions, and shared-mailbox ownership nobody has reviewed since they were first created.
What we need first
Who’s authorized to request a new site, mailbox, or distribution list, the naming and ownership convention you want enforced, and how permission access should default when someone requests membership in an existing site or mailbox.
What’s included
- Provisioning new Teams sites, SharePoint libraries, shared mailboxes, and distribution lists on request
- Mail-flow rule changes you’ve approved (routing, forwarding, transport rules)
- A scheduled permission review naming stale access and requesting a keep/remove decision
Handled separately
- Deciding information architecture, site structure, or retention policy for your client
- Granting site or mailbox ownership without the named approver’s sign-off
- Data migration into or out of Teams/SharePoint from another platform — that’s project work
What you get: A collaboration environment where new sites and mailboxes follow one naming and ownership convention, and stale permissions get reviewed on a schedule instead of accumulating silently.
What we hand back: A provisioning or permission-review note naming what was created or changed, and what’s still open.
What collaboration administration has to define before it’s priced
Site and mailbox ownership, on paper
Every Teams site and shared mailbox needs a named human owner responsible for its membership — "the whole department" is not an owner. Set this rule before the first site request, not after the tenth ungoverned one.
What triggers a permission review
A calendar date, a headcount change, or a fixed cadence can all trigger a cleanup — pick one, because "whenever someone notices" means it never actually happens.
Mail-flow rules that affect deliverability
A forwarding rule or transport rule can silently break delivery for people outside its intended scope. Rules that touch more than one mailbox or group need a named approver before they go live, not after a complaint.
What counts as a request versus a migration
Adding a new shared mailbox is a request. Moving years of content from a file server or a different platform into SharePoint is a project with its own inventory and timeline — naming the line early avoids a support ticket quietly becoming a migration.
What this line doesn’t include
- Information architecture or governance strategy for your client’s tenant
- Data migration from another platform or file server — quoted separately as project work
- A guaranteed mail-delivery time or a Microsoft partnership claim
Straight answers on Teams, SharePoint, and mail-flow
Is this the same as the Microsoft 365 administration on the Services page?+
It’s the specific, detailed version of one line inside that broader scene. Account and licence administration lives on the Services page; this page is specifically Teams, SharePoint, mailboxes, and mail-flow.
Can you clean up years of ungoverned Teams sites in one pass?+
We can start the scheduled review and work through what you prioritize, but a large backlog of ungoverned sites is realistically a project-scoped cleanup, not a single routine request — we’ll say so upfront rather than quote it like a quick task.