Choose by the responsibility, not the provider name.

For: access, accounts, mail, Teams, devices, files, and practical user issues.

Not for: automatically turning one ticket into a security review or management agreement.

Bring: who is affected, the tool, when work stopped, and what has been tried.

For: tenant stewardship, lifecycle tasks, recurring hygiene, managed IT, and coordination.

Not for: a one-time issue with no ongoing responsibility.

Bring: environment in scope, current owners, repeated friction, and expected cadence.

For: posture review, hardening, a decision, advisory, or a scoped project.

Not for: vague fear-based “security” without a question or environment in scope.

Bring: decision, scope, constraints, stakeholders, and useful deliverable.

For: agencies, consultants, VARs, and IT practices seeking delivery capacity.

Not for: direct end-client help desk requests.

Bring: partner role, service boundary, client-facing model, and handoff expectations.