Forum Discussion

dfo222's avatar
dfo222
Brass Contributor
Feb 15, 2021

Deep links to channel tabs stop working

We have a custom app that can install channel tabs and channel connectors in MS Teams. We then send connector messages to the to the Teams channels, deep linking to the channel tab.

We have been having problems with these deep links with one of our clients. They work as expected in our tenant  and in other client's tenants.

When first setup the links in the connector messages link to the tabs without any problems. But then in the following days the links stop working. Not all channels stop working at the same time, but may be separated by a day or so.

This does not only affect new connector messages, but links in old messages, that used to work will stop working.
We have tried uninstalling and reinstalling the app, connectors and tabs multiple times. With the same results each time.
 
Does anyone have any suggestions why this may be?
 
Here is an example of a deep link that we use.
 
https://teams.microsoft.com/l/entity/<appId>/<entityId>?webUrl=<entityWebUrl>&context=<context>&tenantId=<tennantId>
https://teams.microsoft.com/l/entity/********/***?webUrl=https%3A%2F%2F*******&context=%7B%22subEntityId%22%3A%22%22%2C%22channelId%22%3A%22*******%22%7D&tenantId=*****
 
We understand that the tenantId is not required, as they are not used across tenants (in the context of connector messages), but we use the same link in emails. Where clients use more than one tenant it ensures they are directed to the correct tenant where the tab is located.

7 Replies

  • dfo222 - Is your app is accessible by multiple tenants? When the clients are using that link are they part of that team/channel? Could you please share more info?

     

    • dfo222's avatar
      dfo222
      Brass Contributor

      Nikitha-MSFT, thanks for looking at this. The app is unique to each programme that we run using it for, so we generate a new version for each client. The uniqueness is only about ids and urls, not about functionality. The scope of the app and connector is limited to 'teams', so the user has to be a member of the team/private channel to use it. The user could be a guest in the team. Any other information that would be helpful?

      • Nikitha-MSFT's avatar
        Nikitha-MSFT
        Former Employee

        dfo222 - If your app scope is limited to teams, your app will be able to access to other tenant users also, The user may not be part for that team. Could you please check whether the user in other tenant is part of the team where your tab is configured?

Resources