If you’ve ever opened Microsoft Teams and spotted a red triangle with an exclamation mark — either on the app icon in your taskbar, next to an organization name, or right beside a message you just sent — you’re not alone. This little warning sign trips up a lot of people because it doesn’t always mean the same thing. It depends entirely on where you see it.
In this tutorial, I’ll walk you through every place the Microsoft Teams red triangle exclamation mark can show up, what it means in each case, and exactly how to fix it. No vague advice like “try restarting your computer.” I’ll give you real, specific steps.
What Is the Red Triangle Exclamation Mark in Teams?
The red triangle with an exclamation mark is a universal warning symbol. In Microsoft Teams, it’s used in a few different spots to signal that something needs your attention. The tricky part is that it means different things depending on where it appears:
- On the Teams taskbar icon — usually a sign-in or account authentication issue
- Next to an organization name — indicates you’re not fully signed in to that org, or there’s an account/policy issue
- On a chat message — the message failed to send
- On a message someone sent you — a red exclamation mark with the word IMPORTANT! just means the sender marked it as important
- Next to a contact’s name — can indicate an external user with restricted access
Let me break each one down. If Teams won’t open or load at all, rather than showing a warning, start with this guide on Microsoft Teams not working instead.
Scenario 1: Red Triangle on the Teams Icon in the Taskbar
This is probably the most common one. You glance at your taskbar, and there it is — a red triangle sitting right on top of the Teams icon.
What it means
This almost always means Teams is asking you to sign back in. It could be because:
- A session token has expired
- Multi-factor authentication (MFA) needs to be re-verified
- Your password has changed and Teams hasn’t been updated with the new credentials (here’s how to change your password in Microsoft Teams the right way)
- An IT policy at your organization is requiring re-authentication
- Teams lost its connection to your account in the background
It’s not a virus, it’s not a crash — it’s just Teams saying, “Hey, I need you to log back in.”
How to fix it
Step 1 — Click the icon first
Before doing anything else, just click the Teams icon in the taskbar. Teams will often pop up a sign-in prompt automatically. Go through the sign-in flow, including any MFA step if required, and the red triangle should disappear.
Inside the app, you’ll usually also see a red banner that says We need you to sign in again. Microsoft says that until you sign in, Teams blocks new chats and calls, meetings, and other features. Select the banner or its sign-in button, then enter your credentials and finish any MFA prompt. If there’s no sign-in button, look for the Teams icon with a red dot or exclamation mark in the system tray near the clock and select it.
Step 2 — Sign out and sign back in manually
If clicking doesn’t trigger a prompt:
- Open Teams
- Click your profile picture in the top-right corner
- Select Sign out
- Close Teams completely (right-click the Teams icon in the system tray → Quit)
- Reopen Teams and sign in fresh

Step 3 — Check for pending MFA
If your organization uses Microsoft Authenticator or SMS-based verification, check your phone. Sometimes Teams is silently waiting for you to approve an MFA request that you missed. Approve it, and the triangle often clears on its own.
Step 4 — Use Teams on the web to verify
Go to teams.microsoft.com in your browser. If you can sign in there without any issues, the problem is specific to the desktop app — not your account. That tells you the desktop app just needs a refresh.
Scenario 2: Red Triangle Next to an Organization Name
If you work across multiple Microsoft 365 tenants — for example, you’re a member of your company’s Teams environment and also a guest in a client’s Teams — you might see a red triangle or red exclamation mark sitting right next to one of the organization names in your account switcher.
What it means
This almost always means you’re not actively authenticated in that organization. Guest access in Teams requires you to be signed in to each tenant separately. If your session has expired for one of them, Teams flags it with that red triangle.
It can also mean:
- That organization has a conditional access policy requiring re-authentication at certain intervals
- The guest account has been modified or restricted by that org’s admin
- There’s a licensing issue with the guest account
How to fix it
Step 1 — Switch to that organization
Select your profile picture at the top right of Teams and choose the organization with the warning. Teams will take you to that org’s context and likely prompt you to sign in or verify via MFA.
Step 2 — Accept the sign-in prompt
Complete the sign-in, including any multi-factor authentication step. Once you’re authenticated, the red triangle next to that org should go away.
If the warning points to a licensing problem in your own organization, open Settings and more (…) > Settings > Accounts and orgs and select the Refresh license and restart button next to your account. Juggling several work accounts? This guide shows how to add multiple accounts on Microsoft Teams and switch between them.

