Skip to main content
All CollectionsStanduply's key features explainedMS Teams
Troubleshooting bot accessibility issues in Microsoft Teams
Troubleshooting bot accessibility issues in Microsoft Teams

How to resolve issues with Standuply not sending messages to respondents in Microsoft Teams

Vlad Zhigulin avatar
Written by Vlad Zhigulin
Updated this week

If you encounter issues with our bot not sending messages or responding as expected in Microsoft Teams, the problem is likely related to app permissions or administrative settings within your tenant.


Common Causes of Bot Inaccessibility

  1. Restricted Bot Permissions
    Microsoft Teams allows admins to control which users or groups have access to specific apps. If the bot is disabled or restricted, it may fail to send notifications or respond.

  2. Legacy Policies
    Some enterprise users may still use legacy policies that explicitly block or allow apps. These settings can inadvertently prevent the bot from functioning correctly if they are not updated.

  3. Org-Wide App Settings
    The "Org-wide app settings" in the Teams Admin Center include options to enable or disable apps at the organizational level. Misconfigured settings here can also block bot access.

  4. Blocked Apps by Policy
    Microsoft Teams app policies may block certain apps entirely. These policies can override individual user or group permissions.

For detailed information, you can refer to the following official Microsoft articles:


Steps to Troubleshoot and Resolve

1. Verify Bot Permissions

Ensure the bot is not restricted to specific users or groups. To check:

  • Navigate to the Teams Admin Center.

  • Go to Manage Apps.

  • Verify that the bot is listed and enabled for all required users or groups.

2. Check Org-Wide App Settings

The "Org-wide app settings" might restrict app functionality organization-wide. To verify:

  • In the Teams Admin Center, click on Actions in the top-right corner.

  • Select Org-wide app settings.

  • Ensure the appropriate checkbox for app availability is enabled.

3. Check Legacy Policies

If you’re using legacy app policies, ensure they allow access to the bot. Microsoft is migrating users to a new policy system, but legacy policies may still be in effect for some organizations.

  • Legacy settings may need to be manually updated to reflect current requirements.

  • Work with your IT admin to ensure all app policies align with the new standards.

Did this answer your question?