Reset Teams status settings in Outlook — step-by-step

Short answer: sign out of Teams, sign out of Outlook, restart both, then sign back in — that fixes most presence-sync problems within a minute. If that does not work, clear the Teams and Outlook local caches, create a safe new Outlook profile (so you do not delete mail data unintentionally), and only then repair or reinstall clients. This guide gives device-specific fast paths, a deeper cache/profile reset sequence, verification tests you can run immediately, and what to collect before you escalate to IT or Microsoft Support.

What you need before you start (prerequisites)

• Signed-in credentials for the affected Microsoft 365 account (user principal name and password) and access to your MFA method.

• A colleague or second account you can use to confirm presence changes from their side.

• Know which clients you use: Outlook for Windows (desktop), Outlook for Mac (desktop), Outlook Web (OWA), Teams desktop (Windows or macOS), Teams mobile, Outlook mobile. Note the app versions if you can: Outlook -> File -> Office Account -> About Outlook; Teams -> Profile -> About -> Version.

• Permissions: you do not need tenant admin rights for the local steps in this guide. If tenant policy or service-side checks are required, have a Microsoft 365 admin, Exchange admin or Teams admin available to run tenant diagnostics.

• Where presence comes from: presence shown in Outlook is sourced from Teams/Exchange/Graph presence services; local client tokens and caches frequently cause mismatches. Tenant-level presence policies, conditional access or identity changes can block presence updates.

• Quick checks before you begin:
• Confirm you can sign out and sign back in (know your MFA method).
• Save open work and close nonessential apps that might lock files (VPN, backup tools).
• If you have limited bandwidth or very large OST files, avoid deleting OST/PST files unless you are prepared for a full re-sync.

Fast path — sign out/in and quick checks (5 minutes)

Try this lowest-risk sequence first on the device where you notice the problem. If you use multiple devices, start with your primary PC.

1. Sign out of Teams (desktop).

Open Teams -> click your profile picture (top-right) -> Sign out

