Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

Assets Importer for Microsoft Azure AD/Entra ID is using lovebyte.codes' general DPA:DPA | Data Processing Addendum

Additional information for Annex 1

App: Microsoft Azure AD/Entra ID

Purposes of processing 

Categories of processing 

Categories of personal data 

Categories of data subjects 

Import Objects/Assets from Microsoft Azure AD/Entra ID into Jira Servicemanagement Assets.

We store Microsoft Azure AD/Entra IDs Tenant ID, Client ID and Client Secret exclusively in the Atlassian Storage API. We do not store any data on our servers.

We process Data from Microsoft Azure AD/Entra ID:

  • Users

  • Groups

  • Devices

  • Relations between Users and Groups, Users and Devices

We do not store this data after processing and importing the data into the Jira Servicemanagement Assets.

The App does not store any Assets or Information (except into the Atlassian Storage API, the Tenant ID, Client ID and Client Secret).

The App processes Data, such as Users, Groups, Devices and their relations.

Microsoft Azure AD/Entra ID…

  • …User

  • …Groups

  • …Devices

  • …Relations between Users and Groups, as well as between Users and Devices.

  • No labels