Free tools Windows power users keep installed
One-click scans. No signup required.
@Mentions in Outlook are meant to create real, trackable mentions—people should get a notification and the message should include the correct recipient identity. When @mentions stop working, it’s usually not a single “magic” setting; it’s a mix of account permissions, directory visibility, client behavior, and Microsoft 365 policy.
This guide walks you through tested methods for 2024, organized by platform and by failure mode. You’ll learn what to check first, the exact settings to touch, and what to do when the usual fixes don’t trigger mention suggestions or notifications.
As an Amazon Associate I earn from qualifying purchases.
What @Mentions in Outlook actually are (and why they fail)
In Microsoft 365, @mention behavior depends on the client’s ability to resolve a person from your organization directory and then attach that identity to the message being composed. If Outlook can’t confidently resolve the identity (or your org policy blocks mention experiences), your message may show plain text instead of a true mention.
Quick triage: confirm the problem and narrow the cause
Before changing settings, confirm exactly what’s broken. “Not working” can mean different things, and each points to a different cause.
Identify the symptom
- Mentions don’t suggest names when you type
@. - Names suggest, but the mention won’t attach after you select the person.
- Mention sends, but the recipient never gets a notification.
- Mentions work in one mailbox/account but not another.
Check who you’re trying to mention
- Are they in the same Microsoft 365 tenant as you?
- Are they a mail-enabled user with a valid directory identity (not an external contact only)?
- Do you see their presence in your address book / people picker?
If @mentions fail only for specific people, you likely have directory or visibility scope issues—not a client setting problem.
Fixes that work across platforms
Start with these because they eliminate the most common causes: stale client state, invalid identity resolution, and account-level policy/permissions.
1) Verify you can resolve the person in your people picker
In a new email (or meeting invite), click the To field and start typing the same name/email you’re trying to mention. If you can’t resolve them there, @mentions won’t work either.
Recommended Free Tools
2) Use the correct syntax and selection behavior
Type @ then the person’s name. For best results, choose the suggested person entry (mouse click or keyboard selection). Don’t rely on free-typing the name; free text won’t reliably create a real mention identity.
3) Check if you’re editing HTML vs plain text mode
Some Outlook experiences behave differently depending on message format. If you have a setting that forces plain text, toggle back to HTML (where available) and test mentions again.
4) Update Outlook and restart your app
Microsoft frequently updates Outlook’s mention resolution and suggestion components. Make sure you’re on a current build:
- Windows: update Outlook via File > Office Account > Update Options > Update Now.
- macOS: update via the Microsoft AutoUpdate or macOS App Store (depending on how Office is installed).
Then fully close Outlook and reopen it. For stubborn UI caching, a machine reboot can help.
5) Test from a different device or mode
If you can, send the same email draft from Outlook on the web (OWA). If OWA works while your desktop client doesn’t, you’re looking at a client-specific issue (add-in, local settings, or build-specific behavior).
Outlook for Windows (new Outlook + classic) fixes
Windows users often see different behavior between new Outlook and classic Outlook. If @mentions fail in one, try the other as a diagnostic path.
Step-by-step: switch to classic Outlook (or back)
- Open Outlook for Windows.
- Look for the toggle to switch between new Outlook and classic Outlook (often found in the upper-right area).
- Compose a new message and test
@mentions again.
If mentions work in one mode but not the other, focus troubleshooting on that specific client.
Disable add-ins (classic Outlook)
Add-ins can interfere with the compose experience and content rendering.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →- In classic Outlook, go to File > Options.
- Select Add-ins.
- At the bottom, next to Manage, pick COM Add-ins and click Go.
- Uncheck non-Microsoft add-ins and restart Outlook.
- Test @mentions by selecting the suggested person entry.
Repair Office (when everything fails)
If mentions fail across multiple accounts and both HTML/plain modes, a repair can restore broken components.
- Close Outlook.
- Open Windows Settings > Apps > Installed apps.
- Find Microsoft 365 or Office and choose Modify.
- Select Quick Repair. If that doesn’t help, run Online Repair.
Clear focus on the compose box (avoid stale drafts)
If you’re editing a very old draft, the compose surface can behave oddly. Create a brand-new message, type @, select the suggested person, and send a test to confirm.
Outlook for Mac fixes
macOS clients can show @mention issues tied to Office build, local caches, or add-in conflicts. The fastest path is to test in a clean new compose window and, if needed, isolate add-ins.
Step-by-step: test in a new message composer
- Open Outlook for Mac.
- Click New Email.
- In the message body, type
@followed by the person’s name. - Select the person from the suggestions.
If mentions work in a fresh message but not in your existing drafts, don’t force the old draft—start a new one.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsDisable add-ins on macOS (Microsoft 365 apps)
Exact menus vary by Office version, but the process is typically:
- Go to Outlook > Settings (or Tools > Options depending on build).
- Find add-in management (often under add-ins or extensions).
- Disable third-party add-ins and restart Outlook.
- Test @mentions again.
Update Office, then relaunch
Update to the latest Outlook build for macOS (Microsoft AutoUpdate). After updating, quit Outlook completely and reopen it.
Outlook on the web (OWA) fixes
OWA is your best “control test.” If mentions work in OWA, the problem is likely your desktop client (build, add-ins, or local settings). If they also fail in OWA, it’s more likely tenant policy or directory visibility.
Rank #3
- 【Portable Mini Keyboard】Ultra-small size,attached detachable USB-C cable,effectively saves desktop space. You can connect the mini keyboard (plug and play) and a normal-size keyboard with the same computer at the same time, they will not interfere with each other.
- 【Default function】 The default function of three keys is Copy,Paste,Search,Backspace,Save,Cut, All and Enter(Ctrl+C,Ctrl+V,Ctrl+F,Backspace,Ctrl+S,Ctrl+X,Ctrl+A,Enter).Plug and play,No software needed.Makes workflow super fast.
- 【Other function】 You can also use other functions, such as Shortcut keys, Multi-step operation, Multi-key in one, Undo, Redo, Play, Pause, Volume, Switch song, Forward, Backward, etc. You can control the light color and gradient mode of the case you want through the software or website.
- 【Programming by Website】 The Website is applicable to MacOS,Linux and also Windows Systems.We recommend that you try to use Chrome and Edge Browser to access the website! Website:SayoDevice.com
- 【Device】 Programming will be saved on the device. You don't need to set it up again when you change the computer.If you encounter any problems with the keypad, please contact us, we will help you deal with it as soon as possible.
Test in OWA with a clean compose and correct selection
- Go to outlook.office.com.
- Click New message.
- In the message body, type
@and start the name. - Select the suggested person entry.
- Send to a test mailbox you control and verify notifications.
Try the light theme toggle and browser refresh
Some compose rendering issues are browser-session specific. Refresh the page (Ctrl+R / Cmd+R) and test in a different browser like Chrome or Edge. If your org allows it, try an incognito window to exclude extensions.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallDisable browser extensions temporarily
Ad blockers, privacy tools, and corporate security extensions can disrupt mention suggestion scripts.
- Turn off extensions for outlook.office.com.
- Reload the compose window and test again.
Outlook mobile fixes (iOS and Android)
Mobile clients sometimes have partial feature parity. If you’re trying to mention multiple people or you don’t see suggestions, test on desktop or OWA to confirm whether it’s a mobile-only limitation.
Step-by-step on iPhone and iPad (iOS)
- Update the Outlook app in the App Store.
- Open Outlook and start a new email.
- Type
@then the name. - Use the suggestion list and select the correct person.
- Send a test message to confirm notifications.
Step-by-step on Android
- Update the Outlook app in Google Play.
- Create a new email.
- Type
@and select the suggested person entry. - Send a test message and verify that the mention resolves.
Force re-authentication if the mailbox is stale
If Outlook mobile is signed in through a cached token that’s expired or partially broken, mentions may degrade. Remove the account from the app and add it again (only if your org policy allows it).
Common edge cases and gotchas
Most mention failures trace back to one of these scenarios.
External recipients (outside your tenant)
@mentions are typically designed for internal directory identities. If you’re mentioning external addresses, Outlook may treat it as plain text or fail to resolve identities.
Shared mailboxes and room mailboxes
Some mailbox types may not be mention-resolvable depending on how your directory and Exchange objects are configured. If you can’t mention a shared mailbox, test by addressing it in the To field first and then try @ again in the body.
Directory sync delays
After HR changes or directory updates, it can take time for identity resolution. If someone was just added or renamed, wait and retest after your tenant’s directory refresh window.
Policy restrictions from IT
Your organization may restrict mention experiences or reduce suggested identity behavior. In that case, only admin changes (Exchange/Microsoft Entra ID and Exchange settings) will fully fix it.
Recipient notification settings
Even if the mention attaches correctly, the recipient might have notification settings that silence mention alerts. That can look like “@mentions not working” even though the mention is valid.
Troubleshooting when mentions still don’t trigger
When the obvious fixes don’t help, use a structured approach. The goal is to determine whether the failure is client-side, browser-side, or tenant-side.
1) Compare behavior across three surfaces
- Test in OWA (outlook.office.com) compose.
- Test in desktop Outlook for Windows.
- Test in Outlook mobile (iPhone or Android).
If two surfaces fail, tenant policy or directory resolution is more likely. If only one fails, isolate that client.
2) Check the exact account and mailbox type
- Confirm you’re using the intended Microsoft 365 account (same tenant).
- If you have multiple accounts in Outlook, test mentions in each one.
- Switch between shared mailbox and your user mailbox if applicable.
3) Remove third-party interference
- Disable Outlook add-ins (Windows) and extensions (OWA).
- Try a different Windows user profile or a different browser profile to exclude local interference.
4) Validate message composition format
Compose a brand-new message in HTML, not a forwarded or legacy draft. Then test: type @, select the suggested person, and send.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →5) Use a test notification recipient you control
If you’re verifying mention effectiveness, send to a second mailbox you control (or a teammate who can confirm notifications). This distinguishes “mention resolution failed” vs “notification blocked.”
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Workarounds that keep your workflow moving
If your org is mid-rollout or a specific client build is buggy, you can still get the job done.
Workaround A: Address in To/CC, then use plain text name
If you can add the person in To or CC, they’ll reliably receive the email even if mention notifications aren’t firing. Pair this with a plain-text “@Name” in the body for clarity.
Workaround B: Use OWA for mention resolution
If desktop Outlook is failing but OWA works, draft messages in OWA and send from there. You can also copy/paste message content into OWA while the mention feature is behaving.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Workaround C: Escalate via IT with proof
When mentions fail for all users or specific users, IT can check tenant policy. Provide:
- Your tenant type (Microsoft 365 business or enterprise)
- Exact client (e.g., Outlook for Windows new Outlook)
- Which recipients fail (internal user? shared mailbox? external?)
- Whether OWA works
Comparison: @Mentions vs Teams mentions vs plain text
@Mentions in Outlook are not the same as Teams mentions. Teams mentions are handled in Teams message posting and can route notifications differently.
| Method | Where it works | Notification reliability |
|---|---|---|
| @Mention in Outlook compose (select from suggestions) | Outlook email/meeting surfaces that support mentions | High when identity resolution succeeds and notifications are enabled |
| Teams mention | Teams chat/channel messages | Depends on Teams notification settings and channel policies |
| Plain text @Name | Any email body | Low; recipient gets email only if they’re in To/CC |
FAQs
Why can I type @ but I don’t see any suggestions?
That usually points to identity resolution being unavailable—either the directory lookup isn’t working, your org policy restricts the mention experience, or an add-in/extension interferes with the compose UI. Test in OWA to confirm whether the issue is client-side.
I can select a suggested person, but they’re not getting notified. What gives?
Two common causes: (1) the mention didn’t attach properly (often happens if you free-typed instead of selecting the suggestion), or (2) the recipient’s notification settings don’t include mentions. Verify by sending a test and asking the recipient to confirm how notifications are configured.
Do @mentions work for external email addresses?
Often, they don’t behave like internal directory mentions. External recipients may require addressing via To/CC to ensure delivery, with plain text “@Name” only serving as a visual cue.
What if @mentions work for me but not for my teammate?
That points to either a user-specific mailbox/account state, different app build, or recipient-side notification/policy differences. Have them test in OWA and compare add-ins/extensions.
Is this a known Outlook bug in 2024?
Outlook compose behavior can regress across specific releases. Updating Outlook/Office and comparing results between OWA and desktop helps confirm whether you’re hitting a client build issue vs a tenant policy/directory problem.
Bottom Line
When Outlook @mentions aren’t working, treat it like a resolution problem: confirm the directory lookup (people picker), ensure you select the suggested identity, then isolate client interference using OWA as your control test. If the feature fails across surfaces, the fix usually lives in tenant policy or directory configuration.
Recommended Free Tools
If you want the fastest path to a stable result in 2024, test mentions in OWA first, then repair or isolate add-ins on the failing desktop client. For recurring enterprise issues, gather evidence (working vs failing surfaces, affected recipients) so your IT team can address the root cause quickly.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
