What are the downside of using public service URL in Microsoft Teams Integration

Vaibhav Kinger 0 Reputation points
2024-09-23T11:42:21.17+00:00

I'm integrating Microsoft teams to send message to users as an App using bot framework.

Currently, I need service url for sending messages but in my design, I can't use webhook.

Therefore I'm planning to use public service url (https://smba.trafficmanager.net/teams).
Are there any security or latency concern If I use this public service URL?

Microsoft Teams
Microsoft Teams
A Microsoft customizable chat-based workspace.
10,039 questions
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,230 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Prasad-MSFT 6,686 Reputation points Microsoft Vendor
    2024-09-24T06:28:03.1933333+00:00

    Using the public service URL https://smba.trafficmanager.net/teams for sending messages in Microsoft Teams via the bot framework is a common approach. When a user sends a message to your bot, the incoming request contains an Activity object with a serviceUrl property that specifies the endpoint to which your bot should send its response.
    https://video2.skills-academy.com/en-us/azure/bot-service/rest-api/bot-framework-rest-connector-api-reference?view=azure-bot-service-4.0#base-uri

    While using the public service URL is generally reliable, there can be occasional latency issues. These might be due to network conditions or the load on the traffic manager. Public URLs can expose sensitive data or endpoints to unauthorized access, making them vulnerable to attacks or data breaches.

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.