Smart Connect RSC upgrade (2026)

To enable shared chats within Jira, we historically relied on a user-based authentication system, meaning the Microsoft user that created the chat would be the leading entity in relaying chat data to Jira users. This system comes with the drawback of collapsing should the sharing Microsoft user not exist anymore (e.g. left the company). To move forward with the sharing concept and to futureproof it considering latest Microsoft authentication trends, we are adopting the RSC pattern. RSC is the abbreviation for “resource specific consent” and is Microsoft’s way of letting apps (like Smart Connect) access specific resources, like chats. Read more about RSC here.

Starting in January 12, 2026, we are adding certain RSC capabilities to Smart Connect, which affects the way it needs to be installed into Microsoft chats and as such will require an approval by Microsoft admins. If you have approved notifications for Smart Connect in our Jira products within the past 6 months or earlier, you will not have to do this.

To be setup for this future concept, complete the approval flow started from the following URL. If you are not a Microsoft admin for your tenant, send this URL to them:

https://login.microsoftonline.com/organizations/v2.0/adminconsent?client_id=89d5ca9f-d63b-4885-bd30-6e7433c1540c&scope=TeamsAppInstallation.ReadWriteAndConsentForChat%20TeamsTab.Create&redirect_uri=https%3A%2F%2Fatlassianconnect.yasoon.com%2Fv2%2Fjira-teams%2Fsoftware%2Frsc-upgrade-admin-consent-success