Support and helpdesk

Two different jobs, coordinated on purpose.

A help desk answers the person who filed a ticket. Recurring tenant administration answers a question nobody thought to file one for. Here's exactly where that boundary sits, and how the two stay coordinated whatever desk your team already uses.

Book a scoping call

Two jobs, defined plainly

Start with what each job is actually for.

Ticket
A ticket has a start and a stop
Can't print, mailbox's full, laptop won't join the network—a support ticket is a bounded request with a visible end: it gets fixed, or it doesn't, and either way someone closes it.
Ownership
Ownership has no ticket to file
Nobody opens a ticket because a departed employee is still listed as a Team owner. Recurring administration exists because that kind of gap is real, and nobody would otherwise notice it.
Overlap
The same symptom can trigger both
Three tickets in a month about the same folder access problem usually point to a group-membership design question, not three unrelated mistakes by three different people.
Handoff
The failure mode is neither side knowing where it ends
A problem gets fixed twice by two different people, or it sits in the gap between "that's a ticket" and "that's ownership" until someone gets frustrated enough to escalate it.

What this is—and is not

A boundary, not a rivalry.

Recurring administration is not a help desk, and doesn't try to be one.

A help desk exists to answer the person in front of it, quickly: a queue, a ticket number, a technician who can see the problem and close it. That's a different operating model from recurring tenant administration, which spends most of its time on things nobody would think to file a ticket for—a stale licence, an ownerless Team, a Conditional Access exception nobody remembers approving.

M365 Desk is a related service under common ownership with M365 Care.

M365 Care doesn't run a ticket queue itself, whether the desk behind it is an internal colleague, a break/fix shop, or a dedicated service like M365 Desk ↗. What recurring administration does instead is make the boundary explicit: a request that's actually a ticket goes to whichever desk handles those, and a pattern that's actually an ownership gap gets caught in the monthly review instead of being closed, and reopened, indefinitely.

Three moments the handoff gets tested

Different triggers, the same two questions.

A repeating access complaint

The fourth ticket about the same folder in a month is a signal, not a coincidence. It belongs in the next ownership review, not just the next ticket close.

A new hire's first morning

Whoever answers day-one laptop and login questions is doing desk work. Confirming the access and licence baseline actually matches the role is ownership work, triggered by the same event.

An after-hours outage report

Recurring administration doesn't carry an on-call rotation or promise a response time. Whichever desk is the front door for urgent issues stays the front door; any resulting tenant fix becomes part of the next cycle, not a same-hour promise.

Worth agreeing before both are in place

Five things worth agreeing before both are in place.

Which desk is the front door for a user-facing request, written down rather than assumed
How a repeated ticket gets escalated to an ownership review instead of just closed again
Who tells the other side when an account, licence, or access baseline changes
What happens with an urgent after-hours issue—named, not assumed
Where the reasoning behind a decision is recorded, so it isn't rebuilt from memory each time

If there's no desk yet

Recurring administration doesn't absorb ticket volume either.

Some growing teams don't have a dedicated desk at all—requests go to whoever's free that day. Recurring administration doesn't fill that role. If ticket volume is high enough to need a real answer, that's worth choosing deliberately, rather than letting it become unplanned scope inside a monthly plan built for ownership work, not queue management.

Connect this to the rest of care

Support and ownership meet at the same tenant.

Compare service shapes What we manage each month Decision rights and escalation Book a scoping call

Start with what each job is actually for.

A ticket has a start and a stop

Ownership has no ticket to file

The same symptom can trigger both

The failure mode is neither side knowing where it ends