Skip to main content
View as MarkdownOpen in ChatGPTOpen in Claude

Identity Mesh — February 25, 2026

Version: Identity Mesh 02-25-2026
Release Date: February 25, 2026\

Overview​

This release expands Identity Mesh's integration coverage with a new connector framework that adds support for 14 third-party systems. Connectors built on this framework synchronize users, groups, applications, and related entities into Identity Mesh. The Jira connector is available first, with the remaining integrations to follow. Existing connectors are unaffected.

New features​

14 new third-party integrations​

Identity Mesh can now synchronize identity data from the following systems:

  • Identity and access: Auth0, Google Workspace

  • Cloud infrastructure: AWS

  • Development and collaboration: GitHub, Jira, Confluence, Linear, Databricks

  • Business applications: Box, DocuSign, Dropbox, PagerDuty, Datadog, Snyk

Available now: Jira. The remaining integrations will be enabled in upcoming releases.

What these connectors do:

  • Synchronize users, groups, applications, roles, projects, and permissions from the connected system into Identity Mesh

  • Support incremental sync, so recurring syncs transfer only what changed — faster and lighter on the connected system

  • Track sync progress and recover automatically if a sync is interrupted, resuming where they left off

  • Prevent the same sync job from running twice at once

  • Scale automatically with sync workload

You set up these connectors the same way as existing ones: select the provider from the provider list when adding a connector in the dashboard.

No impact to existing connectors​

All existing connectors, including Microsoft Entra ID and ServiceNow CMDB, continue to work unchanged. This release introduces no changes to existing functionality.

Known issues​

  • Jira projects and project roles: project and project-role information is not yet synchronized. Support will be added in a future release.

  • Users missing required fields: a small percentage of Jira users may be skipped during sync if their account is missing an email address or name.

  • Entity coverage: not every entity type is mapped yet for every integration. Additional coverage is being added iteratively.

  • Jira user identifiers: Jira user identifiers may appear in two different formats depending on the account's age. A consistent format is planned.

  • Last sign-in: last sign-in information is not yet populated for Jira users.