Fix Teams Bot Does Not Respond in a New Teams Client

Your Teams bot stops responding after you switch to the new Teams client. The bot shows as online but never replies to messages or commands. This often happens because the new Teams client uses a different runtime and permissions model. This article explains why bots fail in the new client and gives you step-by-step fixes for the most common causes.

Why a Teams Bot Stops Responding in the New Teams Client

The new Teams client, released in 2023, is built on a different web technology stack than the classic client. It runs in a Chromium-based shell and uses a newer version of the Teams JavaScript SDK. Bots that were built for the classic client may not work correctly in the new client because of these changes.

The most common technical reason is a mismatch in the bot’s messaging endpoint. The new client sends requests using a different user agent and may require the bot to support HTTPS and the latest Bot Framework protocol version. If the bot’s endpoint is not updated, the new client cannot authenticate the request, and the bot never receives the message.

Another frequent cause is a policy or app permission issue. The new Teams client enforces app permission policies more strictly. If the bot is not allowed by your org’s permission policy, it will appear in the app list but will not respond when you chat with it.

Finally, the bot may be blocked by an app governance rule. In the new Teams admin center, you can set apps to be blocked for security reasons. A blocked bot will not process any messages.

Steps to Diagnose and Fix a Non-Responding Bot in the New Teams Client

Follow these steps in order. Each step addresses a specific cause. Test the bot after each step to see if the problem is resolved.

1. Check the bot’s app status in the admin center
   Go to the Teams admin center at admin.teams.microsoft.com. Select Teams apps > Manage apps. Search for the bot’s name. Check the Status column. If the status is Blocked, click on the app name, then click Publish or Allow to unblock it. If the status is Pending update, approve the update to ensure the bot uses the latest code.
2. Verify the app permission policy
   In the Teams admin center, go to Teams apps > Permission policies. Select the policy that applies to your users. Under Microsoft Apps, ensure the bot is set to Allowed. If it is set to Blocked, change it to Allowed and save. Wait 30 minutes for the policy to propagate.
3. Test the bot with the diagnostics shortcut
   In the new Teams client, press Ctrl+Shift+K to open the meeting diagnostics panel. Type the bot’s name in the search box. The panel will show whether the bot is reachable and if there are any connection errors. If the panel shows a network error, proceed to the next step.
4. Clear the Teams client cache
   Close Teams. Press Ctrl+R on your keyboard to reload the client. If that does not work, clear the cache manually. Press Ctrl+Shift+Esc to open Task Manager, end all Teams processes, then delete the cache folder at %appdata%\Microsoft\Teams. Restart Teams and try the bot again.
5. Reinstall the bot from the app store
   In the new Teams client, go to Apps on the left sidebar. Search for the bot. Click the bot’s icon, then click Remove. After removal, click Add to reinstall it. This resets the bot’s local configuration.
6. Check the bot’s endpoint with a web browser
   If you have access to the bot’s source code, open the bot’s endpoint URL in a browser. The URL is usually in the bot’s registration in Azure. If the endpoint returns a 404 or an SSL error, the bot is not running correctly. Update the endpoint to use HTTPS and ensure the Bot Framework protocol version is v3 or later.

If the Bot Still Does Not Respond After the Main Fix

Teams Bot Shows as Offline Even Though It Is Online

This usually happens when the bot’s presence is not synced with the new client. Go to the bot’s chat window and type /status. If the bot replies with a status message, the bot is working. If not, the bot may be down. Check the bot’s hosting service, such as Azure App Service, to see if it is running.

Teams Bot Only Works in Classic Teams, Not in New Teams

This indicates a compatibility issue with the Teams JavaScript SDK. The bot must be updated to use the latest version of the SDK. If you do not own the bot, contact the bot developer. As a workaround, you can switch back to classic Teams temporarily by clicking the toggle in the top-left corner of the new client.

Teams Bot Does Not Respond to Commands but Responds to Messages

This is often caused by a malformed command definition. The bot’s manifest file may have incorrect command IDs. Request the bot developer to check the manifest and ensure each command has a unique ID and the correct scope. In the new client, you can also try typing the command with a leading slash, such as /help.

New Teams Client vs Classic Teams for Bot Compatibility

Item	New Teams Client	Classic Teams Client
Runtime	Chromium-based shell	Electron-based shell
JavaScript SDK version	Requires SDK v1.13 or later	Works with SDK v1.12 or earlier
App permission enforcement	Stricter, with automatic blocking	More lenient, manual policy
Cache location	%appdata%\Microsoft\Teams	%appdata%\Microsoft\Teams
Diagnostics shortcut	Ctrl+Shift+K	Ctrl+Shift+K

The table shows that the main difference is the SDK version requirement. If your bot was built for the classic client, it may not meet the new client’s requirements. Update the bot to the latest SDK to ensure compatibility.

You can now diagnose why your bot is not responding in the new Teams client. The fixes range from checking admin policies to clearing the cache. Start with the admin center checks because they are the most common cause. If the bot still fails, update its SDK or contact the developer. Use the Ctrl+Shift+K diagnostics to quickly test connectivity after each change.