Virtual Agent is unresponsive in Teams after the instance is cloned
Import
·
Mar 11, 2022
·
article
Background:
Your instance is successfully integrated with your Azure tenant and VA works on Teams. You clone the instance then integrate again. On Teams connected to the cloned instance, when you type "hi" or "restart" on Virtual Agent, it doesn't respond. The most common issue after a clone is that the Virtual Agent credential is missing or needs to be re-created manually.
Solution:
- Change the current scope to "Conversational Integration with Microsoft Teams"
- Open "Virtual Agent MS Teams Credentials" from connection & credential aliases
- Delete the related record "VA Microsoft Teams"
- Create a new record under credentials
- Choose type of credentials as "VA Microsoft Teams Credentials" and name it "VA Microsoft Teams"
- Choose Authorization Algorithm as "VA Teams Outbound Token"
- Save the record
View original source
https://www.servicenow.com/community/ms-teams-articles/virtual-agent-is-unresponsive-in-teams-after-the-instance-is/ta-p/2314031