Missing a Teams message because no notification fired is the kind of problem that erodes trust in the app fast. Someone @mentions you, you never see it, and you find out an hour later from a “did you get my message?” follow-up. The frustrating part is that “notifications not working” almost always has a boring, fixable cause — and most of the time it isn’t Teams at all.
Notifications pass through two gates before they reach you: Windows has to allow them, and Teams has to be configured to send them. A block at either layer kills the alert. Windows Focus assist (now called Do Not Disturb in recent Windows 11 builds) is the single most common culprit, followed by a Teams notification style quietly set to “Off.”
This guide works through both layers in order, from the OS down to per-channel settings, so you stop guessing and find the gate that’s actually closed.
Start at the Windows layer
Before touching anything in Teams, rule out Windows. If the OS is suppressing notifications, no Teams setting will get them through.
Notifications are on for Teams. Open Settings > System > Notifications. Confirm the master toggle is on, scroll to Microsoft Teams in the per-app list, and make sure it’s enabled with Banners (and Sounds, if you want audio) turned on. An app sitting at the bottom of that list with its toggle off is a silent notification killer.
Focus assist / Do Not Disturb. This is the big one. Windows can hold all notifications when Focus assist is set to Priority only or Alarms only, or when a Focus session is running. On Windows 11, check Settings > System > Notifications > Do not disturb and any automatic rules (during certain hours, while gaming, when duplicating your display). A projector or second monitor can trigger “while duplicating my display” and silence everything without you realizing.
Quiet hours and presentation modes. Notifications are also suppressed automatically while you present or share your full screen — that’s by design, so you don’t leak a private message on a projector. Just remember it’s happening.
Windows notification checks
- Settings > System > Notifications master toggle is on
- Microsoft Teams is enabled in the per-app notification list
- Banners and (if wanted) Sounds are on for Teams
- Do not disturb / Focus assist is off or set to allow Teams
- No automatic Focus rule is firing (presenting, second display, gaming)
Then check the Teams layer
With Windows out of the way, move into Teams. Open Settings > Notifications and activity (the gear menu or the … next to your profile picture).
Notification style. Teams can show notifications as native Windows banners or only collect them in the activity feed. If your style is set to Off or Only show in feed for a given category, you won’t see pop-ups. For chat and mentions, set these to Banner and feed so they appear on screen and stay in your activity list.
Do Not Disturb inside Teams. Separate from Windows, Teams has its own DND status. If your presence shows Do Not Disturb, Teams suppresses most banners regardless of Windows settings. Set your status back to Available (or add the right people to your priority access list if you want to keep DND but still hear from them).
Sounds. Sound is its own toggle. If banners appear but you hear nothing, turn notification sounds back on here, then confirm Windows isn’t muting Teams in the volume mixer.
Per-channel and per-chat notifications
Even with everything above correct, channels are quieter by default than people expect. Teams won’t banner every message in every channel, because that would be unusable in a busy team. You opt in to the channels that matter.
For a channel you care about, open the channel, click its More options (…) menu, choose Channel notifications, and pick the level:
Channel notification levels
| All activity / All new posts | Banner + feed for every new message — use sparingly, only for channels you can't miss |
|---|---|
| Banner and feed (custom) | Pop-up for mentions and replies you're involved in; everything else goes to the feed |
| Feed only / Off | No banner; activity collects in the feed (or nothing) — the quiet default for many channels |
The same idea applies to individual chats: you can mute a noisy group chat, or make sure an important one isn’t muted. A muted chat shows a small mute icon and produces no banners. If one specific conversation is silent while everything else works, check whether it’s muted.
Restart, update, then clear the cache
If the settings all look right and notifications still don’t fire, treat it like any other Teams glitch.
- Restart Teams fully — quit from the system tray, confirm the process is gone, relaunch. A surprising number of notification issues are just a stuck session.
- Update Teams. New Teams updates silently, but force a check from the … menu > Check for updates. Notification bugs after an update are common and usually fixed by the next build.
- Clear the cache. Corrupted local state can break notifications specifically. Quit Teams and clear the cache folder — the full steps are in clear the Microsoft Teams cache on Windows. This resolves notification glitches more often than it should.
When it’s more than your machine
If notifications fail for one person, it’s local: Windows settings, Focus assist, Teams settings, or cache. If a whole group loses notifications at once, look higher up.
Managed environments sometimes push a Focus assist or notification policy through Group Policy or Intune that suppresses app notifications more aggressively than users expect. A recent change there can silence Teams for everyone on a configuration baseline. Teams messaging and app setup policies can also shape some behavior. And occasionally it really is a service incident — check Microsoft 365 service health before assuming it’s your fault.
For broader Teams fixes, the Teams meeting troubleshooting guide covers related client and account problems that can ride along with notification issues.
Email notifications and the missed-activity digest
There’s one more layer worth understanding, because it’s where people get confused about what’s actually broken. Teams sends two kinds of email related to activity: the missed activity email (when it thinks you didn’t see a live alert) and the missed activity digest that summarizes what you missed. These are controlled separately from live banners, under the email section of your notification settings.
If you’re drowning in missed-activity emails, that’s usually a symptom, not the problem — live banners are being suppressed somewhere, so Teams keeps emailing you instead. Fix the live notifications first and the email volume drops on its own. If you simply don’t want the emails regardless, you can turn the missed-activity email and digest down or off in Settings > Notifications and activity without touching your live banner behavior.
The reverse case happens too: someone disables the missed-activity email to cut clutter, then assumes notifications are “off” entirely. The live banner and the email are independent. Turning off one doesn’t affect the other, so check both if your expectations don’t match what you’re seeing.
Wrapping up
Teams notifications run a gauntlet: Windows has to allow them, Focus assist / Do Not Disturb has to be out of the way, your Teams notification style has to be set to banner, your presence can’t be on DND, and the channel has to be set to notify you. Work down that list in order and you’ll find the closed gate quickly — it’s usually Windows-level, and usually Focus assist.
If the settings are clean and it still fails, restart, update, and clear the cache before you go deeper. And when it hits everyone at once, stop debugging the client and look at policy or service health instead.
