Upgrade considerations for Notify teams conectorDescriptionNotify connector for Microsoft Teams enables you to manage and initiate a Microsoft Teams meeting directly from any record such as an incident, or a task. This KB talks about the install differences in the documentation for version 2.0.2 vs 2.1.2 InstructionsWith the new version of Notify connector for Teams , ServiceNow also changed the product documentation on how to set up the connector.Previously, it was to register the MS Teams App via Application Registry with Client ID, Client Secret etc.This has now been changed Background: Here are the difference between Notify connector 2.0.2 vs 2.1.2 In version 2.0.2 the Paris documentation covered the following steps:1.) Add App Studio in MS Teams2.) Add App in MS Teams3.) Manage Permissions for Notify Connector App4.) Create a MS Teams application registry entry in ServiceNow5.) Create Connection & Credential alias for MS Teams,6.) Set up Notify connector for MS Teams,7.) Configure MS Teams as a Service Provider In version 2.1.2 the steps have been changed to:1.) Connect the ServiceNow instance to your Microsoft Teams tenant2.) Authorise multi-tenant Azure apps to grant required permissions3.) Download manifest file and configure Notify connector for Microsoft Teams app in Microsoft Teams4.) Make Microsoft Teams the default communication channelMake Microsoft Teams the default communication channel to initiate a conference call to resolve a ticket. Question is what happens when we upgrade from version 2.0.2 to 2.1.2. Does it automatically take over the old configurations from 2.0.2 and migrates it to the 2.1.2 way or do we need to set up everything from scratch? Store app DocumentationRelease NotesNew - Added support for Azure Multi-Tenant app. The users can use the BOT shipped by ServiceNow for the Microsoft Teams meeting.Bottom line:After upgrading to 2.1.2, your old configurations should work fine unless you do steps 1 and 2 for 2.1.2( New version) in above note. So, If apps are authorised by Teams app, the configuration will be auto updated to use the authorised app otherwise it will use old configurationSteps in new config should be performed ONLY if you want to utilize the new feature in 2.1.2. If you don't want , old config's should still work after upgrade without any changes