Counting premium messages in triggering a bot from an external web app to send notifications to Teams Users

Baaridun Nasr 0 Reputation points
2024-02-13T12:44:52.43+00:00

User's image

Currently I am doing some testing and development work on the free tier.

Here I have an external web app, from which I want to trigger a teams bot hosted on Azure Bot Service to send a message to Users who have installed the bot. I will be triggering via a POST request with message content designated for each user.

The message consists of simple text once every 4 hours, but I am making just 1 POST request to the Bot, so does this count against 1 direct line message on premium channel? Or does it count as N direct line messages to all Microsoft Teams users?

Also where does one see the total premium messages sent and received by the bot?

Microsoft Teams | Development
Microsoft Teams | Microsoft Teams for business | Other
{count} votes

1 answer

Sort by: Most helpful
  1. Sayali-MSFT 3,991 Reputation points Microsoft External Staff Moderator
    2024-08-09T11:07:24.0766667+00:00

    @Baaridun Nasr- When you trigger a Teams bot hosted on Azure Bot Service via a POST request from an external web app, the message count on a premium channel is calculated based on the number of messages sent to users.

    If you are sending a message to multiple users, each message sent to a user count as a separate message. So, if you send a message to N users, it will count as N direct line messages on the premium channel.

    To see the total premium messages sent and received by the bot, you can use Azure Bot Service's analytics and monitoring tools. Application Insights, which is integrated with Azure Bot Service, provides detailed telemetry and analytics, including message counts. You can access this information through the Azure portal by navigating to the Application Insights resource associated with your bot

    0 comments No 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.