Fix Teams Bot Does Not Respond after a Policy Update

When you update a policy in the Teams admin center, a bot that previously worked can stop responding. This often happens because the policy change revokes the bot's permission or changes its routing. You see the bot in the chat list, but it ignores messages or shows an error. This article explains why policy updates break bots and gives you a step-by-step fix to restore responses.

You will learn how to check the affected policy, re-enable the bot, and test it in a controlled way. The fix takes about 15 minutes and does not require coding.

Why a Policy Update Stops a Bot From Responding

Bots in Teams rely on two separate policy layers. The first layer is the messaging policy, which controls whether bots are allowed at all. The second layer is the app permission policy, which decides which specific apps, including bots, a user can install and use. When you update a policy, the change can accidentally disable one of these layers.

A common mistake is editing a global policy that applies to everyone. For example, if you set the "Bots" toggle to Off in a messaging policy, every bot in that policy scope stops responding. The bot does not disappear from the chat, but it cannot send or receive messages.

Another cause is the app permission policy. If you block the Microsoft app category or remove a specific bot app from the allowed list, the bot becomes unavailable. The user might still see the bot in a previous chat, but the bot cannot process new messages.

How Policy Priority Works

Teams applies policies in a specific order. A user gets the policy that is directly assigned to them. If no direct assignment exists, the user inherits the global policy. This means a global policy update can affect many users at once, even if you only intended to change one group.

Where to Check Effective Policies

You can see which policy a user actually has by using the Teams admin center. Go to Teams admin center > Users > select a user > Policies. This shows the effective messaging policy and app permission policy for that user. This is the first place to look when a bot stops responding.

Steps to Diagnose and Fix the Bot After a Policy Update

Follow these steps in order. Each step checks a specific part of the policy chain.

1. Identify the affected user and policy scope
   Open the Teams admin center at admin.teams.microsoft.com. Go to Users, select the user who reports the bot issue, and open the Policies tab. Note the names of the messaging policy and app permission policy that are assigned. Write them down because you will need them later.
2. Check the messaging policy for the bot setting
   In the Teams admin center, go to Messaging policies. Select the policy you noted in step 1. Scroll to the Bots section. Verify that the "Bots" toggle is set to On. If it is Off, switch it to On and click Save. If it is already On, move to the next step.
3. Verify the app permission policy allows the bot
   Go to Teams admin center > App permission policies. Select the policy from step 1. Under Microsoft apps, make sure the toggle is On. Then check the "Allow specific apps" list. If your bot is not listed, click Add apps, search for the bot name, and add it. Click Save.
4. Refresh the Teams client to clear cached policies
   Ask the user to close Teams completely. On Windows, right-click the Teams icon in the system tray and choose Exit. Then reopen Teams. If the problem persists, press Ctrl+F5 while the Teams window is active to force a refresh of the client cache.
5. Test the bot in a private chat
   Send a simple message to the bot, such as "hello". Wait 10 seconds for a response. If the bot replies, the policy fix worked. If not, continue to the next step.
6. Confirm the bot app is installed for the user
   In Teams, go to Apps on the left sidebar. Search for your bot. If it shows "Add", the app is not installed. Click Add, then test the bot again. If the bot is already installed, click the ellipsis (three dots) next to it and choose "Manage" to check for any error messages.
7. Check the bot's service health
   If the bot still does not respond, the problem may be on the bot's server side. Go to the Microsoft 365 admin center at admin.microsoft.com. Select Health > Service health. Look for any incident labeled "Microsoft Teams" or "Bot Framework". If there is an active advisory, wait for resolution and test again later.

If You Need to Roll Back a Policy Change

If you recently changed a policy and want to revert it, open the policy in the Teams admin center and click Restore default. This resets all settings in that policy to the Microsoft default values. After saving, ask the user to restart Teams and test the bot again.

If the Bot Still Has Issues After the Main Fix

Bot responds only sometimes, or with a delay

A delayed response often comes from the bot's backend, not from Teams policies. Check the bot's application logs for timeouts. If you manage the bot, increase the timeout value in the bot's code. If you do not manage the bot, contact the bot vendor.

Bot shows an error message saying "Policy does not allow this action"

This error means the messaging policy still restricts bots. Re-check the messaging policy from step 2. Also check if a group policy assignment overrides the user's direct policy. Go to Teams admin center > Messaging policies > Group policy assignments. Remove any conflicting assignment that blocks bots.

Bot works for some users but not others

This happens when users have different policy assignments. Use the effective policy check from step 1 for each affected user. Compare the two policies. The user who cannot use the bot likely has a policy with Bots turned Off or an app permission policy that blocks the bot app.

Messaging Policy vs App Permission Policy: Key Differences

Item	Messaging Policy	App Permission Policy
Controls bot availability	Yes, via the Bots toggle	No, but controls if the bot app can be installed
Scope	Applies to messages and chat features	Applies to all apps, including bots
Default setting	Bots enabled by default	Microsoft apps allowed by default
Typical fix	Turn Bots to On	Add the bot to the allowed apps list

Both policies must allow the bot for it to respond. If either one blocks the bot, the bot will not work. Always check both when troubleshooting.

After you apply a fix, remember that policy changes can take up to 24 hours to fully propagate, though most updates apply within a few minutes. If the bot still does not respond after an hour, revisit the effective policy check.

For a quick test, use the Teams desktop client with Ctrl+F5 to refresh. This clears cached policy data that may show old settings.