Teams notifications are silent: the four toggles that actually control them

It's 4:47 PM on a Thursday. You're cleaning up your inbox before signing off, you glance at Teams, and there it is. Three messages from your boss. Two of them marked urgent. The little red dot has apparently been screaming at you for an hour and a half and you heard absolutely nothing.

Sound familiar?

Yeah. This one comes up in my inbox more than any other Teams problem, and the cause is almost never what people think. They blame the headset. They blame the laptop. They reinstall Teams (please don't reinstall Teams, it almost never helps). The real answer is way more boring. Four different notification systems are stacked on top of each other like a bureaucratic layer cake, and any single one of them can mute the whole thing without telling you.

Once you know where they live, the fix takes maybe two minutes. Getting there is the hard part.

The four layers, in the order they fire

Think of it like an airport. Your message is a passenger. Before it reaches you (the gate), it has to clear four checkpoints. Any single checkpoint can turn it back, and each one is run by a different department that doesn't really talk to the others.

1. The OS itself. Windows or macOS — Focus Assist, Do Not Disturb, the master notification toggle. This is the bouncer at the front door.
2. App-level OS permission for Teams specifically. Even if the bouncer lets apps through, Teams needs its own pass.
3. Teams' internal notification settings. Now we're inside Teams. What kind of alerts does Teams generate?
4. Per-channel and per-chat overrides. The most personal layer. And the one that bites people the most.

In my experience helping clients with this, layer 1 and layer 4 are the troublemakers about 80% of the time. Layer 1 because Windows enables DND on its own for things you didn't sign up for. Layer 4 because someone clicked something six months ago and forgot.

Walk these in order. Don't skip ahead. I know it's tempting.

Layer 1: the OS-level Do Not Disturb

Windows 11

Windows 11 turns on Focus or DND in situations that genuinely surprise people. Plug in a second monitor? DND. Start a PowerPoint? DND. Some Windows updates ship with new automatic rules turned on by default. Fun.

Here's what to check:

• Open Settings → System → Notifications.
• The master Notifications toggle at the top — make sure it's on.
• Click Do not disturb, confirm it's off.
• Expand Set priority notifications. Teams needs to be in that priority list, otherwise even when DND is on for "good" reasons, Teams still gets muted.
• Expand Turn on do not disturb automatically and look at every rule. The big offenders: "When duplicating my display" and "When playing a game." Turn those off unless you specifically want them.

Quick aside — Microsoft renamed Focus Assist to Do Not Disturb in Windows 11, then added a separate thing called Focus Sessions for Pomodoro timers. Both can mute Teams. They have separate schedules. It's confusing. I complain about this every time.

macOS

On a Mac it's System Settings → Focus. Check that nothing's currently active, and look at the Schedule and Smart Activation tabs because — and this is genuinely funny — Macs love to flip on Do Not Disturb during meetings. Which is exactly when you want notifications most. Check that twice.

Layer 2: Teams' app permission inside the OS

So the OS isn't muting all apps. Now: does the OS specifically allow Teams?

Windows 11

• Same path: Settings → System → Notifications. Scroll down to Notifications from apps and other senders.
• Find Microsoft Teams. Heads up — if you have both new Teams and the classic client installed, you'll see two entries: "Microsoft Teams" and "Microsoft Teams (work or school)". Check both.
• Click in. Confirm: Notifications on, Show banners on, Show in notification center on, Play a sound on.

If you only see the classic listing but you're using new Teams, the new client probably hasn't registered with Windows yet. Restart Teams once. The listing should show up. (If it doesn't, that's a sign-in-as-admin-and-restart-the-computer kind of problem and beyond what I'll cover here.)

macOS

• System Settings → Notifications → Microsoft Teams.
• Allow Notifications on. Alert style set to Banners or Alerts — anything except None. Show in Notification Center on.

Layer 3: inside Teams itself

Now we're past the OS and into the app. Click your profile picture, then Settings, then Notifications and activity.

The settings that actually matter:

• Sound. Set to All notifications or at the very minimum Calls and mentions. If this is Off, Teams flashes silently like a fish in an aquarium and that's it.
• Show message preview. Leave it on. Otherwise banners just say "New message" and you have to switch to Teams to see what's going on.
• Notify me when — for Mentions and replies, Reactions, and Calls, set to Banner and feed rather than Only show in feed.

Banner only vs Banner and feed vs Only show in feed

This trips literally everyone up. Including me, the first six times I tried to write about it.

• Banner and feed — popup AND activity counter goes up.
• Banner only — popup, no badge.
• Only show in feed — totally silent. The little bell icon top-left increments by one. That's it. No popup. No sound. Nothing.

If a category is set to "Only show in feed," you will never hear it. Ever. That's the whole game. If your "Mentions and replies" is sitting on that setting, that's why you missed your boss's @mention this morning.

I'd say a third of the silent-Teams cases I see are exactly this and nothing else.

Mac-specific: "Show new activity in dock"

On macOS there's also Show new activity in dock, which controls the bouncing icon and the red badge. If your specific complaint is "the dock icon stopped flagging me," this is your switch. I always forget this one exists until a Mac client mentions it.

Layer 4: the per-channel and per-chat trap

Here's the kicker. Even if layers 1, 2, and 3 are all set perfectly, an individual channel or chat can be muted on its own. And these overrides survive a Teams reinstall. They're stored server-side against your account. Reinstalling Teams does nothing to fix them. (See? I told you not to reinstall Teams.)

Channels

Right-click the channel name → Channel notifications → Custom.

You'll see three rows:

• All new posts — Banner and feed if you want to know about every thread. Off if you only want @mentions to ping you.
• Channel mentions — Banner and feed. Always.
• Replies — Banner and feed if you reply in the thread.

If All new posts is Off, the only thing that'll wake the channel up is @channel. People in chatty channels turn this off and then forget, and then a year later wonder why they keep missing things.

Chats

Open the chat. Click the More options (…) menu in the chat header. Look for Mute. A muted chat shows a tiny bell-with-a-slash icon next to the chat name in the chat list. Unmute it.

The favourites trap

This one's nasty. Teams uses different defaults for your favourited (pinned) channels vs unpinned ones. If you recently unpinned a channel — even by accident — its notification settings can quietly downgrade themselves. Re-pin the channel, then go back into channel notifications and re-confirm. I had a client lose a month of project comms to this exact behavior.

The Outlook OOO sneaker

Wait, Outlook? Yes. Stay with me.

When you turn on Automatic replies in Outlook with a date range covering "right now," Teams reads that and sets your presence to Out of office, which suppresses notification sounds. Banners still show. But no audio. So you're staring at a quiet screen while Teams quietly thinks you're on holiday.

Check it. In classic Outlook, File → Automatic Replies. In new Outlook, the calendar gear icon. Make sure there's no active OOO bleeding into the current time.

Related: if you set your status to Do not disturb in Teams (profile picture → status), Teams suppresses everything except people on your priority access list. Set it back to Available, or to Busy which still pops banners.

Mobile: the battery optimization disaster

Push notifications on Teams mobile go silent constantly because Android (and to a lesser extent iOS) decides Teams is "using too much battery" and starts throttling it. This is the single most common reason for "I never get Teams alerts on my phone."

Android

• Settings → Apps → Teams → Battery → Unrestricted.
• Settings → Apps → Teams → Notifications. Confirm everything is on.
• Inside the Teams app: Menu → Notifications → Block notifications when active on desktop. This needs to be Never or After 3 minutes. If it's When active on desktop, your phone goes silent the second your laptop is unlocked. Which means: never gets alerts during work hours. Which is when you need them.

iOS

• Settings → Notifications → Teams. Allow Notifications on, Sounds on, Banners persistent if you want them to stick.
• Settings → Focus → Personal (or whichever Focus profile is currently active). Teams needs to be in the Allowed Apps list.
• iOS 17+ has Scheduled Summary that batches "non-time-sensitive" notifications. Disable it for Teams or you'll only see Teams alerts twice a day at scheduled times. Genuinely I have no idea why Apple thinks any work chat app is non-time-sensitive but here we are.

A diagnostic flow that takes about three minutes

When notifications go quiet, just walk this:

1. Is OS-level DND or Focus on right now? Off it.
2. Windows notification settings, find Teams, everything on.
3. In Teams: Settings → Notifications and activity → Sound = All notifications.
4. The specific channel or chat that went silent — right-click, set to Banner and feed.
5. Outlook OOO and Teams status both clean.
6. On mobile, kill battery optimization.

That's the whole list. Nine times out of ten, the fix is a single toggle that quietly flipped itself, often weeks before you noticed.

Honestly, the most frustrating part isn't the fixing. It's that Microsoft scattered these controls across four different surfaces with overlapping vocabulary and no master view. Some day they'll consolidate this. Probably not this decade. Until then, bookmark this page.