How to exclude ITSM Integration with Microsoft Team from cloning the production instance to sub prod

[G Sai Vamshi]

Hello All,

We are planning to clone the production instance to sub production instances , we are having itsm integration with microsoft teams. We have our sub prod to connected with Teams Dev Tenant. Prod to Teams Prod Tenant. By cloning the prod to sub prod , we dont want to disturb the existing integration with teams dev tenant. 

Please let me know what to exclude while cloning.

[Vasantharajan N]

Please make sure you exclude the table where you stored the MS Teams configuration, from system clone, by adding the table in the Exclude table list.

Refer the documentation link below,

https://docs.servicenow.com/en-US/bundle/sandiego-platform-administration/page/administer/managing-data/task/t_ExcludeATableFromCloning.html

[G Sai Vamshi]

Hi Vasantha, thanks for response,

I am not sure on the tables to exclude, I am looking for table name which needs to be excluded.

[Fu]

There are 3 tables that store Azure and VA infos: 

• sn_now_azure_installed_tenant
• sn_now_azure_installed_app
• sys_cs_provider_application

However, there are a number of other configs that might contain tenant info that is not on those tables. The easiest I've found is to clone prod to dev "as-is" then delete the records on those 3 tables, then reinstall using credentials from the dev tenant. 

[Niclas]

Try to upgrade "Conversational Integrations with MS Teams" to Version 4.0.1 that was released on November 3rd. As of the Release Notes in ServiceNow Store it should cloning issues: