...
Data | Description |
|---|---|
User data | Ids, name & email adress of users |
User Access Tokensaccess tokens | Access tokens (Microsoft Graph, Atlassian OAuth1.0a and OAuth 2) |
Jira & Confluence related data | The apps store data related to issues/projects/spaces etc. |
Microsoft Graph related data | The app store data related to Microsoft Graph activities (e.g. status of active subscriptions) |
Settings | Settings created by the admins, e.g. templates, presets |
Automation Datadata | Data related to the automation features |
Audit Loglog | Log of auditable acitivitiesactivities |
Non-Regional data
The following data are “stored globally” and are replicated into every region.
Data | Description | ||
|---|---|---|---|
Teams user data | We keep a mapping and user profile (incl. email address) of Microsoft Teams users to region to forward requests into the correct region. | ||
Instance data | We maintain a list of all customer instances including their baseUrl Jira URL and their region. | ||
Teams Bot bot data | MIcrosoft Microsoft Teams does not have a data residency concept for Botsbots. We need to forward these requests into the correct region. | Teams User data | Same as above, we keep a mapping of Team User Ids to region to forward store bot installation data globally to forward these requests into the correct region. |