When you open a contact that is linked to a shared mailbox, Teams may show a presence status that does not match reality. You might see a green Available dot for a colleague who is actually offline, or a red Busy indicator for someone who is in a meeting. This happens because Teams cannot read presence from a shared mailbox object the same way it reads presence from a user account. This article explains why the presence status is wrong and shows you how to fix it using the correct Teams policies and contact settings.
The root cause is that shared mailboxes are not licensed user accounts. They do not have a presence state stored in Teams. When you add a shared mailbox as a contact, Teams tries to map it to a user, but the mapping often fails. The fix involves removing the broken contact, adding the correct user account, and checking the Teams policy that controls contact presence.
Key Takeaways: Fixing Presence for Shared Mailbox Contacts
- Teams > Contacts > Add contact: Use the user account email, not the shared mailbox address, to get correct presence.
- Teams admin center > Messaging policies > Contact sync: Set this policy to On to allow presence to sync from the user directory.
- Teams > Settings > Privacy: Turn on presence sharing to let other users see your real status.
Why Teams Shows the Wrong Presence for a Shared Mailbox Contact
A shared mailbox is a security principal in Exchange Online that does not have a Teams license. It has an email address, but it does not have a presence state because presence is tied to a signed-in user or a licensed resource. When you add a shared mailbox address as a contact in Teams, Teams attempts to resolve that address to a directory object. If the resolution succeeds, Teams may show a default presence such as Available, even if no one is actively using that mailbox. If the resolution fails, Teams may show Offline or Unknown.
The problem also occurs when a user has a shared mailbox set as their primary SMTP address in the contact card. Teams looks up the user by that address, but the shared mailbox is not the user account. The result is that the presence dot reflects the shared mailbox object, not the actual person. This is a common issue in organizations that use shared mailboxes for departments or roles, such as support@contoso.com or sales@contoso.com.
Another angle is that Teams caches contact information locally. If you previously added the shared mailbox as a contact and then the mailbox was converted to a user mailbox, the cached entry may still point to the old object. The presence status can stay wrong until you clear the cache or remove and re-add the contact.
Steps to Fix the Presence Status for a Shared Mailbox Contact
Follow these steps to correct the presence status. You will need to remove the incorrect contact and add the correct user account. You may also need to adjust a Teams policy if the presence does not update after re-adding.
- Remove the shared mailbox contact from Teams
Open Teams and go to Contacts by selecting the Contacts icon on the left sidebar. Find the contact that shows the wrong presence. Right-click the contact and choose Delete. Confirm the deletion. This removes the local cached entry that may be pointing to the shared mailbox object. - Verify the correct user account email
Ask the user for their personal work email address, not the shared mailbox address. The user account email is the one that ends with the user’s own name, such as john.doe@contoso.com. Do not use the shared mailbox address like sales@contoso.com. - Add the user account as a new contact
In Teams, go to Contacts and select Add contact. Enter the user’s personal email address in the Email field. Fill in the first and last name if needed. Select Add to save the contact. The presence dot should now show the user’s real status. - Check the Teams messaging policy for contact sync
If the presence still does not update, a Teams admin must check the messaging policy. Go to the Teams admin center at admin.teams.microsoft.com. Select Messaging policies from the left menu. Select the policy that applies to the user. Look for the Contact sync option and set it to On. Save the policy and wait up to 24 hours for the change to propagate. - Clear the Teams client cache
Close Teams completely. Press Ctrl+Shift+Escape to open Task Manager. End all processes that contain Teams in the name. Press Windows+R to open the Run dialog. Type %appdata%\Microsoft\Teams and press Enter. Delete the contents of the folder that opens. Restart Teams and sign in again. This clears the local cache that may hold the old presence data. - Verify the presence after re-adding
After re-adding the contact and clearing the cache, check the presence dot. If the user is online, the dot should be green. If the user is in a meeting, the dot should be red. If the user is offline, the dot should be gray or white. If the presence is still wrong, move to the next section.
If Teams Still Shows the Wrong Presence After the Main Fix
Teams Shows Available for a User Who Is Actually Offline
This can happen when the user has set their presence to appear available even when they are not. The user can change this in Teams by selecting their profile picture and choosing a custom status. To force a correct status, the user should select Reset status in the presence menu. If the issue persists, the user may have a policy that overrides presence. Check the Teams admin center under Presence policies and ensure the policy allows the user to set their own status.
Teams Shows Offline for a User Who Is Online
This often occurs when the user is signed in on the web version of Teams but not on the desktop app. Presence is tied to the user’s active session. Ask the user to sign in to the Teams desktop app or the mobile app. Also check if the user has set their presence to Do not disturb, which may show as offline to others. The user can reset their status by selecting their profile picture and choosing Available.
Presence Never Updates After the Contact Is Added
Teams may not refresh presence automatically for contacts added manually. You can force a refresh by closing and reopening the contact card. Or you can use the search bar at the top of Teams and type the user’s name. The search result will show the live presence. If the search result shows the correct presence but the contact card does not, remove the contact and add it again using the exact email from the search result.
Shared Mailbox Contact vs User Account Contact in Teams
| Item | Shared Mailbox Contact | User Account Contact |
|---|---|---|
| Presence source | No presence state exists | Presence from the user’s Teams session |
| License requirement | No license needed | Teams license required |
| Typical presence shown | Available or Offline, always wrong | Accurate based on real activity |
| How to add in Teams | Add as a contact with the shared mailbox email | Add as a contact with the user’s personal email |
| Best use case | Send email to a department | See presence and chat with a person |
Use the user account contact when you need to see presence. Use the shared mailbox only for email delivery. If you need to see presence for a department, create a team or a group instead of a shared mailbox contact.
After you remove the shared mailbox contact and add the correct user account, Teams will show the real presence status. You can also set the user’s presence to appear offline when they are actually busy by asking them to use the Do not disturb status. To keep presence accurate, make sure the contact is always added with the personal email address and that the Teams messaging policy allows contact sync.
Next, try using the Teams search bar to confirm the presence of any user before starting a chat. You can also pin the contact to the top of your Contacts list by right-clicking the contact and selecting Pin. For advanced control, ask your Teams admin to review the Presence policies in the Teams admin center to ensure no policy is overriding the user’s manual status.