Step 3 — If you don’t use that org anymore
If it’s an old organization you no longer work with, you can quiet it or leave it:
- Go to Settings and more (…) → Settings → Accounts and orgs
- Find the organization with the red triangle and turn off its toggle so it stops sending you notifications
- To leave it for good, sign in at myaccount.microsoft.com, select Organizations, and choose Leave next to that organization (some organizations don’t allow this, and then their admin has to remove you)
Leaving an external organization won’t delete your own work account. It only ends your guest access there, so Teams stops trying to keep you authenticated in that org.
Scenario 3: Red Triangle on a Chat Message (Failed to Send)
This one is immediately obvious and pretty frustrating. You type a message, hit send, and instead of the usual sent/delivered checkmark, you see a red triangle with an exclamation mark right next to your message, along with text that says “Failed to send.”
What it means
Your message didn’t go through. This can happen because of:
- A network blip — your internet dropped for a second right as you hit send
- Teams service issues — Microsoft’s backend servers were briefly unavailable
- Messaging to an external user — the other person’s organization may have restrictions on external communication
- Group chat configuration issues — certain group settings can block messages from going through
- Session timeout — Teams may have lost your authenticated session in the background
How to fix it
Step 1 — Try resending the message
Click the red triangle or the Retry option next to the failed message. Often, it’s just a one-second network hiccup and a retry is all it takes.
Step 2 — Check your internet connection
- Make sure you’re still connected to the internet
- Try opening a website in your browser to confirm
- If you’re on Wi-Fi, try switching to a wired connection or toggling Wi-Fi off and back on
Step 3 — Check Microsoft’s service health
Sometimes the problem isn’t on your end at all. Microsoft occasionally has service disruptions that affect Teams messaging.
- If you’re an admin, open the Microsoft 365 admin center and go to Health → Service health
- Or check Microsoft’s public Service Health Status page at status.cloud.microsoft to see if Teams is experiencing a big incident

If there’s an active incident, just wait it out. It usually resolves within minutes to a couple of hours.
Step 4 — Check if you’re messaging an external user
If you’re trying to send a message to someone outside your organization and you’re getting the “Failed to send” error consistently (not just once), there may be a policy blocking external chat. Things to check:
- Ask your IT admin whether external communication is allowed for your account
- Try messaging a colleague within your own org to confirm the issue is only with external contacts
- The other person’s organization may have completely disabled external messaging
If you’re still setting up that contact, here’s how to add someone on Microsoft Teams outside your organization so chats with them work.
Step 5 — Clear Teams cache
A corrupted cache can sometimes cause persistent sending failures. Here’s how to clear it:
- Quit Teams completely (right-click the taskbar icon → Quit)
- Press Windows + R, type
%userprofile%\appdata\local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams, and press Enter (that’s the new Teams folder; classic Teams used%appdata%\Microsoft\Teams) - Delete everything inside that MSTeams folder (leave the folder itself)
- Restart Teams and try sending again
For Mac users on new Teams, quit Teams and delete the contents of ~/Library/Group Containers/UBF8T346G9.com.microsoft.teams and ~/Library/Containers/com.microsoft.teams2. For screenshots of every step, follow this guide to clear Microsoft Teams cache.
Step 6 — Sign out and back in
If clearing cache doesn’t work:
- Click your profile picture → Sign out
- Completely quit Teams
- Reopen and sign back in
- Try sending the message again
Step 7 — Use Teams on the web
Open teams.microsoft.com in your browser and try sending the message from there. If it works on the web but not the desktop app, the issue is isolated to the app. In that case, reinstalling Teams is your best next step. And if older messages are missing rather than failing, see what to do when your Microsoft Teams chat is not showing.
Scenario 4: Red Exclamation Mark Next to a Contact’s Name
Sometimes you’ll notice a red exclamation mark sitting right next to someone’s name in a chat or when you’re composing a message. This is slightly different from the triangle on a message.
What it means
This typically signals one of the following:
- The contact is an external user and there are delivery concerns or access restrictions
- There’s a question about whether the message will actually reach them (common when composing emails in Outlook but can appear in Teams for external contacts)
- The contact’s account has been flagged by your organization’s security policies
If you can still send the message and it goes through fine, the red marker might just be a visual indicator that the person is outside your organization — not necessarily an error.
Red Exclamation Mark on a Message You Received (Important)
Not every red exclamation mark is an error. If a message in a chat or channel shows a red exclamation mark and the word IMPORTANT!, the sender marked it as important. Nothing is broken, and there’s nothing to fix.
You can do the same with your own messages. In new Teams on the desktop or web:
- Type your message in the compose box.
- Select Actions and apps (+) → Set delivery options.
- Choose Important, then send the message.
- To remove the label later, edit the message, go back to Set delivery options, and pick Standard.
There’s also an Urgent option. Microsoft says an urgent message notifies the person every 2 minutes for 20 minutes or until they read it. Urgent isn’t available in channels or in group chats with more than 20 people. If you just want to know whether someone saw your message, read receipts tell you that, and here’s how to turn off read receipts in Microsoft Teams if you’d rather not share yours.
How to Prevent the Red Triangle from Coming Back
Once you’ve fixed it, here are a few habits that help keep the red triangle away:
- Stay signed in across all your organizations. If you’re part of multiple Teams tenants, make sure you authenticate each one regularly, especially after long weekends or holidays.
- Keep Teams updated. New Teams updates itself in the background. When an update is ready, a banner appears at the top; select Update → Update and restart Teams. You can check your version under Settings and more (…) → Settings → About Teams. Running an outdated version causes all sorts of random issues.
- Don’t ignore MFA prompts. If your phone shows an Authenticator notification, approve it promptly. Letting them time out can cause your session to fail.
- Restart Teams once a week. This clears temporary session issues before they snowball.
- Check your org’s IT policies. If the red triangle keeps coming back despite everything, your IT admin may have a conditional access policy that forces re-authentication on a schedule. That’s by design — check with them.

