Fix Teams Bot Does Not Respond on Teams for the Web

When you use Teams for the Web, a bot may stop responding to your messages. The chat shows your message but no reply ever arrives. This usually happens because the browser blocks third-party cookies or because the bot needs a fresh sign-in. This article explains the root causes and gives you step-by-step fixes to get the bot working again.

The most common cause is that Teams for the Web relies on cookies to keep the bot session alive. When your browser blocks these cookies, the bot cannot see your messages. Another cause is an outdated app manifest that the bot uses. This article covers both scenarios and shows you how to resolve them.

Why the Teams Bot Does Not Respond in the Browser

Teams for the Web is a browser-based client that communicates with the Teams backend through REST APIs. Bots are separate services that receive messages through a webhook. When you send a message in a chat, the Teams client forwards it to the bot’s endpoint. The bot then processes the message and sends a reply back.

For this round trip to work, the browser must maintain a session with the Teams service. This session uses cookies to store authentication tokens and conversation state. If the browser blocks third-party cookies, the session breaks. The bot may still receive the message, but the reply cannot be delivered back to your chat window.

Another common cause is an expired access token. Bots often use tokens to call Microsoft Graph APIs. When the token expires, the bot cannot read the message content or send a reply. The bot may log an error but show nothing to the user.

A less frequent cause is a misconfigured bot manifest. The manifest defines the bot’s permissions and scopes. If the manifest lacks the message.read permission, the bot cannot see the message text. This is rare because most bots are tested before deployment.

Steps to Diagnose and Fix the Bot on Teams for the Web

Follow these steps in order. After each step, test the bot by sending a message in the chat. Stop when the bot responds.

1. Check the browser console for errors
   Press F12 to open the developer tools. Go to the Console tab. Look for red errors that mention 401, 403, or token. A 401 error means the authentication token expired. A 403 error means the bot lacks permission. Write down the exact error message. This tells you which fix to apply next.
2. Allow third-party cookies for the Teams domain
   In your browser settings, find the cookie section. Add teams.microsoft.com and all subdomains to the allow list. For example, in Chrome go to Settings > Privacy and security > Cookies and site data. Click Add and enter the domain. In Edge, go to Settings > Cookies and site permissions. In Firefox, go to Options > Privacy & Security and use the Manage Exceptions button. After adding the domain, refresh Teams for the Web and try the bot again.
3. Sign out and sign back in to Teams
   Click your profile picture in the top right corner. Select Sign out. Close the browser tab. Open a new tab and go to teams.microsoft.com. Sign in with your work or school account. This refreshes your authentication token and clears any corrupted session state. Test the bot after signing back in.
4. Clear the browser cache and site data
   Go to your browser history and clear cached images and files. In Chrome, press Ctrl+Shift+Delete. Select Cached images and files and Cookies and other site data. Set the time range to All time. Click Clear data. In Edge, press Ctrl+Shift+Delete and select the same options. In Firefox, press Ctrl+Shift+Delete and choose Everything. After clearing, reload Teams and sign in again.
5. Verify the bot’s permissions in the Teams admin center
   Open the Teams admin center at admin.teams.microsoft.com. Go to Teams apps > Manage apps. Search for the bot app by name. Select the app and go to Permissions. Check that the bot has the Microsoft Graph permission for ChatMessage.Read and ChatMessage.Send. If the permissions are missing, click Edit and add them. Save the changes and wait 10 minutes for the update to propagate.
6. Check the bot’s endpoint URL
   If you own the bot, go to your bot registration in the Azure portal. Under Settings, verify the Messaging endpoint URL is correct. The URL must be publicly accessible and use HTTPS. If the URL is wrong, update it and save. Then restart the bot service.
7. Use the desktop app as a test
   Open the Teams desktop app and send a message to the same bot. If the bot responds in the desktop app but not in the browser, the issue is browser-specific. If the bot does not respond in either client, the problem is with the bot itself, not Teams for the Web.

If the Bot Still Does Not Respond

Teams for the Web Shows a Blank Chat Window

A blank chat window often means the web client failed to load the bot’s adaptive card. This can happen when the bot returns a card format that the browser cannot render. Try switching to the classic Teams chat view by clicking the ellipsis menu in the chat header and selecting Reload. If the window remains blank, use the desktop app instead.

Bot Replies Only Once Then Goes Silent

This pattern indicates a token expiry. The bot’s access token lasts about 60 minutes. If the bot does not refresh the token, it stops responding after the first hour. The fix is to ensure the bot uses the Microsoft Authentication Library to refresh tokens automatically. If you do not own the bot, contact your IT admin to report the issue.

Bot Works in Private Chat but Not in a Channel

Bots that are not added to the team cannot respond in channel conversations. The bot must be installed to the team. In the channel, click the plus icon to add a tab and select the bot. Alternatively, ask a team owner to install the bot by going to Apps and selecting the bot, then choosing Add to a team.

Browser Extensions Interfere with the Bot

Ad blockers and privacy extensions can block the bot’s webhook requests. Temporarily disable all extensions and reload Teams. If the bot responds, enable extensions one by one to find the culprit. Then add an exception for teams.microsoft.com in that extension.

Teams for the Web vs Teams Desktop App for Bot Support

Item	Teams for the Web	Teams Desktop App
Cookie dependency	Requires third-party cookies enabled	Uses native session storage
Token refresh	Depends on browser session	Handled by the app automatically
Browser extensions	Can block bot requests	No extension interference
Performance with large bots	May lag with heavy adaptive cards	Better performance
When to use	Quick access on any computer	Full functionality and reliability

The web version is convenient but has more failure points. The desktop app is more reliable for bot interactions. If you depend on a bot for daily work, consider installing the desktop app.

After applying the fixes above, you should be able to send messages to the bot and receive replies in Teams for the Web. Start by allowing third-party cookies and checking the browser console for errors. If the problem persists, verify the bot’s permissions and endpoint URL. For advanced troubleshooting, use the desktop app to isolate whether the issue is browser-specific. Remember to clear your cache after any policy change in the admin center.