Smart Connect for Jira

Publisher Attestation: The information on this page is based on a self-assessment report provided by the app developer on the security, compliance, and data handling practices followed by this app. Microsoft makes no guarantees regarding the accuracy of the information.

Last updated by the developer on: July 21, 2021

General information

Information provided by yasoon GmbH to Microsoft:

Information Response
App name Smart Connect for Jira
ID WA200002055
Office 365 clients supported Microsoft Teams
Partner company name yasoon GmbH
URL of partner website
URL of Teams application info page
URL of Privacy Policy
URL of Terms of Use


Questions or updates to any of the information you see here? Contact us!

How the app handles data

This information has been provided by yasoon GmbH about how this app collects and stores organizational data and the control that your organization will have over the data the app collects.

Data access using Microsoft Graph

List any Microsoft Graph permissions this app requires.

Permission Type of permission (Delegated/ Application) Is data collected? Justification for collecting it? Is data stored? Justification for storing it? Azure AD App ID
Channel.ReadBasic.All delegated The permission is used to let the user select one of this joined channels in Jira. Channel ID, for caching purposes 89d5ca9f-d63b-4885-bd30-6e7433c1540c
ChannelMessage.Read.Group application Allows the app to show linked channel messages in Jira. Message IDs for linking messages to Jira issues 89d5ca9f-d63b-4885-bd30-6e7433c1540c
ChannelMessage.Send delegated No data is used, this API is used for letting the user reply to channel messages from Jira. None 89d5ca9f-d63b-4885-bd30-6e7433c1540c
ChannelSettings.Read.Group application Used to lookup detail information about a channel. None 89d5ca9f-d63b-4885-bd30-6e7433c1540c
Chat.ReadWrite delegated Used to allow the user to add new replies to chats and view chat messages from Jira. None 89d5ca9f-d63b-4885-bd30-6e7433c1540c
Member.Read.Group application Used for permission checks, allows the app to validate team membership of users. None 89d5ca9f-d63b-4885-bd30-6e7433c1540c
Team.ReadBasic.All delegated The permission is used to let the user select one of this joined teams in Jira. Team IDs for caching purposes 89d5ca9f-d63b-4885-bd30-6e7433c1540c
TeamSettings.Read.Group application Allows the app to read Team settings to respect certain defaults. None 89d5ca9f-d63b-4885-bd30-6e7433c1540c
User.ReadBasic.All delegated Allows the user to select co-workers to @-mention in a channel message None 89d5ca9f-d63b-4885-bd30-6e7433c1540c

Non-Microsoft services used

If the app transfers or shares organizational data with non-Microsoft service, list the non-Microsoft service the app uses, what data is transferred, and include a justification for why the app needs to transfer this information.

All non-Microsoft services OII is transferred to What OII is transferred? Justification for transferring OII?
Atlassian Jira and possibly one of our contractors, can be seen here: Message metadata (ids, timestamps), user and organizational metadata (user id's, org id's) and user email addresses Supporting the app functionality (e.g. matching Atlassian accounts with Office accounts) and enabling our support to troubleshoot issues faster.

Data access via bots

If this app contains a bot or a messaging extension, it can access end-user identifiable information (EUII): the roster (first name, last name, display name, email address) of any team member in a team or chat it's added to. Does this app make use of this capability?

Justification for accessing EUII? Is EUII stored in database(s)? Justification for storing EUII?
Matching the users Teams account with the users Atlassian Jira account No

Telemetry data

Does any organizational identifiable information (OII) or end-user identifiable information (EUII) appear in this application's telemetry or logs? If yes, describe what data is stored and what are the retention and removal policies?

User metadata (id)

Organizational controls for data stored by partner

Describe how organization's administrators can control their information in partner systems? e.g. deletion, retention, auditing, archiving, end-user policy, etc.

We only work with services that offer strict data privacy guarantees.

Human review of organizational information

Are humans involved in reviewing or analyzing any organizational identifiable information (OII) data that is collected or stored by this app?



Questions or updates to any of the information you see here? Contact us!

Information from the Microsoft Cloud App Security catalog appears below.

View in a new tab


Questions or updates to any of the information you see here? Contact us!

Identity information

This information has been provided by yasoon GmbH about how this app handles authentication, authorization, application registration best practices, and other Identity criteria.

Information Response
Do you integrate with Microsoft Identify Platform (Azure AD)? Yes
Have you reviewed and complied with all applicable best practices outlined in the Microsoft identity platform integration checklist? Yes
Does your app use MSAL (Microsoft Authentication Library) for authentication? Yes
Does your app support Conditional Access policies? No
Does your app request least privilege permissions for your scenario? Yes
Does your app's statically registered permissions accurately reflect the permissions your app will request dynamically and incrementally? Yes
Does your app support multi-tenancy? Yes
Does your app have a confidential client? No
Do you own all of the redirect Unified Resource Identifier (URI) registered for your app? Yes
For your app, what do you avoid using? - Wildcard redirect URIs,
- OAuth2 Implicit Flow, unless required for a SPA
- Resource Owner Password Credential (ROPC) flow
Does your app expose any web APIs? No
Does your app use preview APIs? No
Does your app use deprecated APIs? No


Questions or updates to any of the information you see here? Contact us!