Azure Sync for Jira Assets vs. Assets Data Manager
This page explains how Azure Sync for Jira Assets differs from Atlassianβs built-in Assets Data Manager, so you can choose the right option for bringing Azure and Entra data into Jira Assets.
In short: Assets Data Manager is a multi-source IT asset data pipeline with cleansing and reconciliation. Azure Sync for Jira Assets is a dedicated, cloud-native integration for Azure and Microsoft Entra ID, with broader Azure resource coverage and a simpler setup for Azure-focused teams.
Overview
Aspect | Assets Sync for Jira | Data Manager |
|---|---|---|
What it is | An Atlassian Marketplace app that synchronizes Azure resources and Microsoft Entra ID objects into Jira Assets. | A native Jira Service Management feature that connects multiple data sources, cleanses and reconciles data, and helps build a reliable single source of truth. |
Availability | Available on the Atlassian Marketplace for Jira Cloud. | Generally available and included with Service Collection / Jira Service Management Premium and Enterprise plans. It must be enabled in Assets settings. |
How it runs | Fully cloud-based (built on Atlassian Forge). No local agents or middleware required. | Cloud administration plus locally installed Data Manager clients (Adapters client and Cleanse & Import client) used to fetch and process data. |
Key features comparison
Feature | Azure Sync for Jira Assets | Assets Data Manager |
|---|---|---|
Primary focus | Azure and Entra ID β Jira Assets | Multi-source asset data quality (complete, current, and correct) |
Azure / Entra connectivity | Broad Azure resource synchronization plus Entra ID (users, groups, devices, and related objects) | Limited Azure-related adapters today: Azure Virtual Machines, Entra ID Users, and Entra ID Devices |
Other data sources | Focused on Azure and Entra ID | Flat files, SQL/ODBC, and many tool adapters (for example Intune, SCCM, Qualys, ServiceNow, and others) |
Setup | Install from the Marketplace, connect your Azure app registration, and configure sync in the app | Enable Data Manager in Assets settings, configure roles, install local clients, set up adapters, then cleanse, merge, and import |
Data cleansing & reconciliation | Keeps Jira Assets aligned with Azure as the source of truth for synchronized objects | Advanced cleansing, deduplication, normalization, and reconciliation across multiple sources |
Automation & scheduling | Automated and on-demand synchronization options | Jobs run via local clients and your scheduler; imports into Assets schemas can be scheduled |
User experience | Guided, Azure-specific configuration | Broader admin experience for sources, adapters, and data integrity |
Benefits
Azure Sync for Jira Assets | Assets Data Manager |
|---|---|
Deep Azure integration Synchronize a wide range of Azure resources into Jira Assets with relationships suited to Azure operations. | Multi-source asset management Bring data from many tools into one place. |
Faster time to value for Azure Configure sync in the cloud without installing local middleware. | Data quality tooling Cleanse, deduplicate, normalize, and reconcile records across sources. |
Cloud-native delivery Built on Forge, with data handled inside the Atlassian ecosystem. | Flexible connectivity Files, databases, and a wide set of enterprise adapters. |
Azure-focused product roadmap Ongoing Azure and Entra enhancements driven by customer feedback. Active development with dedicated developers, quick implementation of feature requests, and a smaller backlog for faster improvements. | Included with Premium / Enterprise No separate Marketplace fee for Data Manager itself. |
Flexible synchronization Use the built-in 12/24-hour scheduler, run imports on demand, or trigger selected imports from Jira Automation when you need custom timing or workflow-driven sync. | Β |
Limitations
Azure Sync for Jira Assets | Assets Data Manager |
|---|---|
Designed for Azure and Entra ID - not a general importer for unrelated tools | Limited native Azure coverage (Virtual Machines and Entra ID users/devices) |
Requires Azure app registration and appropriate Microsoft permissions | Requires a Premium or Enterprise plan and Assets administrator enablement |
See Known Limitations in the Azure Sync user documentation | Requires local Data Manager clients and operational capacity planning; Azure VM setup is typically one subscription per adapter. See Atlassianβs Data Manager requirements and limits documentation |
Azure Sync for Jira Assets
See the current list of supported Azure resources and attributes in theResource Sync Feedback Hub. Coverage includes areas such as subscriptions and resource groups, networking, compute, storage, databases, containers, AI services, and Entra ID objects.
Assets Data Manager
Azure Virtual Machine
Entra ID User
Entra ID Device
Typical use cases
Azure Sync for Jira Assets is a strong fit when⦠| Assets Data Manager is a strong fit when⦠|
|---|---|
Azure is your primary cloud source for asset data in Jira | You need to combine many non-Azure sources (for example discovery tools, endpoint tools, files, or databases) |
You need broad Azure resource visibility in Jira Service Management | You need advanced cleansing and cross-source reconciliation |
You prefer a cloud-only setup without local import clients | You already operate (or are ready to operate) Data Manager clients on Premium or Enterprise |
Pricing
Pricing
Aspect | Azure Sync for Jira Assets | Assets Data Manager |
|---|---|---|
Pricing model | Paid Atlassian Marketplace app for Jira Cloud | Included with Jira Service Management / Service Collection Premium and Enterprise |
Cost considerations | Marketplace app subscription based on Atlassian Marketplace tiers | No additional Data Manager license fee, but requires a Premium or Enterprise plan and the operational effort to run local clients |
For current list prices, refer to the Atlassian Marketplace listing for Azure Sync for Jira Assets and Atlassianβs current plan pricing.
Support and resources
Aspect | Azure Sync for Jira Assets | Assets Data Manager |
|---|---|---|
Support | Partner-supported by SΓ½kora IT via Marketplace support channels Documentation and setup guides provided by the app developers. Active feedback hub for feature requests and suggestions. | Atlassian Support, documentation, and community resources |
Resources | Product documentation, data mapping guide, FAQ, roadmap, frequent updates from dedicated developers and Resource Sync Feedback Hub | Documentation for adapters, clients, cleanse/import workflows, and Data Manager administration |
Which should you choose?
Choose Azure Sync for Jira Assets if your organization is Azure-centric, needs broad Azure and Entra coverage in Jira Assets, seeks quick development cycles with dedicated developers, active feedback hub, fast updates and wants a cloud-native synchronization experience without local Data Manager clients-
Choose Assets Data Manager if you need a multi-source IT asset pipeline with cleansing and reconciliation across many tools and Azure is only one part of that picture.
Many teams use Azure Sync specifically for Azure β Jira Assets synchronization. Data Manager remains a good option when you also need to unify non-Azure data sources.