2. Quit Teams fully (don't just close the window).

3. Sign out of Outlook desktop.

File -> Office Account -> Sign out

Outlook menu -> Sign Out

4. Close Outlook fully and wait 10–15 seconds.

5. Re-open Teams first and sign in. Wait until your presence reflects calendar state (Available/Busy/Do not disturb) in the Teams client.

6. Open Outlook and sign in if it prompts.

7. Quick verification:

• In Outlook desktop, hover over your profile or a colleague’s contact card; the small colored dot and status text should match Teams.
• In Outlook Web (OWA), check your profile indicator top-right; it should match Teams.
• On mobile, sign out and back into the Teams mobile app, then check Outlook mobile for the same indicator.

Expected result: presence updates in Teams and Outlook within 30–60 seconds. If it does not, continue to the deep reset steps.

Deep reset — caches, safe profile reset and reinstall (15–30 minutes)

If the fast path fails, clear local caches, recreate an Outlook profile safely, then repair or reinstall clients. Work in this order and stop when the problem is resolved.

1. Clear Teams cache (Windows).

Close Teams (right-click tray icon -> Quit)
%appdata%\Microsoft\Teams\application cache\cache
%appdata%\Microsoft\Teams\blob_storage
%appdata%\Microsoft\Teams\Cache
%appdata%\Microsoft\Teams\databases
%appdata%\Microsoft\Teams\IndexedDB
%appdata%\Microsoft\Teams\Local Storage
%appdata%\Microsoft\Teams\tmp

Delete the files and folders listed, then restart Teams and sign in.

2. Clear Teams cache (macOS).

Quit Teams (Cmd-Q)
~/Library/Application Support/Microsoft/Teams
~/Library/Caches/com.microsoft.teams
~/Library/Logs/Microsoft Teams

Remove those folders, restart Teams and sign in.

3. Clear Outlook local cache (Windows) — safe first step.

Close Outlook
%localappdata%\Microsoft\Outlook\RoamCache

Delete files in RoamCache, then start Outlook.

4. Recreate Outlook profile safely (Windows).

Control Panel -> Mail (Microsoft Outlook) -> Show Profiles -> Add

Create a new profile and add your account. Set Outlook to prompt for a profile if you want to test without removing the original.

5. Repair Office or reinstall clients.

• Windows: Settings -> Apps -> Microsoft Office -> Modify -> Online Repair (preferred) or Quick Repair.
• macOS: Quit Outlook/Teams, remove the app bundles and cached folders listed earlier, then reinstall from the Microsoft site or the Mac App Store. Check your org’s managed deployment policy first.

6. Mobile clients (iOS/Android).

• Android: Sign out of Teams and Outlook, force-stop the apps, Settings -> Apps -> Teams -> Storage -> Clear cache, then sign back in.
• iOS: Sign out, uninstall, and reinstall the app to clear the client cache. iOS does not expose a manual cache clear.

7. Collect logs if the issue persists:

• Teams desktop logs: Teams -> Profile -> Help -> Collect support files, or press Ctrl+Alt+Shift+1 (Windows) to produce a zip.
• Outlook logs: File -> Options -> Advanced -> Enable troubleshooting logging, reproduce the issue, then collect log files as described in Outlook Help.

Expected result: after caches are cleared and a new Outlook profile is in use, presence updates in Teams and Outlook within one minute of a deliberate status change. If presence still fails across clients, the cause is likely tenant- or service-side.

How to verify the reset worked (tests and expected results)

You need to confirm both what you see and what others see. Run these checks immediately after a reset.

1. Self-check (1 minute):

1. In Teams, manually set your status to a distinct state (for example, "Do not disturb").
2. Wait 30–60 seconds and open Outlook (desktop or web). Check your profile indicator; the colored dot and any status text should match the Teams setting.

Expected result: Outlook shows the same status you set in Teams within one minute.

2. Colleague check (1 minute):

1. Ask a colleague to open your contact card in Teams or Outlook.
2. Change your status (Available -> Busy -> Do not disturb), pausing 20–30 seconds between changes.
3. The colleague reports whether the indicator and presence text update.

Success: the colleague sees each status change within 30–60 seconds. If the colleague sees changes in Teams but not in Outlook, the issue is Outlook-side.

3. Interpreting outcomes:

• All clients match and colleagues see you: problem solved.
• Teams matches but Outlook does not: try Outlook profile reset or repair steps above.
• No client updates anywhere for you and others: likely tenant policy or service issue — escalate.

When and how to escalate to IT or Microsoft Support (what to collect)

Escalate when local troubleshooting fails or multiple users are affected. Provide clear evidence and logs so IT or Microsoft Support can triage quickly.

1. When to escalate:

• Presence mismatch persists after cache clears and a new Outlook profile.
• Multiple users in the tenant report the same problem.
• Presence does not update across all clients (desktop, web, mobile).

2. What to collect before opening a ticket:

• Tenant ID and your UPN.
• Exact local steps and timestamps (UTC) you tried.
• Screenshots or a short video showing mismatch between Teams and Outlook.
• Logs: Teams support zip, Outlook logging files (noting when logging was enabled), client versions and OS/build numbers.

3. Tenant-side checks IT should run:

• Verify presence settings in Microsoft 365 admin center and Teams admin center; confirm presence service is enabled and no org policy blocks presence.
• Check Exchange Online mailbox health and service incidents.
• Check conditional access and session policies that could block the Graph Presence API or token refresh.
• Review recent identity/authentication changes that might affect token lifetime or refresh.

4. Suggested ticket summary (short):

User presence not syncing between Teams and Outlook after local cache reset. User: <UPN>. Clients: Teams <version>, Outlook <version>. Steps tried: signed out/in, cleared Teams and Outlook caches, created new Outlook profile, repaired Office. Attached: Teams logs, Outlook logs, screenshots, timestamps. Please check tenant presence service, conditional access and Graph presence API access.

5. Signs of server-side or policy issues:

• Multiple users affected or presence never updates in OWA after client resets.
• Admin sees errors or throttling in Graph or Exchange traces for the user.