“Is this an Outlook problem—or a project?”

The app name does not define the engagement. The kind of change does.

An employee blocked in Outlook, Teams, OneDrive, or SharePoint may need everyday help. A tenant-wide design, migration, policy, investigation, or major rollout needs separate ownership.

Describe an app issue

Outlook & Exchange use

Mailbox, device, browser comparison, exact wording, sender or recipient scope, and time observed.

Good desk starting points

Profile and sync trouble
Shared mailbox access
Calendar delegation
Sending or receiving symptoms

Teams meetings & collaboration

Organizer, participant type, meeting or channel, client, device, and whether others see the same result.

Good desk starting points

Joining and scheduling
Client and notification friction
Guest-access questions
Channel or chat use

SharePoint & OneDrive

Site or library, safe link or location, expected owner, sync state, and who can or cannot open the content.

Good desk starting points

Sync and sign-in symptoms
Known-site permissions
Sharing-link trouble
Finding the working copy

Three-part boundary test

Ask what is changing, how widely, and who must approve it.

One person or many?A single-user symptom can reveal a wider issue, but breadth should be checked before the path is assumed.
Restore or redesign?Helping someone use an agreed setup differs from changing the setup for everyone.
Routine approval or risk decision?Privileged access, security, retention, and investigation need explicit ownership.

Bring the symptom

Let the support boundary stay visible.

Describe the app issue →Review common situations →

The app name does not define the engagement. The kind of change does.

Let the support boundary stay visible.

One place for everyday Microsoft 365 questions to begin.

Related services