/
BETA - What is iConfig? (Introduction)

BETA - What is iConfig? (Introduction)

During the Open-Beta phase, we recommend that you use sandbox instances or new schemas in your production.

By installing this Beta App you agree with the Beta Terms and Usage Terms

iConfig is an endpoint inventory discovery solution that helps you discover, standardize, and keep your endpoint inventory up to date in Jira Assets (formerly Insight). It uses a lightweight Discovery Agent installed on endpoints to collect hardware/software and other endpoint data, then syncs the results into your Jira Assets object schema, enabling reporting, governance, and real-time querying.

What problems does iConfig solve?

Teams typically struggle with endpoint inventory because data is fragmented, stale, and hard to query:

  • Asset inventories become outdated as devices change or move

  • Hardware/software details require manual collection or spreadsheets

  • ITSM/Asset Management workflows need a reliable source of endpoint truth

  • Organizations need more than a “snapshot”—they need continuous discovery and filtering controls

iConfig addresses these needs by combining agent-based discovery, Jira Assets synchronization, and query tooling.

How iConfig is different from Assets Discovery

This is not meant to replace every use case of Atlassian Assets Discovery.

Assets Discovery is useful, especially in environments where network-based discovery and infrastructure scanning make sense.

iConfig focuses on a different approach:

Area

Assets Discovery

iConfig

Area

Assets Discovery

iConfig

Discovery model

Primarily network/server-based discovery

Agent-based endpoint discovery

Cloud scenario

May require additional setup, infrastructure, or connectivity considerations

Designed to send data directly to Jira Assets Cloud

Endpoint support

Depends on discovery configuration and reachable environments

Agent installed on Windows, Linux, and macOS

Remote/hybrid environments

Can be harder to manage when devices are not always on the same network

Better suited for distributed endpoints

Data control

Discovery output depends on scan configuration

Focus on controlled collection, filtering, and synchronization

Real-time device queries

Not the main use case

Includes additional Power Query capabilities for retrieving live data from a specific device

In short, iConfig is focused on the agent-based scenario many Assets Cloud customers have been asking for: install an agent, collect hardware and configuration data, and sync it into Jira Assets.

Key capabilities

Endpoint inventory discovery (via agent)

  • Collects endpoint details from Windows, macOS, and Linux endpoints using the iConfig Discovery Agent

  • Uses a secure connection via TLS and 100% outbound

  • Supports endpoints and maintains an up-to-date inventory in Jira Assets

Sync endpoints into Jira Assets inventory

  • Maps discovered endpoint data into Jira Assets object types/attributes

  • Enables reporting and asset governance directly in Jira/Assets

Software inventory + filtering/whitelisting

  • Supports software inventory collection

  • Provides filtering / whitelisting options to control which software entries are stored/imported reducing noise and improving data quality

Power Query for real-time endpoint queries (including custom queries)

  • Run real-time queries against endpoints

  • Create and test custom queries for advanced collection and validation use-cases

High-level: how iConfig works

A typical end-to-end flow looks like this:

  1. Onboard iConfig in your environment

  2. Create/choose an Assets schema (object schema and object types) for endpoint inventory

  3. Use the manual import link/on-boarding flow as applicable

  4. Download and install the iConfig Discovery Agent on endpoints

  5. Endpoints begin to sync discovered inventory into Jira Assets

  6. Use Power Query and filtering to validate results, run real-time queries, and tune what is collected (e.g., software whitelisting)

Prerequisites and important notes

  • Download links expire after 24 hours (plan your rollout accordingly)

  • Syncing may take time, depending on the environment size and endpoint availability

  • Avoid manual sync on many endpoints at once, as it may cause unnecessary load and longer processing times

  • For Linux/macOS, run the agent/installer as root when required by the procedure

  • On Windows, the user must be an admin and accept the risk indicated by Microsoft Screen Check.

    • We are already working to fix this during the beta testing phase.

Next steps (recommended reading)

Follow these pages to set up, deploy, and operate iConfig:

  1. iConfig Addon Setup Procedure

  2. Software Filtering Procedure - white list like

  3. Download and install the iConfig Agent on your endpoints

  4. Power Query Usage

  5. Creating Custom Queries in Power Query

  6. Tested custom queries

  7. Checking results of filtering - or whitelisting - software

Tip: If you’re new to iConfig, start with the setup procedure, then deploy the agent to a small pilot group of endpoints before scaling up.