When you mention a contact that belongs to a shared mailbox in Microsoft Teams, the person may not receive an alert or notification. This problem occurs because Teams does not treat shared mailbox contacts as individual users with active presence. Instead, the mention appears as plain text, and the notification system skips it. This article explains why Teams misses these alerts and shows you the exact steps to fix the problem in the Teams admin center and in Outlook.
You will learn how to convert a shared mailbox contact into a real user account, how to verify the policy settings that control mentions, and what to do when the issue persists. The fix involves a combination of Exchange Online settings and Teams policy changes.
Key Takeaways: Restoring Mention Alerts for Shared Mailbox Contacts
- Teams admin center > Users > Manage users: Shows whether the contact is a real user or a mail contact that Teams cannot alert.
- Exchange admin center > Recipients > Mailboxes: Lets you convert a shared mailbox to a regular user mailbox so that Teams recognizes the person.
- Teams admin center > Messaging policies > Mentions: Controls whether users can receive mention notifications; verify this policy is enabled.
Why Teams Ignores Mentions for Shared Mailbox Contacts
Teams builds its mention system on the Azure Active Directory user directory. When you type the @ symbol and search for a name, Teams queries the directory for objects that have a user principal name and a valid presence. A shared mailbox contact is not a user object. It is a mail-enabled contact that exists only in Exchange Online.
Because the contact lacks a user ID, Teams cannot assign a mention token to it. The text stays as plain text, and the notification engine never fires. This is not a bug. It is a design limitation that affects any mail contact, including contacts created for shared mailboxes.
To trigger an alert, the mentioned person must have a real user account with a Teams license. The workaround is to either convert the shared mailbox to a regular user mailbox or to add the shared mailbox as a team member using its email address. The latter method still does not produce alerts, so the conversion is the only reliable fix.
Steps to Fix Mention Alerts for a Shared Mailbox Contact
Follow these steps in order. The first step verifies the current object type. The second step converts the mailbox. The third step checks the Teams policy.
Step 1: Verify the Contact Is Not a User Account
- Open the Teams admin center
Go to Teams admin center > Users > Manage users. Search for the contact name. If the search returns no result, the contact is not a user object. - Check the user type
If the search returns a result, click the user and check the User type field. A shared mailbox contact shows as Guest or Member only if it has a real account. Otherwise, it shows as Contact, which Teams cannot alert.
Step 2: Convert the Shared Mailbox to a Regular User Mailbox
- Open the Exchange admin center
Go to Exchange admin center > Recipients > Mailboxes. Find the shared mailbox entry. - Convert the mailbox type
Select the shared mailbox, then click Convert to shared mailbox if it is not already. To make it a regular user mailbox, click Edit and change the mailbox type to User. This action requires global admin or Exchange admin permissions. - Assign a Teams license
After conversion, go to Microsoft 365 admin center > Users > Active users. Select the new user and assign a Teams license. Without a license, Teams still does not generate alerts.
Step 3: Verify the Teams Messaging Policy
- Open the messaging policy
Go to Teams admin center > Messaging policies. Select the policy applied to the user who sends the mention. - Enable mentions
Scroll to Mentions and confirm it is set to On. If it is off, turn it on and save the policy.
If Mentions Still Do Not Trigger Alerts
Teams Shows the Mention as Plain Text After Conversion
After converting the mailbox, the old mention text may remain plain text because Teams cached the directory. Ask the sender to type a new mention using the @ symbol and search for the converted user name. The new mention should appear with a blue highlight.
The Mentioned User Receives No Notification in the Activity Feed
Check the user’s notification settings. In Teams, click the profile picture and go to Settings > Notifications. Under Mentions, make sure Email and Banner and feed are selected. If they are not, the user will not see the alert.
The Shared Mailbox Is Still Listed as a Contact in Teams
Teams may cache the old contact for up to 24 hours. Wait for the cache to expire, then restart Teams. If the problem persists, remove the contact from the team and add the new user account manually.
Shared Mailbox Contact vs Converted User Account: Key Differences
| Item | Shared Mailbox Contact | Converted User Account |
|---|---|---|
| Object type in Azure AD | Mail contact | User |
| Teams mention support | No alert | Full alert |
| License requirement | None | Teams license |
| Sign-in capability | No | Yes |
| Presence in Teams | Unavailable | Available |
Use this table to decide whether conversion is worth the administrative effort. For a small team, conversion is quick. For a large organization, consider using a distribution group instead, but note that distribution groups do not support individual mentions either.
After applying the fix, test the mention in a private chat before using it in a channel. Type @ and the new user name. If the name appears with a blue highlight and the user gets a banner, the fix worked. If not, recheck the license assignment and the messaging policy.
To prevent future issues, create a standard procedure for adding shared mailbox contacts as real users when they need to be mentioned. Use the Get-Mailbox PowerShell cmdlet to audit which mailboxes are still shared and need conversion.