Why is my Teams status not syncing with Outlook?

Short answer: most mismatches are client-side — a stuck Teams or Outlook client state, cached credentials, mixed accounts, or a blocked network path. Try signing out/in, fully quitting and restarting the apps, and clearing the client cache; those three steps fix the majority of cases. If those don’t help, the problem may be tenant-side (Exchange/Graph/OAuth or presence policy) and will need admin action or Microsoft support.

Symptom — what you see and when it happens

You see different presence text or icons for the same person in Teams and Outlook. For example, Teams may show Available while Outlook shows Away or Out of Office. This section explains when mismatches happen and what we won’t fix here.

This mismatch can be constant or appear after sign-in, after a network change (VPN connect or disconnect), after a client update, or when Outlook shows a shared mailbox or delegated access.

• Common visible mismatches: Teams desktop vs Outlook desktop; Teams desktop vs Teams web; Outlook showing a shared mailbox presence while Teams shows the signed-in user.

• What this note won’t fix: tenant admin changes (presence policies you don’t control), Exchange server configuration that needs admin work, or Microsoft service outages. The article explains how to collect evidence for those escalations.

Before you start (applicability and safe checks)

Use this guide if you are an end user or a frontline helpdesk technician who can sign out, clear caches, reinstall clients, and run basic network checks. The next steps are safe and reversible in most cases.

• Preconditions: you can sign out and sign back in to both Teams and Outlook, or you can ask the user to do so. You don’t need admin rights for the quick checks and most client repairs.

• Safe checks to run first: confirm the signed-in account looks the same in both apps by checking the profile picture or email. Confirm the system clock is set to automatic network time. Check whether the issue reproduces for other users or only on this device.

• Stopping conditions: if the user relies on an Outlook profile you can’t recreate, stop before deleting the profile and escalate to IT. If a tenant-wide outage is suspected, stop local changes and collect evidence for admins.

Quick 3-step checks to try first (fast path that fixes ~70% of cases)

Try these safe, reversible steps in order. After each step, wait 60–120 seconds and check presence in Teams desktop, Teams web, Outlook desktop, and Outlook web.

1. Sign out and sign back in to both apps, ensuring the same account.

1. In Teams desktop: Click your profile (top-right) > Sign out. Quit from the system tray if Teams stays running. Reopen and sign in with the same account Outlook uses.

1. In Outlook for Windows: File > Office Account > Sign out. In Outlook for Mac: Outlook menu > Sign Out. Sign back in with the same account as Teams.

2. Fully quit and restart the apps, then restart the machine if needed.

2. Right-click the Teams tray icon > Quit and close Outlook fully. Reopen both apps. If that doesn’t help, reboot the device and check again.

3. Confirm account and basic connectivity.

• Check account: both apps must show the same email/UPN.
• Check time: system clock set to automatic network time.
• VPN or proxy: temporarily disconnect VPN and test, or switch to a different network (mobile hotspot) to rule out network path blocking.

If presence matches after any of these steps, you’re done. If not, proceed to the deeper diagnostics below.

If quick checks fail: branching diagnostics (client-only vs tenant/server causes)

First decide whether the issue is limited to this device or affects multiple users. That determines whether you follow client repairs or tenant/server checks.

A. Is it only this device? (client-only)

1. Test web clients: sign in to Teams web and Outlook web in the same browser and account.

• If web shows correct presence while desktop apps do not, treat this as a local client issue and follow the client repairs in the next section.
• If web also shows the mismatch, move to the tenant/server branch.

B. Is it multiple users, regions, or client types? (tenant/server)

• If many users, whole groups, or multiple client types show mismatches, or if web and mobile are affected, suspect tenant-side problems: Exchange, Graph, OAuth, presence policies, licensing, or a Microsoft service issue. Proceed to the tenant/server checks and evidence collection section.

C. Mixed-account or shared mailbox scenarios

• If Outlook is open to a shared mailbox or you’re viewing mail as a delegate, remember that Teams shows the signed-in user's presence, not the shared mailbox.

Client-only repairs (exact steps for Teams and Outlook clients)

If web works but desktop apps don’t, follow these repairs. Perform them on the affected device and keep the order.

Clear Teams cache (Windows)

%appdata%\Microsoft\Teams

1. Quit Teams: right-click the tray icon > Quit.
2. Delete the contents of these folders inside %appdata%\Microsoft\Teams: Application Cache, Blob_storage, Cache, databases, GPUCache, IndexedDB, Local Storage, tmp.
3. Restart Teams and sign in.

Expected result: presence updates within a minute after sign-in. If not, reinstall the Teams client from your tenant’s approved source and try again.

Clear Teams cache (Mac)

1. Quit Teams.
2. In Finder, remove contents of ~/Library/Application Support/Microsoft/Teams (you can move them to a temporary folder).
3. Restart Teams and sign in.

Outlook profile reset (Windows)

1. Close Outlook.
2. Open Control Panel > Mail > Show Profiles.
3. Add a new profile and configure your account, then set it as default. Open Outlook and sign in.

Outlook for Mac

1. In Outlook menu > Preferences > Accounts, remove and re-add the account if credentials are synced via Exchange/Office 365.

If these steps don’t restore sync and web is correct, capture logs and escalate to your admin with the evidence described later.

Network and proxy troubleshooting (when the path is blocked)

If the desktop app fails while web works, or presence returns on a different network, treat this as a network path problem. These checks help confirm that.

1. Test without VPN or on a different network (mobile hotspot).

• If presence returns off-VPN, the VPN or corporate proxy is likely blocking or intercepting authentication or Graph calls.

2. Check browser DevTools when running Teams web: open the Network tab, reproduce presence activity, and watch for failed requests to Graph or Exchange endpoints with 401, 403, or network errors.

3. Ask IT to verify proxy/TLS interception settings and to whitelist Microsoft 365 endpoints required for presence. IT should consult Microsoft 365 documentation for the current endpoint list.

Tenant/server causes and admin checks

If multiple users or client types are affected, admins should check service health, licensing, API access, and hybrid connectivity. These items commonly cause tenant-side presence problems.

• Service health: check Microsoft 365 Service health for Exchange Online and Teams for known outages.
• Licensing: verify users have Teams and Exchange Online mailbox licenses assigned.
• Presence APIs: confirm whether the tenant uses Exchange Online presence (EWS) or Microsoft Graph presence APIs and that any service principals or app permissions are valid.
• Hybrid Exchange: if using Exchange on-premises or hybrid, verify OAuth between Exchange and Azure AD and that EWS is reachable from Microsoft services.
• Presence policies: review Teams admin center for custom presence policies that might control or limit presence syncing.

If tenant settings or service issues are suspected, collect the evidence described below and open a support ticket with Microsoft or escalate internally.

Verify sync and capture logs for escalation

Confirm the fix by checking that presence matches across clients within a minute or two. This section lists logs and the minimum ticket contents for IT or Microsoft Support.

Presence should match (Available, Away, Do not disturb, Out of Office) across Teams desktop, Teams web, Outlook desktop, and Outlook web within a minute or two for activity-driven changes. Calendar-driven states may take longer while services propagate.

Logs and evidence to collect before escalating:

• Screenshots showing the mismatch with visible timestamps and account name.
• Teams desktop client logs: press Ctrl+Alt+Shift+1 in Teams; the client saves a zip to your Downloads folder. Attach that zip.

Teams desktop: press Ctrl+Alt+Shift+1 to collect logs

• Outlook logging: enable File > Options > Advanced > Enable troubleshooting logging, reproduce the issue, then collect log files.
• Browser traces: export a HAR file from DevTools Network tab when running Teams web and reproducing the issue.
• Network tests: note whether the issue disappears off-VPN and include traceroute or simple connection test results.

Minimum ticket contents for IT or Microsoft Support:

• Short summary: affected users, the mismatch observed, first occurrence time, and duration.
• Steps you already tried: sign-out/in, cache clear, web test, VPN test, profile reset.
• Affected clients and versions (Teams and Outlook desktop versions if available).
• Attachments: Teams logs zip, Outlook logs, HAR file (if available), screenshots, and any relevant error messages or service-health screenshots.
• For tenant escalations: include the user's UPN, Azure AD sign-in failure IDs (if any), and whether multiple users or groups are affected.

When to escalate and what to include

Escalate to your tenant admin or Microsoft Support when multiple users, locations, or client types are affected, or when web clients also show the mismatch. Include the evidence listed earlier and a clear reproduction path.

When you open a ticket, tell admins which users and devices are affected, the exact times you collected logs, and the quick tests that reproduced or resolved the issue locally. Attach the Teams logs zip, Outlook logs, HAR files, screenshots, and network test results.