When switching a Virtual Agent app to the Global Policy in MS Teams, connection was lostIssue Customer switched from using their unbranded Test Virtual Agent on MS Teams, with their production branded Virtual Agent. They performed the switch by disabling the test agent and moving it to the restricted policy and moving the production agent to the global policy in MS Teams. After the switch they lost the connection and got no response from the Virtual Agent. CauseAll applications, including disabled applications, need to be in the same global policy. This was confirmed by Microsoft Teams support.ResolutionCustomer added the unbranded Test policy to global. About 15 seconds, the issue was fixed for some non-cached users. And after a few hours, the issue was resolved for all users. The disabled (unbranded) application needed to be in same global policy as the production branded app.