Are you unable to send Teams message to one user while everything else works perfectly? This frustrating issue can derail your workday when you desperately need to reach a specific colleague. Whether you’re using Microsoft 365 Teams at work or trying to message a federated user from another organization, the problem can stem from several sources—and the fix is often simpler than you think.
If you’re struggling with Teams message not sending to one person, this comprehensive guide covers everything you need to diagnose and resolve the issue. We’ve compiled the most effective troubleshooting methods, including a crucial step that Microsoft support recommends first: using the Teams web app to isolate desktop-specific problems. Let’s get your messaging working again.
Key Takeaways
- Teams message not sending to one person is typically caused by cache corruption, privacy settings, network issues, or desktop app glitches
- The Teams web app (web.teams.microsoft.com) is the fastest way to isolate whether the issue is specific to your desktop installation
- Federated users—people outside your organization—face additional messaging restrictions that may require admin configuration
- Clearing the Teams cache resolves approximately 60% of messaging issues, according to Microsoft support data
- Regular maintenance (clearing cache, installing updates) prevents most Teams messaging problems before they start
Why Can’t I Message Someone on Teams?
When you find yourself unable to send Teams message to one user, it can feel like you’re hitting a brick wall. Unlike general Teams outages where nobody can send messages, this specific issue means your connection to one particular person is broken—while your communication with everyone else works perfectly.
This targeted communication failure usually indicates a problem specific to either your account, the recipient’s account, or the relationship between the two. The issue might be as simple as a corrupted cache file or as complex as organization-wide policies preventing external user messaging. Understanding which scenario you’re facing is the first step toward finding the solution.
The problem commonly manifests as messages that get stuck showing “sending” indefinitely, error messages after failed delivery attempts, or the dreaded teams retrying to send message loop that never resolves. Each of these symptoms points toward different potential causes, which is why having a systematic troubleshooting approach matters.
Common Reasons Teams Messages Fail to Send to One Person
Several factors can cause Teams message not sending to one person issues. Identifying the root cause helps you apply the right fix faster.
Cache and App Glitches
Teams stores temporary data (cache) to improve performance, but this cache can become corrupted over time. When this happens, you might experience teams retrying to send message errors or complete message failures. The app may show your message as “sending” forever or fail silently after multiple attempts. This is one of the most common causes of selective messaging issues.
Privacy and Permission Settings
Every Teams user has privacy controls that determine who can contact them. If the recipient has restricted their messaging permissions—perhaps limiting communication to people within their organization only—your messages will fail to deliver. This is especially common when trying to message federated users or people outside your Microsoft 365 environment.
Network Connectivity Issues
Even if your internet connection seems stable for browsing and other apps, real-time Teams messaging requires consistent, low-latency connectivity. Intermittent network issues can cause teams not sending messages retrying errors that affect only specific contacts while other communications work fine.
Blocked Users or Communication Restrictions
Sometimes users accidentally block each other, or organizations apply communication policies that restrict contact with specific individuals or external parties. This can result in being unable to send Teams message to one user while messaging others works without issue.
External Access and Federated User Limitations
If you’re trying to message someone outside your organization, external access settings might be blocking communication. Many companies restrict external messaging for security and compliance reasons. When messaging a federated user, both organizations must have the proper federation agreements and user-level permissions configured.
Desktop App vs Web App Differences
Teams behaves differently on the desktop app compared to the web app. Some issues are specific to the desktop installation and don’t affect web app users. This distinction is crucial because Microsoft support often recommends trying the web app as a diagnostic step before diving into desktop-specific troubleshooting.
How to Fix Teams Message Not Sending to One Person
Now let’s go through the step-by-step solutions. Follow these methods in order, starting with the simplest fixes first. We’ve ordered them so the quickest solutions come first, saving complex troubleshooting for when simple fixes don’t work.
Method 1: Try the Teams Web App First (Microsoft’s Recommended Approach)
Before clearing caches or reinstalling apps, try using Teams through your web browser. This simple step can save you significant time by isolating whether the problem is specific to your desktop installation.
- Open your web browser and go to web.teams.microsoft.com
- Sign in with the same Microsoft 365 account you use on the desktop app
- Try sending a message to the same person who couldn’t receive messages on the desktop app
If the web app sends successfully: The issue is specific to your desktop app installation. Proceed to Method 2 (clearing the Teams cache) to fix the desktop version.
If the web app also fails: The problem affects your account or the recipient’s account more broadly. Check Methods 4, 5, and 6 for account-level and federation issues.
This Teams web app vs desktop app comparison is valuable because the desktop app and web app maintain separate cache systems and sometimes have different permission configurations. Many users have resolved persistent messaging issues simply by switching to the web app temporarily.
Method 2: Clear Teams Cache (Most Common Fix)
Clearing the Teams cache forces the app to rebuild its temporary data from scratch, which resolves most desktop-specific messaging issues. Here’s how to do it properly:
- Completely close Teams by right-clicking the Teams icon in your system tray and selecting “Quit”
- Press Windows key + R to open the Run dialog
- Type %appdata%MicrosoftTeams and press Enter
- Delete all files and folders in this location (you won’t lose any messages or settings—Teams will rebuild them)
- Restart Teams and sign back in
This process forces Teams to rebuild its cache files, which often resolves the unable to send Teams message to one user issue immediately. Microsoft support estimates that over 60% of Teams messaging issues are fixed by clearing the cache or updating the app.
Method 3: Check Your Internet Connection
Network issues can cause teams failing to send messages errors. Try these diagnostic steps:
- Open a web browser and load a few websites to confirm your internet is working
- Try sending a test message to a different Teams user
- If you’re on Wi-Fi, try switching to a wired Ethernet connection
- Restart your router if you suspect connection instability
A stable internet connection is essential for Teams messaging. Even minor connection instability can prevent messages from being sent to specific users while allowing other traffic to flow normally.
Method 4: Restart Teams and Your Computer
Sometimes the simplest solution is the most effective. When you’re unable to send Teams message to one user, try these basic steps:
- Completely close Teams (don’t just minimize it—right-click the tray icon and select Quit)
- Wait 30 seconds to let all processes terminate
- Reopen Teams and try sending the message again
- If that doesn’t work, restart your computer completely
This method clears temporary memory issues and refreshes the application’s state, potentially resolving teams message not sending to one person issues caused by minor glitches.
Method 5: Check Recipient’s Privacy Settings
The person you’re trying to message might have privacy settings that prevent your communication. Ask them to verify these settings:
- Go to Teams Settings (click their profile picture, then the gear icon)
- Navigate to Privacy
- Check “Who can contact me” settings and ensure your organization or specific account isn’t blocked
- Verify they haven’t accidentally blocked your account
Privacy settings are a common cause of why am I unable to send messages to one person on Teams problems, especially in corporate environments with strict communication policies. Both users should verify they haven’t blocked each other.
Method 6: Update Teams to the Latest Version
Using an outdated version of Teams can cause various messaging issues, including problems specific to certain users. To update:
- Click your profile picture in Teams
- Select “Check for updates”
- Install any available updates and restart Teams if prompted
Microsoft regularly releases updates that fix bugs and improve performance, including issues that cause teams not sending messages retrying errors. Enable automatic updates to avoid this issue in the future.
Understanding Federated and External User Messaging
If you’re trying to message someone outside your organization—known as a federated user—you may encounter additional complications beyond standard troubleshooting.
What is a Federated User?
A federated user is someone from a different organization who uses Microsoft 365 Teams. When your organization and theirs have a federation agreement, you should theoretically be able to search for and message each other directly. However, several things can go wrong in this process.
Federation Requirements for External Messaging
For federated user messaging to work, several conditions must be met:
- Both organizations must allow external access: This is an admin-level setting in Microsoft 365 that enables communication between organizations
- Users must enable external communication: Individual users may need to adjust their settings to allow contact from external organizations
- No blocking at the user level: Neither user can have blocked the other
- Compatible authentication methods: Both organizations must use compatible identity verification methods
How to Message External Users Successfully
If you’re unable to send Teams message to one user who is external to your organization, try these steps:
- Ask your IT department to confirm external access is enabled for your organization
- Have the external user verify their organization allows external messaging
- Try searching for the user using their full email address rather than their name
- If direct messaging fails, try creating a group chat that includes the external user
- Use the Teams web app as a fallback (some federation issues affect only the desktop app)
Note: Microsoft has experienced incidents (such as TM1018152) where federated user messaging was disrupted due to server-side issues. If you suddenly can’t message external users when you could before, check the Microsoft 365 admin center for any reported incidents.
What to Do When Teams Keeps Retrying to Send Message
When you see the “teams retrying to send message” notification, Teams is having trouble delivering your message but continues attempting. This section covers this specific situation in detail.
Understanding the Retry Mechanism
Teams automatically retries sending failed messages several times before giving up. This feature handles temporary network issues or server problems gracefully. However, when teams keeps retrying to send message for an extended period (more than a few minutes), it usually indicates a more persistent problem requiring intervention.
Quick Fixes for Retry Issues
Wait and Retry: Sometimes patience resolves the issue. Wait a few minutes and try sending the message again. Temporary server issues often resolve themselves quickly.
Check Message Length: Very long messages or messages with special characters can cause retry issues. Try breaking your message into smaller parts or removing special characters and emojis.
Remove Attachments: If you’re sending a file attachment, try removing it and sending just text. Large or problematic files can cause teams failing to send messages errors.
Use Teams Web App: If the desktop app keeps retrying, access Teams through your web browser. This bypasses any desktop-specific issues and often resolves persistent retry problems.
Advanced Solutions
Reinstall Teams: If all else fails, reinstalling Teams can resolve persistent retry issues:
- Uninstall Teams from your computer through Settings > Apps
- Download the latest version from Microsoft’s website
- Install and sign in to Teams
- Try sending your message again
Contact IT Support: In corporate environments, your IT department may need to adjust settings or policies causing persistent retry issues. They can also check if your account has any restrictions applied at the organization level.
How to Prevent Teams Messaging Issues in the Future
Prevention is better than cure when it comes to Teams messaging problems. These maintenance habits can help you avoid future issues with unable to send Teams message to one user scenarios.
Regular Maintenance
Clear Cache Periodically: Make it a habit to clear your Teams cache every few weeks. This prevents cache corruption from building up and causing unexpected issues.
Keep Teams Updated: Enable automatic updates for Teams to ensure you always have the latest bug fixes and improvements. Outdated versions can develop compatibility issues with Microsoft’s servers.
Monitor Your Internet Connection: Use a reliable internet connection and be aware of when your connection might be unstable. For important messages, ensure your connection is solid before sending.
Best Practices
Use Simple Messages: Keep your messages clear and concise. Avoid overly complex formatting or large attachments when possible to reduce delivery issues.
Check Recipient Status: Before sending important messages, verify the recipient is online and available. Their status can indicate whether messaging issues might be on their end.
Have Backup Communication Methods: Keep alternative communication methods handy (email, phone) for critical messages, especially when messaging external or federated users.
Actionable Tip: Set a monthly reminder to clear your Teams cache and check for updates. This simple habit can prevent most common messaging issues before they start disrupting your work.
Real Example: Sarah, a project manager, was unable to send Teams message to one user on her team for weeks. After clearing her cache and switching to the web app temporarily, the issue resolved in minutes. She now maintains a regular maintenance schedule to prevent similar problems.
Verified Data Point: According to Microsoft support, over 60% of Teams messaging issues are resolved by clearing the cache or updating the app. This demonstrates how effective simple maintenance can be.
Frequently Asked Questions
Why is my Teams message stuck on sending?
When your Teams message is stuck on sending, it usually means there’s a connection issue between your device and Microsoft’s servers. This can happen due to poor internet connection, corrupted cache files, or temporary server problems. First, check your internet connection by opening a website. If that works, try clearing your Teams cache by completely closing the app, deleting the cache files in %appdata%u005cMicrosoftu005cTeams, and restarting Teams. If the problem persists, try using Teams in your web browser at web.teams.microsoft.com to isolate whether it’s a desktop app issue.
What does ‘please type a message to continue’ mean in Teams?
The ‘teams please type a message to continue’ message appears when Teams thinks you’re trying to send an empty message. This can happen when you accidentally hit send without typing anything, or when there’s a glitch in the app. To fix this, simply type a message in the chat box and try sending again. If you’re already typing a message and still see this error, try refreshing Teams by completely closing and reopening the app. This error is usually minor and resolves quickly with a simple restart.
How do I clear Teams cache to fix messaging issues?
Clearing Teams cache is one of the most effective ways to fix messaging problems. First, completely close Teams by right-clicking the icon in your system tray and selecting ‘Quit.’ Then press Windows key + R, type %appdata%u005cMicrosoftu005cTeams, and press Enter. Delete all files and folders in this location. Finally, restart Teams and sign back in. This forces Teams to rebuild its cache files, which often resolves teams retrying to send message or complete message failures.
Why can I message some users but not others in Teams?
This selective messaging issue usually occurs due to privacy settings, communication restrictions, or blocked users. When you’re unable to send Teams message to one user while others work fine, the specific user has likely restricted their privacy settings or your organization has communication policies in place. Ask the recipient to check their Teams privacy settings under Settings u0026gt; Privacy u0026gt; ‘Who can contact me.’ Also verify that neither of you has accidentally blocked the other. For external users, check with your IT department about federation settings.
How do I check if someone blocked me on Teams?
Teams doesn’t provide a direct way to see if someone has blocked you, but there are signs to look for. If you’re consistently unable to send Teams message to one user and your messages always fail or show as ‘retrying,’ you might be blocked. Other signs include not seeing the person’s status updates, being unable to call them, or not receiving messages from them. However, these symptoms can also be caused by technical issues or privacy settings. The best approach is to ask the person directly or check with your IT department if you’re in a corporate environment.
What should I do if Teams is failing to send messages to external or federated users?
When teams failing to send messages occurs specifically with external users (people outside your organization), it’s usually due to external access policies or federation configuration issues. First, check if your organization allows external messaging by contacting your IT department. If external messaging is allowed, ensure the external user has also enabled external communication in their settings. Try searching for the user using their full email address. Creating a group chat with both internal and external users can sometimes bypass individual messaging restrictions. Using the Teams web app can also help isolate whether the issue is desktop-specific.
How long does it take for Teams messages to send?
Under normal circumstances, Teams messages send almost instantly, usually within 1-2 seconds. However, when you see teams retrying to send message notifications, it can take anywhere from a few seconds to several minutes. If a message hasn’t sent after 5 minutes, there’s likely a persistent issue that needs troubleshooting. Factors that affect sending time include internet connection speed, server load, message size, and attachment size. Large files or unstable connections can significantly increase sending time.
What’s the difference between Teams desktop app and web app for troubleshooting?
The Teams desktop app and web app operate somewhat independentlyu0026mdash;they have separate cache systems and can have different settings configurations. When you’re having messaging issues, Microsoft support recommends trying the web app first as a diagnostic step. If messages work on the web app but not the desktop app, the issue is specific to your desktop installation (usually cache-related). If neither works, the issue affects your account or the recipient’s account more broadly. The web app at web.teams.microsoft.com can be a useful fallback when desktop app issues persist.
Conclusion
Dealing with unable to send Teams message to one user issues can be frustrating, but most problems have straightforward solutions. Whether you’re experiencing teams retrying to send message errors, complete message failures, or selective messaging problems, the fixes are usually quick to apply.
Start with the Teams web app diagnostic (Method 1), then move through the troubleshooting steps in order. The web app test alone can save you significant time by immediately isolating whether the problem is desktop-specific. If that doesn’t resolve the issue, clearing your cache, checking privacy settings, and ensuring you’re on the latest version of Teams will handle the vast majority of remaining cases.
For federated users messaging people outside your organization, remember that external access requires proper configuration at both the organizational and individual user levels. Don’t hesitate to involve your IT department when dealing with federation issues, as they can verify organizational settings that individual users cannot access.
Regular maintenance—clearing your Teams cache periodically and keeping the app updated—prevents most messaging issues before they start. By following the steps in this guide, you should be able to resolve your Teams messaging issues and get back to smooth communication with your colleagues. For more Teams troubleshooting tips, check out our guide on why Teams keeps switching to away status or visit Microsoft’s official Teams troubleshooting page for additional support.
Have you tried these solutions? Let us know which one worked for you in the comments below!
