MS teams is not working is not responding after cloning

[ServiceNow10sun]

Hi All , 

After the cloning the MS teams chat bot is not responding. After the clone the Client ID and Tenant ID has been cloned from production instance to stag instance  ,which i have corrected and updated as well the stag instance( updated the Client ID and Tenant ID as how it was before the clone) , however still the chat bot is not responding. 

I have even after the update of the Client ID and Tenant ID downloaded the Manifest file and uploaded into the MS teams application but still the chat bot(Virtual agent) is not responding. 

Any suggestions or anyone has faced similar issue. 

[Sainath N]

@ServiceNow10sun : Along with the credentials, could you also check the endpoints to see if they are pointing correctly?

Please mark this as correct answer and helpful if it resolved, or mark this helpful if this help you to reach towards solution.

[ServiceNow10sun]

End points means you mean Client ID and Tenant ID or Secret ID as apart from this there is no other info which we enter to set up the integration between the MS teams and ServiceNow.

and Client ID , Tenant ID and Secret ID are fine.

[ServiceNow10sun · Accepted solution]

The issue has been resolved.

1. Clean up the cache by running back ground script. 

2. Updating all the Microsoft plugins

3. By reinstalling the Azure apps in ServiceNow.

4. Re authorizing the ServiceNow and MS teams from ServiceNow instance. 

FYI - Reason for the issue is while doing upgrade we should exclude all tables related to Azure apps/ MS teams in SN instance. 

[Aaron Duncan]

Can you share the background script for this?