Does serviceURL change or remain the same ? And What is pattern of serviceURL generation ?

Meet Rathod 5

According our bot use case we have to store user details like userId, tenantId, conversationID and serviceURL into our database while bot configuration. As per my findings I could see that serviceURL are changing as per region. While looking into Bot SDK v3 documentation and forums question answer I got to know that serviceURL is not stale and it may change in future. We are using Bot sdk v4 while developing our bot but I see that in Bot SDK v3 document clearly mention that serviceURL are not stale and your bot must verify serviceURL every time user message received but in Sdk Bot v4 documentation I can't find anything written about serviceURL. Our bot is sending proactively message to user once bot configuration happens. so there is no way we can able to update serviceURL after user configure our bot.

I also see in bots docs that if we are not receiving serviceURL from message activity context we can use global serviceURL endpoints to send message to our bot. interestingly, I can able to send message to public user using GCC serviceURL endpoint.

Questions:

Is the serviceURL received from the user activity context determined by the tenant region or the region from which the user sent the messages, essentially reflecting the user’s network region?
If the serviceURL isn't stale, how can we update it in our scenario? Given that we're building a proactive messaging bot and user interactions only occur once during bot configuration.
Can we directly utilize the global serviceURL to send messages to our users without storing the user message activity context serviceURL in our database?
Is there a way to determine the user's tenant type (public, GCC, GCCH, or DoD) from the message activity context or through any another method?

Azar 22,870 Reputation points MVP

2024-04-04T11:42:13.26+00:00
Hey there Meet Rathod

Thats a good question and thanks for using QandA platform,

And answering the questions.

The serviceURL received from the user activity context is determined by the tenant's region. It reflects the region where the tenant's resources are hosted.

If the serviceURL isn't stale, but your bot needs to send proactive messages and interactions only occur once during bot configuration, you can consider storing the serviceURL at the time of bot configuration and periodically verifying it. You might implement a background process that periodically checks the validity of the stored serviceURL and updates it if necessary.

Yes, you can utilize the global serviceURL to send messages to your users without storing the user's message activity context serviceURL in your database. The global serviceURL endpoints are designed for this purpose, allowing you to send messages to users across different regions without needing to know their specific serviceURL.

Unfortunately, there is currently no direct method to determine the user's tenant type (public, GCC, GCCH, or DoD) from the message activity context. but, you may be able to infer the tenant type based on other information available in the message activity context, such as the tenant's domain or specific properties provided by the messaging platform.

If this helps kindly acce[pt the answer thanks much.
Meet Rathod 5 Reputation points

2024-04-04T11:52:22.23+00:00

Thanks for answer. @Azar Is there currently any limitation in using global serviceURL ?
Azar 22,870 Reputation points MVP

2024-04-04T11:56:14.8266667+00:00

Hi again, im not sure about any major limitations,

But hhe global serviceURL may not offer the same level of performance as region-specific serviceURLs. Messages sent through the global serviceURL may experience slightly higher latency comparitevly.

Dont forget to mark the answer accepted if it helped thanks again.
Meet Rathod 5 Reputation points

2024-04-04T12:18:36.7866667+00:00

currently, I am able to send message to public user using GCC serviceURL endpoint. Do you know anything about this ? Is that some kind of feature or it's bug ?
Azar 22,870 Reputation points MVP

2024-04-05T13:03:59.82+00:00

Hi there

Checking if this helped, kindly accept the answer if it did thanks much.
Vikram Boorla (Tata Consultancy Services Limi) 250 Reputation points Microsoft Vendor

2024-04-17T07:59:53.0266667+00:00

Hello Meet Rathod
Could you please let us know whether your issue has got resolved?
Meet Rathod 5 Reputation points

2024-04-17T08:48:44.16+00:00

@Vikram Boorla (Tata Consultancy Services Limi) I got most of my question answer from azar. only one question answer I have not received is that I am able to send message to public user using GCC serviceURL endpoint. Do you know anything about this ? Is that some kind of feature or it's bug ?
Vikram Boorla (Tata Consultancy Services Limi) 250 Reputation points Microsoft Vendor

2024-04-30T11:55:13.8766667+00:00

Hello @Meet Rathod
Using the global serviceURL to send messages to users across different regions without needing to know their specific serviceURL is a feature designed for this purpose. This allows messages to be sent to users in government cloud environments, including GCC, using the appropriate endpoints.

Share via

Does serviceURL change or remain the same ? And What is pattern of serviceURL generation ?

Your answer