Share via

Question regarding testing a teams bot with different organization, "Unable to post message to user"

Min Soh 0 Reputation points
2024-10-03T00:46:00.6+00:00

I have created a teams bot in my organization, and uploaded it to the teams account belonging to the organization. The bot works perfectly fine by sending messages to all users in the organization after the admin connects the bot and consenting on behalf of the organization. The bot uses the proactive messaging to send out messsages

I tried to create a separate organization to test the bot, I receive an error response "Unable to post message to user" from the proactive messaging endpoint while trying to send messages using proactive messaging to the all users except for the admin that connected the bot.

I would like to understand if the bot can be tested on different organizations? Or it can only work on the organization that created the bot and it will only work when the bot is published to the teams app store for a different organization?

Microsoft Teams Development
Microsoft Teams Development
Microsoft Teams: A Microsoft customizable chat-based workspace.Development: The process of researching, productizing, and refining new or existing technologies.
3,244 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Sayali-MSFT 2,416 Reputation points Microsoft Vendor
    2024-10-03T10:33:14.7266667+00:00

    To test your bot in a different organization without publishing it to the Teams App Store, you need to ensure that the bot's Azure AD App Registration is configured for multi-tenant access. This means that the bot can be used by accounts in any organizational directory, not just the one that created it. Here are the steps:

    Configure Azure AD App Registration for Multi-Tenant Access:

    • In the Azure portal, go to the "App registrations" section and select your bot's app registration.
      • Under "Authentication", set the "Supported account types" to "Accounts in any organizational directory (Any Azure AD directory - Multitenant)".
        • Ensure that the necessary API permissions are granted and admin consent is provided.
    1. Update the Teams App Manifest:
      • Update the manifest for your bot app to ensure it is configured correctly for multi-tenant access.
      • Make sure the "Bot" section includes the correct Microsoft App ID and the necessary permissions.
      Package and Share the Teams App:
      • Download the packaged Teams app manifest file (a .zip file) from the Teams App Studio.
        • Share this .zip file with the admin of the other organization, along with instructions on how to install the app in their Microsoft Teams environment.
        Client-side Installation: 
        - The admin of the other organization can upload the .zip file to their Microsoft Teams environment.

   - Once installed, the bot should be available for use within that organization.

    By following these steps, you can test your bot in different organizations without needing to publish it to the Teams App Store.

    However, if you plan to make the bot widely available to multiple organizations, publishing it to the Teams App Store is a more scalable solution.

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.