LicenseMeter
Free scan

Connect Atlassian to LicenseMeter.

API connector

Atlassian product access survives offboarding more often than most. LicenseMeter reads managed users and their product access through the organization admin API and cross-checks each seat against Entra ID.

Setup, step by step.

  1. Create an organization API key

    In Atlassian Administration (admin.atlassian.com) under Organization settings > API keys, create a key. Only users with the organization admin role can do this.

    Atlassian organization admin API documentation (official documentation)

  2. Note the organization ID

    It is part of the Atlassian Administration URL (admin.atlassian.com/o/<organization-id>) and shown alongside the API key.

  3. Connect

    Paste the organization ID and the API key on the Atlassian connector page. Validated before storage, encrypted at rest.

What it finds.

  • Jira and Confluence seats held by accounts that are disabled in Entra ID.
  • Seats with no matching directory account at all.
  • Seats with no product activity for your inactivity threshold, where Atlassian reports it.

What LicenseMeter reads

  • Managed users: email, name and account status
  • Product access per user (Jira, Confluence) and last activity where Atlassian reports it

What it never reads

  • Issues, pages, projects or any content inside the products

Credentials are validated against the vendor before anything is stored, encrypted at rest (AES-256-GCM), used read-only and deleted the moment you disconnect. Data lives in the EU (Postgres, Frankfurt). The security overview covers the full picture.

Ready in a few minutes.

Open the connector page in your workspace, or walk through the live demo first to see the findings this connector produces.

Open the Atlassian connector