Fix Teams status showing 'Do Not Disturb' incorrectly

If Teams shows Do Not Disturb (DND) when you are available, it’s usually caused by a local client, a mobile client, an active meeting/Focus session, or cached state on your device; a simple presence refresh, sign-out/sign-in, or disconnecting the mobile app will fix it in most cases. Try the safe, reversible checks below in order — each step takes a few minutes and helps you figure out whether the problem is device-, account- or policy-level before you call IT.

What “incorrect Do Not Disturb” looks like

Confirm the symptom so you don’t chase the wrong problem.

• Your Teams presence icon is red with a white minus (DND) while you are at your desk, responding to other apps, or receiving calls.

• Other people see you as DND even after you set your status to Available in your client.

• You can join or start meetings and receive messages, but your presence shown to others stays DND.

• Your status message contradicts the presence icon (for example, status text says “Available” while the icon shows DND).

What to capture when reporting or escalating:

I am signed in on Desktop (Windows) and Mobile (iOS). My Teams icon shows Do Not Disturb but I can receive calls and messages. Colleague X confirmed they still see DND at 10:42 AM UTC.

Before you start: quick safe checks (do these first)

These checks are non-destructive and tell you where the problem likely lives. Do them in order and stop if a check explains the DND.

• Confirm which devices are signed in:

• Open Teams on each device you use (desktop app, web browser, mobile). Note whether each device shows DND.

• What it means: DND on a single device points to a device-local issue. DND on every device points to an account or tenant policy.

• Check your calendar, meetings and Focus/Do Not Disturb features:

• Look for ongoing meetings, calendar events marked Busy, or a Focus session in Outlook or your OS (Focus Assist on Windows, Do Not Disturb on macOS/iOS/Android). These can set DND automatically.

• What it means: An active meeting or Focus is an intended cause. Stop the Focus session or leave the meeting to test.

• Check the Teams mobile app presence:

• Open Teams on your phone and check the presence there. Mobile clients can push presence to the service and affect other devices.

• What it means: If mobile shows DND while desktop does not, mobile is likely controlling presence.

• Check OS-level DND or Focus Assist:

• On Windows check Focus Assist. On macOS/iOS/Android check Do Not Disturb settings. Toggle the OS setting off briefly to see whether Teams presence updates.

• Recall recent automations or shared settings:

• Think about Power Automate flows, calendar delegates, device enrollments or new software installed in the last 24–48 hours; these can change presence.

• What it means: If you identify an automation or delegate that sets presence, don’t disable shared automations without coordinating with the owner or IT.

Stop condition: if any check explains the DND (active meeting, Focus, mobile controlling presence, OS DND), fix that source and re-check presence before proceeding.

Safe-first fixes in priority order

Try each step, then wait a minute and re-check presence. Stop when presence shows correctly.

1. Refresh presence from your client UI.

2. Sign out and sign back in (Desktop and Web).

Desktop: Click your profile picture > Sign out
Web: Click profile > Sign out (then close the browser tab)

3. Restart the Teams client: quit the app, wait 10 seconds, then reopen it.

• Expected: Re-initializes network connections and clears transient state. If presence still shows DND, continue.

4. Temporarily disconnect or disable the Teams mobile app.

• Steps: Sign out on mobile or force-stop the app and disable background activity for a few minutes, then check desktop presence.

• Why: Mobile clients often hold or push presence. If DND clears when mobile is disconnected, the mobile client caused it.

5. Toggle Airplane mode on the phone briefly and re-check desktop presence.

• What it does: Confirms a mobile-originated presence without uninstalling the app.

6. Clear the Teams desktop cache (safe local step).

1. Quit Teams completely: right-click the Teams icon in the system tray and choose Quit.
2. Open File Explorer and go to the settings path:

%appdata%\Microsoft\Teams

3. Delete only these folders: Application Cache\Cache, blob_storage, Cache, databases, GPUCache, IndexedDB, Local Storage, tmp.
4. Restart Teams and sign in.

• Expected: Presence refresh within seconds to a few minutes.

7. Reinstall the Teams desktop client (last local step).

• Steps: Uninstall via your OS normal method and reinstall from your organization’s approved source or Microsoft Download Center. Check IT policy before reinstalling managed clients.

• If nothing changes after these steps across multiple devices, collect evidence and escalate to IT.

Cross-client checks and interpretation

Isolate where the DND originates.

• Test on another network or device you control (home PC, browser incognito, or a colleague’s machine). If the other device shows Available while yours shows DND, the issue is local to your original device.

• Use the Teams web app in an incognito/private browser to remove client cache from the equation.

• Ask a colleague to confirm your presence from their account and capture a screenshot with the clock visible.

What different results mean:

• Web/other device shows Available while your regular desktop shows DND: client-side cache or local device issue.

• All clients show DND: account-level setting or tenant policy is likely.

• Mobile alone shows DND: mobile client is pushing presence and needs to be updated, signed out, or reconfigured.

When to ask IT and what to request

If the problem persists across devices after the safe-first fixes, collect an escalation pack and then contact IT.

What to request from IT (in priority order):

• Check presence policy assignments in the Teams Admin Center and whether any policy forces DND.

• Verify presence routing between Teams and Exchange/Graph and whether Exchange calendar sync or Graph presence integration is failing.

• Check Conditional Access or session policies that might block presence updates for specific platforms or locations.

• Confirm account licensing and service health for Microsoft Graph Presence and Teams Presence services.

Evidence to collect before calling IT:

• Exact timestamps when you saw incorrect DND and when you ran fixes.

• Devices signed in (device names and client types: Desktop app version, Web, iOS/Android). Include client version numbers if visible.

• Screenshots showing your own client and a colleague’s view of your presence, with clocks visible.

• A concise list of steps you tried in order (refresh, sign out, cache cleared, mobile disconnected).

• Client logs if available. The Teams desktop client has Help > Collect support files — follow your organization’s approved method before sending logs.

Verify the fix, rollback and short-term workarounds

How to confirm the problem is solved and what to do while you wait for IT.

• Verify the fix:

• Ask one or two colleagues to check your presence while you test. Expect propagation within seconds to a few minutes.

• Confirm across desktop, web (incognito), and mobile. If all show the correct presence, the issue is resolved.

• If an admin changed a policy, ask how long that change takes to propagate and check after that window.

• Rollback of changes you made:

• Sign back in to any client you signed out of.

• Reinstall the client if you uninstalled it.

• Restore OS DND or Focus Assist settings to your original preference.

• Re-enable any automation or scheduled task only after coordinating with the owner or IT.

• Short-term workarounds while you wait for IT:

• Manually set your presence to Available and add a brief status message that explains the situation. Example status text:

Showing Do Not Disturb to others — I am available. Please message or call if urgent.

• Use Outlook calendar or an explicit calendar event to show availability to colleagues if presence remains incorrect.

• If the problem recurs, collect fresh timestamps, screenshots and logs and reopen the escalation with IT.

Conclusion

If the safe checks and fixes above don’t clear DND across at least two clients, gather the evidence listed and escalate to IT so they can inspect tenant policies, Graph/Exchange presence routing, and service telemetry.