When to Contact IT Support
If you’ve gone through all the steps above and the red triangle is still there — or your messages keep failing — it’s time to loop in your IT department. Some things they can check that you can’t do yourself:
- Whether your account has a licensing issue
- Whether conditional access policies are blocking your session
- Whether there’s a service-side issue specific to your tenant
- Whether an external organization has restricted communication with your domain
Quick Reference: Red Triangle Locations and Meanings
| Where You See It | What It Usually Means | Quick Fix |
|---|---|---|
| Teams taskbar icon | Sign-in or MFA required | Click icon, complete sign-in |
| Next to org name | Not authenticated in that org | Switch to org, sign in |
| Next to a message | Message failed to send | Retry, check internet/cache |
| On a message you received, with IMPORTANT! | Sender marked it as important | Nothing to fix |
| Next to a contact name | External user access issue | Check policies, contact IT |
The red triangle in Microsoft Teams almost always has a straightforward fix once you know what’s causing it. Nine times out of ten, it’s an authentication issue or a temporary network problem — nothing serious. Work through the steps for whichever scenario matches what you’re seeing and you’ll usually have it sorted in under five minutes.
Frequently Asked Questions
What does the red triangle on the Teams icon mean?
It almost always means Teams needs you to sign in again, for example after a password change or an expired session. Select the icon or the We need you to sign in again banner and complete the sign-in, including any MFA prompt.
Why does my Teams message say Failed to send?
The message didn’t reach Teams, usually because your connection dropped, Teams lost your session, or a policy blocks chat with that person. Retry it, check your internet connection, and sign out and back in if it keeps failing.
Is a red exclamation mark on a message always an error?
No. A red exclamation mark with the word IMPORTANT! means the sender marked the message as important with Set delivery options. Microsoft explains how in Mark a message as important in Microsoft Teams.
How do I remove an organization with a red triangle from Teams?
Turn off its toggle in Settings > Accounts and orgs to stop its notifications. To leave the organization, go to myaccount.microsoft.com > Organizations and select Leave; if the organization doesn’t allow it, ask its admin to remove you.
Does clearing the Teams cache delete my messages?
No. Your chats and files are stored in Microsoft 365, not on your PC. Clearing the cache only removes local app data, and Teams rebuilds it the next time it starts.
If you’re still tidying up Teams after fixing the warning, these guides are worth a look:
- Wondering what the status dots mean? See Microsoft Teams last seen vs offline.
- Blocked by a device policy instead? Fix your organization has disabled this device.
- Teams slowing down your PC? Here’s why Microsoft Teams is using a lot of memory.
- Want to tune the app while you’re at it? Walk through the Microsoft Teams settings that matter most.

Hey! I’m Bijay Kumar, founder of SPGuides.com and a Microsoft Business Applications MVP (Power Automate, Power Apps). I launched this site in 2020 because I truly enjoy working with SharePoint, Power Platform, and SharePoint Framework (SPFx), and wanted to share that passion through step-by-step tutorials, guides, and training videos. My mission is to help you learn these technologies so you can utilize SharePoint, enhance productivity, and potentially build business solutions along the way.