You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have developed an MS Teams bot app for our customers. But this is developed a few years ago. We support various regions like Europe, Asia, America and Australia. I don't know for what reasons but our developers had developed different teams apps for different regions. But now We want to have a single app instead of many as it's hard to manage. Currently, We have 4 different apps in Azure and 4 different channel registrations.
So what would be the best way to deal with this situation?
I am looking for both short-term and long-term solutions.
I am also looking for an approach with minimal changes and risk.
The text was updated successfully, but these errors were encountered:
@viveknuna -Thank you for your inquiry about your Teams app development issue!
We are evaluating the possibility of merging the four apps into a single application. We will get back to you shortly with an update.
Hello @viveknuna, At the moment, merging the app is not feasible. The Azure Bot Service operates as a global service and does not support region-specific message endpoints. However, to maintain end-to-end data residency, you can deploy your bot code in the same region as your Azure Bot resource.
We have developed an MS Teams bot app for our customers. But this is developed a few years ago. We support various regions like Europe, Asia, America and Australia. I don't know for what reasons but our developers had developed different teams apps for different regions. But now We want to have a single app instead of many as it's hard to manage. Currently, We have 4 different apps in Azure and 4 different channel registrations.
So what would be the best way to deal with this situation?
I am looking for both short-term and long-term solutions.
I am also looking for an approach with minimal changes and risk.
The text was updated successfully, but these errors were encountered: