Best (or recommended) approach to Integrate 3 SerrviceNow Instances with 1 MS Teams Instance?

[JeremyHoffman]

Back story...We are currently in the process of configuring the Major Incident Management module to be deployed which will replace the custom application we built years ago. We need it to Integrate with MS Teams to initiate and manage the conference bridge during the MI event. Every

In our Test environment, we installed the Pre-published application and followed the steps documented in the the SN Doc here. Everything worked great for the most part. The one failure was we were not able to import the Chat conversation when it was over. Also, when we went to install the Pre-published application we received this error:

We decided to pivot and use the self configured application following the SN Documentation here. Now, we have everything set up but when we "Initiate" the communication task to start the MS Teams meeting, we are receiving this error:

I have engaged SN Support, but they haven't really been able to identify a cause yet. There is a lot of complexity in the self-configured app versus the pre-configured app.  

I am wondering what the best approach is to accomplish a connection for 3 SN instances to 1 MS Teams tenant?

Is the pre-configured app capable of this configuration? If so, how do we get past the error I pasted above? If not, any ideas what may be causing the above error when trying to initiate the teams meeting using the self-configured app?

I know there are a lot of configuration settings I am not including, for a reason, however, if there are some ideas on focus areas I am more than happy to share that information to help.

Thank you in advance!

Jeremy

[JeremyHoffman]

Hi @Peter Bodelier and @Phil A ,

Apologies for the delayed response and thank you for the follow ups!

A few weeks ago I met with SN support as a result of a support ticket I submitted. It was shared with me that the preconfigured app only allows for a 1 SN instance to 1 Azure/Teams Tenant. We need to use the self configured app and have different configurations in all 3 of our instances (Dev, Test, and Prod). In Azure/Teams, we will have a Dev, Test, and Prod Bot and Meetings app all with unique App ID's, Bot ID's, etc.

We have been working on finalizing the configuration in our Dev environment and will probably look to move onto Test in the next week or 2 (Before Christmas). So it will be interesting to see if we run into the same scenario @Phil A mentions. However, we are not using this in VA yet, only Major Incidents (Incident Communication Tasks).

They also shared with us that we would need to look at the Clone Preservers and Exclusions and ensure that the settings are not overwritten when we clone prod over the sub prod instance. 

These are the 2 sets of documents I followed to configure our Dev environment:

Integrate Notify connector self-configured app with Microsoft Teams (servicenow.com)

Integrate Meeting Extensions self-configured app with Microsoft Teams (servicenow.com)