What to do if Teams status is showing away when I’m active?

Most false Away statuses come from a local client or device idle setting you can fix quickly: restart Teams and check the Teams web app. If the desktop and web disagree, focus on the desktop client. If both show Away, work through calendar, cross-device, and admin checks and collect logs for IT using the escalation packet in the diagnostics section.

Symptom — what you see

You see Teams status as Away while you are actively typing, moving the mouse, or using a mobile device. The problem may be constant, limited to certain hours, or happen after locking/unlocking or resuming from sleep.

This can change chat availability, call routing, and the presence your colleagues see.

Before you start — scope, preconditions and safe checks

You can sign into Teams on at least one client (desktop, web or mobile) with the affected account and you may change local device settings.

• If you are on a corporate-managed device, some settings may be blocked by IT.
• Collect screenshots and timestamps before asking IT to change tenant-level policies.

TL;DR — quick triage you can do in 2 minutes

1. Quit and restart Teams (desktop).

2. Open Teams on the web in a private/incognito browser window and sign in with the same account.

3. Check and clear any manual status (Away, Do not disturb) in Teams.

4. Sign into Teams on a second device (phone/tablet) to compare presence.

If the web shows Available while desktop shows Away, follow the desktop client fixes. If both show Away, move to calendar and admin checks.

Step-by-step diagnostic flow and fixes (stop when fixed)

Follow the steps in order. Stop when a step fixes the status.

1. Restart the client and compare

1. Quit Teams completely and restart it.

1. Open Teams on the web in a private/incognito window and sign in with the same account to compare presence.

Expected: If web = Available and desktop = Away, the desktop client is likely at fault. If both show Away, continue to account-level checks.

2. Check manual status and simulate activity

1. Confirm you didn’t set a manual status: click your profile and verify Status is not set to Away or Do not disturb.

1. Interact with another application (type and move the mouse) for 30–60 seconds, then return to Teams and wait up to 2 minutes for presence to update.

If presence updates, idle detection was the trigger; continue with device power and idle checks below.

3. Device-level settings (Windows)

1. Check power and sleep settings that can make the system appear idle.

Settings > System > Power & battery
Settings > System > Power & sleep

1. Increase display and sleep timeouts for testing (for example, set to 30 minutes) and test presence.

1. Disable USB selective suspend for the active power plan if input devices stop reporting activity.

1. Update or reinstall keyboard/mouse drivers in Device Manager if peripherals intermittently stop reporting activity.

If changing these makes Teams show Available, restore acceptable timeouts for daily use.

4. Device-level settings (macOS)

1. Check battery and energy settings.

System Settings > Battery
System Settings > Lock Screen

1. Prevent the Mac from sleeping during critical work periods and disable aggressive App Nap for Teams where the OS allows it.

Finder > Applications > Teams > Get Info > Prevent App Nap

If Teams updates after these changes, macOS was suspending Teams or input wasn’t delivered.

5. Device-level settings (Android)

1. Open App info for Teams > Battery and allow background activity or remove Teams from battery optimization.

1. Disable any vendor aggressive power-saving mode that forces apps to sleep.

If presence updates on mobile after this, the OS was stopping background presence updates.

6. Device-level settings (iOS)

1. Ensure Background App Refresh is enabled for Teams and disable Low Power Mode while testing.

Settings > Teams > Background App Refresh
Settings > Battery > Low Power Mode

If presence updates after opening Teams or toggling background refresh, iOS background restrictions were preventing presence sync.

7. Calendar and presence sync (Outlook/Exchange)

1. Check the Outlook calendar for events at the time you saw Away and confirm the event's Free/Busy status.

1. Verify the calendar belongs to the same account signed into Teams (multiple mailboxes can confuse presence).

1. Check if the event is marked Busy or Show as: Busy/In a meeting. If it is Busy, Teams will usually reflect Busy/In a meeting instead of Available.

If calendar entries explain the Away state, change the event’s Show as to Free or adjust event ownership and sharing.

8. Cross-device and session conflicts

1. Sign out of Teams on other devices and watch presence on the main device to see if another endpoint forces Away.

If signing out other endpoints fixes presence, pick which device should drive presence or keep only one active session when precise presence matters.

