You opened the notification centre looking for a Teams message and it was not there. It was never there. Teams draws its own banners instead of handing them to Windows, so they do not enter the notification centre — and nothing that reads notification history can see them, this app included.
The chat applications around it behave differently, which is why this reads as a bug rather than a design. Slack, Outlook, WhatsApp and Telegram all hand their notifications to Windows. Teams keeps them.
How to tell which apps use Windows notifications
Two checks, a minute in total.
Watch what survives
Wait for a banner from the app, let it fade, then press Win + N. If the notification is in the panel, that app uses the Windows notification system. If the banner appeared and the panel stayed empty, the app drew the banner itself.
Look at the settings list
Open Settings → System → Notifications. Every application registered with the Windows notification system has an entry there, with its own toggles. An application that draws its own banners will still show them when you have switched its entry off, because the switch does not reach it.
Run both on Teams and on Slack in the same sitting and the difference shows immediately.
Teams used to offer the choice
Under Settings → Appearance and sound there was a Notification style dropdown with two values: Teams built-in, and Windows. Choosing Windows routed Teams notifications through the operating system, where they behaved like everyone else's — into the notification centre, obeying focus settings, readable by a history tool.
Microsoft removed that option from the new Teams client in an update around April 2024, and a Microsoft community moderator confirmed it in the support thread where users reported the change, describing the Windows notification style as removed in the latest update and unavailable in new Teams.
A more recent piece of evidence says the situation still stands. In May 2026 Microsoft began rolling out a Teams feature, described in the Microsoft 365 message centre as message MC1269215, that lets Teams honour the Windows Do not disturb setting. It is an opt-in toggle, off by default, on Windows 11 and later only.
That feature says where Teams notifications come from. An application whose notifications went through Windows would not need it — Do Not Disturb would already apply to them, the way it applies to Slack. Teams needed a toggle built for it, and unless you go and find that toggle, it is off.
What it costs you
Three consequences, in the order people usually notice them.
- Nothing to go back to. A banner you glanced at and did not read is gone when it fades. There is no panel holding it.
- Focus settings miss them. Turning on Do Not Disturb quietens Windows, and Teams carries on, unless you have found the toggle above and you are on Windows 11.
- No history, from anyone. Windows exposes notifications to applications through a listener that reads the notification centre. A notification that never enters the notification centre is not in that stream, so no tool can record it. This is a boundary of the platform, not a gap in any particular product.
What reaches Windows and what does not
| Application | Uses the Windows notification system | Can be kept in a history |
|---|---|---|
| Slack | Yes | Yes |
| Microsoft Outlook | Yes | Yes |
| WhatsApp, Telegram | Yes | Yes |
| Chrome, Edge, Firefox | Yes | Yes |
| Windows Security, Windows Update | Yes | Yes |
| Microsoft Teams | No | No |
What to do about Teams instead
Nothing brings back a Teams banner once it has faded. What is available is what Teams itself keeps.
- The Activity feed. The bell at the top of the left rail lists unread messages, mentions, replies and reactions. It is the closest thing Teams has to the panel you were looking for, it survives restarts, and it holds far more than a notification centre would.
- Missed activity emails. Settings → Notifications and activity → Missed activity emails, where you choose how often they arrive. They are digests of mentions and replies rather than a copy of every message, and unlike a banner they sit in your mailbox until you deal with them. For anything you cannot afford to miss, this is the mechanism to lean on.
- The conversation itself. Worth saying because the banner was only ever a pointer to it. Filtering the chat list by unread finds what the banner would have told you, as long as your eye has not already passed over the conversation and marked it read.
- The Do Not Disturb toggle, if you are on Windows 11 and it has reached your build. It gives you no history, but it stops the interruption you were trying to control.
Where Notification Logger stands
Notification Logger records every notification that passes through the Windows notification system and keeps it in a searchable local history — Slack, Outlook, WhatsApp, Telegram, the browsers, Windows Security, and the hundreds of applications that use the platform the ordinary way. It does not record Teams, because Teams does not put anything there to record.
We would rather say that here than let you find it out after installing. If Teams is the only source you needed a history for, this app is not the answer and the Activity feed is. If your day also runs through Slack, mail and a browser the rest of the stream is exactly what it keeps.