Fix Teams Cannot Start a New Chat for a Shared Mailbox Contact

When you open Teams and try to start a new chat with a contact that belongs to a shared mailbox, the chat window may fail to open or show an error. This problem often appears after a policy change or after the shared mailbox was recently added to your profile. The root cause is usually a mismatch in how Teams resolves the contact’s identity against the shared mailbox’s underlying user object. This article explains why the failure happens and provides step-by-step fixes for the desktop, web, and admin console.

Why Teams Cannot Start a New Chat for a Shared Mailbox Contact

A shared mailbox in Microsoft 365 does not have its own user account with a Teams license. When you search for a contact in Teams, the client resolves the contact against the directory, but the shared mailbox’s underlying object may not have a valid SIP address or a Teams policy assigned. This mismatch prevents the chat service from establishing a session.

Another common cause is a stale Teams cache. The desktop client stores local copies of directory entries, including the shared mailbox’s alias. If the mailbox was recently renamed or had its email address changed, the cache still points to the old identity, causing the chat to fail.

In an organization, the Teams messaging policy may block external or federated chats for certain users. If the shared mailbox contact is external, the policy can silently prevent the chat from starting. The fix requires adjusting the messaging policy or using a direct email address instead of a display name.

Technical Root Cause: Identity Resolution and SIP Addressing

Every Teams chat requires a valid SIP URI for each participant. A shared mailbox has an alias that looks like an email address, but it is not a licensed user. When you type the contact’s name in the To field, Teams queries the Graph API. If the API returns a mailUser object without a valid userPrincipalName, the chat creation fails with error 404 or 500. This is a known limitation of shared mailboxes in Teams.

Steps to Diagnose and Fix Teams Chat Failures for Shared Mailbox Contacts

Follow these steps in order. Each step addresses a different part of the problem. Start with the cache clear because it is the fastest fix.

Step 1: Clear the Teams Desktop Cache

1. Close Teams completely
   Right-click the Teams icon in the system tray and select Exit. Ensure the process is not running in Task Manager.
2. Open the cache folder
   Press Ctrl+R to open the Run dialog. Type %appdata%\Microsoft\Teams and press Enter.
3. Delete the Cache folder
   In the Teams folder, locate the subfolder named Cache. Select it and press Shift+Delete to permanently remove it.
4. Restart Teams
   Open Teams again and try to start a chat with the shared mailbox contact. If the chat opens, the problem was the stale cache.

Step 2: Use the Web Version to Confirm the Issue

1. Open Teams on the web
   Go to teams.microsoft.com and sign in with your work account.
2. Start a new chat
   Click the Chat icon on the left sidebar, then click the New Chat button with the pencil icon.
3. Enter the shared mailbox email
   Type the full email address of the shared mailbox, such as shared@contoso.com. If the chat opens, the desktop client is the problem. If it fails, the issue is with the mailbox configuration.

Step 3: Check Teams Messaging Policies

1. Open the Teams admin center
   Go to admin.teams.microsoft.com and sign in as a Teams administrator.
2. Navigate to Messaging policies
   In the left nav, select Messaging policies under the Teams section.
3. Verify the policy settings
   Check the options for Chat and External users. If the policy blocks external chats and the shared mailbox is external, change the setting to On.
4. Assign the policy to the user
   Go to Users > Manage users, select the affected user, and assign the corrected policy under Policies.

Step 4: Grant Send-As Permissions via PowerShell

1. Connect to Exchange Online
   Open Windows PowerShell and run Connect-ExchangeOnline with your admin credentials.
2. Grant send permissions
   Run the command Set-Mailbox -Identity “shared@contoso.com” -GrantSendOnBehalfTo “user@contoso.com” where user@contoso.com is the person who needs to chat.
3. Wait for replication
   Allow up to 30 minutes for the change to sync. Then try the chat again in Teams.

If Teams Still Has Issues After the Main Fix

Some failures persist even after clearing the cache and adjusting policies. The following scenarios address the remaining edge cases.

Teams Shows a Blank Window When Starting a Chat with a Shared Mailbox

This happens when the shared mailbox has no license and the Teams client cannot create a chat session. The workaround is to create a contact object in the directory that maps to a licensed user. Ask your Microsoft 365 admin to add a mail contact that points to the shared mailbox’s primary SMTP address. Then search for that contact in Teams.

Teams Cannot Start a Chat Because the Contact Is External

If the shared mailbox belongs to another domain, Teams treats it as an external user. Your organization may have federation disabled. Enable federation in the Teams admin center under External access. Alternatively, use the email address directly in the To field instead of the display name.

Teams Says the Contact Does Not Exist

The shared mailbox may not be synced to the Teams directory. In the Microsoft 365 admin center, go to Users > Shared mailboxes and confirm the mailbox is active. If it is inactive, activate it and wait 15 minutes before trying again.

New Teams Desktop vs Teams on the Web for Shared Mailbox Chats

Item	New Teams Desktop	Teams on the Web
Cache clearing	Requires manual deletion of the Cache folder	No local cache to clear
Chat with shared mailbox	May fail due to stale cache	Works if mailbox is properly configured
Policy enforcement	Applies immediately after restart	Applies on page refresh
Best for troubleshooting	Useful for testing cache-related issues	Useful for isolating client-side problems

After applying the fixes, you can now start a new chat with a shared mailbox contact in Teams. Test the chat with both the desktop and web clients to confirm the fix. For ongoing issues, ask your admin to check the Teams service health dashboard for any known incidents. As a final tip, use the keyboard shortcut Ctrl+N in the desktop client to open a new chat window quickly and verify the fix without navigating menus.