Bot Framework serviceUrl

Viewed 453

I am developing a Notification Only bot to enable proactive Teams notifications.

As far as I am aware it is necessary to store the ServiceUrl from an incoming message to the bot endpoint. I have read that it is also possible that service Url can change in the future (although unlikely) and that if this happens the serviceUrl should be updated and used for future messages.

Using a test O365 instance in UK region I see the following behaviour:

When I add member to team or install the app to a team, the service Url comes through as: https://smba.trafficmanager.net/uk/

When I remove a member from team or remove the app from team, the service Url comes through as: https://smba.trafficmanager.net/emea/

If our service tries to send a notification via the rest api, using the /emea ServiceUrl it returns a 403 Forbidden

Doing the same using an O365 instance in US region the service Url is allways: https://smba.trafficmanager.net/amer/

Is this expected behaviour or a bug?

Are there any rules on when the Service Url should be updated and when it should not?

Many Thanks.

0 Answers
Related