9. Network differences and VPN

1. Test from a different network (home or mobile hotspot) without corporate VPN to see if network policies or proxying affect presence sync.

If presence differs by network, collect network context for IT (VPN on/off, network name).

10. Admin policies, federation, and conditional access

1. If both desktop and web show Away after local checks, ask IT to review tenant presence policies, Azure AD conditional access events, or federation settings that can override presence.

Evidence IT needs: timestamps, account UPN, screenshots and support logs (see diagnostics section).

Verify the fix

Presence should update quickly after you create input.

1. After a change, interact with the device (type and move the mouse) and watch Teams for 2–5 minutes; presence should switch from Away to Available for client/idle fixes.

1. Use Teams on the web in a private window as a control; if both web and desktop show Available, the fix likely worked.

1. If the issue was calendar-driven, start or end the scheduled event and confirm Teams updates presence according to the event’s Show as value.

Collect diagnostics and an escalation packet for IT or Microsoft Support

Collect these items before opening a ticket.

1. Exact account and tenant

• Account UPN/email and tenant name.

2. Timestamps

• Exact local timestamps (with timezone) when you observed the incorrect Away state.

3. What you observed

• Which clients showed Away (desktop, web, mobile) and whether Outlook showed Busy/Free at the same time.

4. Client and OS versions

• Teams desktop: Profile > About > Version and OS version from system settings or About This Mac.

5. Steps you already tried

• List the quick triage steps you ran (restart, web test, sign-out, power changes).

6. Screenshots

• One showing Teams status, one showing the relevant calendar event in Outlook, and one of Teams About > Version.

7. Teams support files and logs

1. In Teams desktop: Profile > Help > Collect support files (use this if available).

1. If Collect support files isn’t available, note the client version and attach screenshots and timestamps; IT can request logs from the tenant side.

8. Browser/network traces (only if web discrepancy exists)

9. Windows Event Viewer (optional)

• Export Application events around your timestamps if there are Teams-related errors.

10. Example escalation packet (copy-paste)

Summary: Teams shows Away while I am actively using the device and interacting with other apps.
Account: user@example.com
Tenant: Contoso
When: 2026-11-12 09:17–09:23 UTC (local timezone: America/YourZone)
Clients tested: Teams desktop (version: <copy>), Teams web (browser + private window), Teams mobile (if tested)
What I saw: Desktop and web both showed Away while I was typing and had mouse movement; Outlook calendar shows <Free/Busy state>
Steps tried: restarted Teams, compared web, signed out/in, checked power settings, disabled battery optimizations on mobile
Attached: screenshots (Teams status, Outlook event), Teams support files, HAR file (if available)
Requested action: Please check tenant presence policies, conditional access events at these timestamps, and server-side presence logs for this account.

When to involve IT or Microsoft Support

Involve IT when local checks don’t fix the problem and both desktop and web show Away, or when calendar entries don’t explain the state.

1. Provide the escalation packet above. Ask IT to check the Teams admin center, Azure AD sign-ins/conditional access logs, and tenant-side presence logs for the timestamps you supplied.

1. Ask Microsoft Support only after IT confirms tenant-side configuration looks correct but server logs or client logs show errors IT cannot resolve; include support files and HAR/network traces if available.

Prevent recurrence — practical settings and habits

You can reduce repeat false Away states with a few habits and settings.

1. Keep Teams and your OS up to date and verify release-note changes against Microsoft Docs or your tenant admin.

1. Use reasonable display and system sleep timeouts rather than disabling sleep completely to avoid false Away states while preserving battery life.

1. On mobile, enable Background App Refresh (iOS) and remove Teams from battery optimization (Android) so presence can update without opening the app.

1. In Outlook, use Show as = Free for personal calendar items that should not change Teams presence. For shared or delegated calendars, coordinate with owners if their events mark you Busy.

1. If presence is business-critical, keep only one active session or decide which device should be authoritative for presence.

Conclusion

If a quick client restart and a web check fix the issue, you’re done. If both desktop and web still show Away after device and calendar checks, collect the diagnostics above and give the escalation packet to IT so they can inspect tenant and server-side logs.