Confluence Cloud

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: August 18, 2021

General information

Information provided by Atlassian to Microsoft:

Information Response
App name Confluence Cloud
ID WA200003113
Office 365 clients supported Microsoft Teams
Partner company name Atlassian
URL of partner website https://www.atlassian.com
URL of Privacy Policy https://www.atlassian.com/legal/privacy-policy
URL of Terms of Use https://www.atlassian.com/licensing/marketplace/termsofuse

Feedback

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

How the app handles data

This information has been provided by Atlassian 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
Calendars.Read delegated - We read the the list of Chat members in a meeting, so we know the list of invitees to the meeting. - We read the users’ names and email addresses which we conditionally display in our meeting app. For example, display the name of the current user taking meeting notes. - Our app reads the user’s calendar event where our app was added to a meeting so we have basic information about the meeting like meeting title. Examples of content we collect and store include: the summary and description added to a JIRA issue, the pages you create in Confluence, your repositories and pull requests in Bitbucket, comments you enter in connection with an incident in Statuspage, and any feedback you provide to us. Content also includes the files and links you upload to the Services. 4aa38041-66a2-41a4-ac97-55bc828a9803
Chat.ReadBasic delegated - We read the the list of Chat members in a meeting, so we know the list of invitees to the meeting. - We read the users’ names and email addresses which we conditionally display in our meeting app. For example, display the name of the current user taking meeting notes. - Our app reads the user’s calendar event where our app was added to a meeting so we have basic information about the meeting like meeting title. Examples of content we collect and store include: the summary and description added to a JIRA issue, the pages you create in Confluence, your repositories and pull requests in Bitbucket, comments you enter in connection with an incident in Statuspage, and any feedback you provide to us. Content also includes the files and links you upload to the Services. 4aa38041-66a2-41a4-ac97-55bc828a9803
User.ReadBasic.All delegated - We read the the list of Chat members in a meeting, so we know the list of invitees to the meeting. - We read the users’ names and email addresses which we conditionally display in our meeting app. For example, display the name of the current user taking meeting notes. - Our app reads the user’s calendar event where our app was added to a meeting so we have basic information about the meeting like meeting title. Examples of content we collect and store include: the summary and description added to a JIRA issue, the pages you create in Confluence, your repositories and pull requests in Bitbucket, comments you enter in connection with an incident in Statuspage, and any feedback you provide to us. Content also includes the files and links you upload to the Services. 4aa38041-66a2-41a4-ac97-55bc828a9803
email delegated - We read the the list of Chat members in a meeting, so we know the list of invitees to the meeting. - We read the users’ names and email addresses which we conditionally display in our meeting app. For example, display the name of the current user taking meeting notes. - Our app reads the user’s calendar event where our app was added to a meeting so we have basic information about the meeting like meeting title. Examples of content we collect and store include: the summary and description added to a JIRA issue, the pages you create in Confluence, your repositories and pull requests in Bitbucket, comments you enter in connection with an incident in Statuspage, and any feedback you provide to us. Content also includes the files and links you upload to the Services. 4aa38041-66a2-41a4-ac97-55bc828a9803
offline_access delegated - We read the the list of Chat members in a meeting, so we know the list of invitees to the meeting. - We read the users’ names and email addresses which we conditionally display in our meeting app. For example, display the name of the current user taking meeting notes. - Our app reads the user’s calendar event where our app was added to a meeting so we have basic information about the meeting like meeting title. Examples of content we collect and store include: the summary and description added to a JIRA issue, the pages you create in Confluence, your repositories and pull requests in Bitbucket, comments you enter in connection with an incident in Statuspage, and any feedback you provide to us. Content also includes the files and links you upload to the Services. 4aa38041-66a2-41a4-ac97-55bc828a9803
openid delegated - We read the the list of Chat members in a meeting, so we know the list of invitees to the meeting. - We read the users’ names and email addresses which we conditionally display in our meeting app. For example, display the name of the current user taking meeting notes. - Our app reads the user’s calendar event where our app was added to a meeting so we have basic information about the meeting like meeting title. Examples of content we collect and store include: the summary and description added to a JIRA issue, the pages you create in Confluence, your repositories and pull requests in Bitbucket, comments you enter in connection with an incident in Statuspage, and any feedback you provide to us. Content also includes the files and links you upload to the Services. 4aa38041-66a2-41a4-ac97-55bc828a9803
profile delegated - We read the the list of Chat members in a meeting, so we know the list of invitees to the meeting. - We read the users’ names and email addresses which we conditionally display in our meeting app. For example, display the name of the current user taking meeting notes. - Our app reads the user’s calendar event where our app was added to a meeting so we have basic information about the meeting like meeting title. Examples of content we collect and store include: the summary and description added to a JIRA issue, the pages you create in Confluence, your repositories and pull requests in Bitbucket, comments you enter in connection with an incident in Statuspage, and any feedback you provide to us. Content also includes the files and links you upload to the Services. 4aa38041-66a2-41a4-ac97-55bc828a9803

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?

No EUII is accessed.

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?

No OII or EUII appear in the applications telemetry or logs.

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.

https://www.atlassian.com/trust/privacy/how-we-handle-your-data

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?

No

Feedback

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

Feedback

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

Identity information

This information has been provided by Atlassian 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? No
Does your app have a confidential client? Yes
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

Feedback

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