Confluence Connector

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: September 22, 2021

General information

Information provided by Move Work Forward to Microsoft:

Information Response
App name Confluence Connector
ID WA200001604
Office 365 clients supported Microsoft Teams
Partner company name Move Work Forward
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 Move Work Forward 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 Channel name and id is used to send notifications from Jira to Microsoft Teams. The channel id and the name is stored to configure notifications from Jira to Microsoft Teams. f3943662-e828-40ed-9c6e-369680fe421f
Teams.ReadBasic.All delegated The permission is used to let the user select one of this joined teams in Jira. Team id and name to display in Configuration screen in Jira. f3943662-e828-40ed-9c6e-369680fe421f
TeamsAppInstallation.ReadForTeam delegated Read installed Teams apps in teams. When setting up delivery to Microsoft Teams the App can send to Teams with the Bot installed. Nothing f3943662-e828-40ed-9c6e-369680fe421f
User.Read delegated Allows the user to create a discussion channel with co-workers and to @-mention in a channel message Nothing f3943662-e828-40ed-9c6e-369680fe421f
email delegated Email is used to match Atlassian and Microsoft Users The email is not stored. Only used during the matching process. f3943662-e828-40ed-9c6e-369680fe421f

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.

Non-Microsoft services are not used.

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?
Greet users by name when the install the App. Match Microsoft Teams and Atlassian users. 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?

We log the tenant url, which is stored in the logs for up to 5 days.

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!

Identity information

This information has been provided by Move Work Forward 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,

- 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!