Cloud-to-Cloud Fetch and Scheduling Are Here for Assets Data Manager

[#1]

Hi everyone! 👋

We're thrilled to announce two major updates to Assets Data Manager that many of you have been asking for: Cloud-to-Cloud (C2C) Fetch for five popular adapters and automated scheduling for C2C-enabled data sources.

These updates mean less infrastructure to manage, fewer steps, and fresher asset data — all without leaving the Data Manager UI when using the C2C adapters.

1. Cloud-to-Cloud (C2C) Fetch — no more CLI required for top adapters🚀

Until now, fetching data from cloud-based sources required you to download, install, and maintain the Data Manager Adapters Client (CLI) on your own infrastructure. You'd need to generate tokens, configure the client, and manually trigger fetches from the terminal.

That changes today.

With Cloud-to-Cloud Fetch, Data Manager connects directly to your cloud data source and runs the fetch entirely on Atlassian's cloud infrastructure. No on-prem agent. No terminal commands. No extra infrastructure to maintain when using the C2C adapters.

Supported adapters:

Adapter	C2C Support
Flexera IT Visibility	✅ Available
Microsoft Intune	✅ Available
Microsoft Entra ID User	✅ Available
Jamf	✅ Available
Lansweeper (API)	✅ Available

Key highlights:

• Test Connection and save time — When configuring a C2C-enabled adapter, Data Manager validates your credentials before saving. No more discovering invalid credentials only after running a job.

• "Fetch from Cloud" button — Once configured, simply click "Fetch from Cloud" from the data source configration page. The fetch runs in the background — no need to switch to a terminal or leave the UI.

• Migrate existing jobs — Already have a CLI-based job? You can switch it to C2C by editing the data source and selecting "Cloud to Cloud" mode. No need to recreate your configuration from scratch.

• CLI still available — Prefer the existing approach? The CLI/Adapters Client continues to work exactly as before. C2C is an additional option, not a replacement.

Note: For Lansweeper, C2C supports the API source type only. SQL source types continue to use the Data Manager Client.

2. Automated scheduling for C2C adapters ⏰

Previously, keeping your asset data fresh meant having to configure an external job scheduler. Now you can schedule the import within Data Manager.

With scheduling support for C2C adapters, you can configure a refresh cadence directly in Data Manager. Once set, the data fetch and merge runs automatically on your chosen schedule.

How it works:

1. Navigate to your C2C-enabled data source

2. Configure a schedule (choose your desired frequency)

3. Data Manager handles the rest — fetching, transforming, cleansing, and importing on autopilot

Built-in safety guardrails:

• Scheduling is only available after your first successful merge — this ensures your mappings and configuration are validated before automation kicks in.

• If a schema change requires updated mappings, scheduled runs automatically pause until you review and confirm the changes. No risk of merging mismatched data.

---

Before and after

	Before	After
Setup	Download & install CLI client on your environment	Configure credentials directly in the Data Manager UI
Fetching a data source	Open terminal, run CLI commands	Click "Fetch from Cloud" or let the schedule handle it
Keeping data fresh	Manually re-run the pipeline or script an external scheduler yourself	Set the schedule inside the Data Manager UI
Credential validation	Discover errors only when the job fails	Instant validation at save time with Test Connection

Getting Started

For new data sources:

1. Go to your Object Class ->Show data sources → Add data source

2. Select a supported adapter (you'll see a “Cloud enabled” indicator)

3. Choose "Cloud to Cloud" mode

4. Enter your credentials and configure your adapter

5. Click "Fetch from Cloud"

6. Once your first fetch succeeds, configure a schedule to automate future refreshes

For existing CLI-based data sources:

1. Navigate to your existing data source

2. Click "Edit data source"

3. Switch the mode to "Cloud to Cloud"

4. Save — your credentials will be validated via Test Connection

5. You're now ready to use "Fetch from Cloud" and scheduling

What's next

This is just the beginning for Cloud-to-Cloud in Data Manager. We're working on expanding C2C support to additional data sources in the coming quarters. Stay tuned for updates. 

Resources

• https://support.atlassian.com/assets/docs/learn-about-adapters — Full documentation on configuring each supported adapter

• https://support.atlassian.com/jira-service-management-cloud/docs/what-is-data-manager/ — Getting started with Data Manager

 Questions?

Drop them in the comments below! We'd love to hear how you plan to use C2C and scheduling in your environment.

#JiraServiceManagement #Assets #DataManager #ITAM #ProductUpdate #AtlassianCommunity

[Dirk Ronsmans]

Awesome! This has (long) been a weird thing that we had to run a local client to pull from a Cloud source to then push to Cloud instance. So happy that we can now do all of it in Cloud.

Especially look at the Entra User ID and Lansweeper adapters!

@Sonia Mahabir Gandhi couple of questions:

• Could you elaborate a bit on when we might be seeing the changes in our instances?
• Will there be some kind of mechanism when a fetch/the process fails? The more we automate we still need to know when something goes wrong of course. Ideally this would feed in to JSM Operations but even just an email would already be great :)
  Normally everything should run smooth of course but you never know whether the source might throw an error/a token might have expired or revoked or if we need to add a new mapping due to adapter changes.
• Linking with that last comment, now we are able to watch the adapters marketplace app when new features are added to an adapter and it was manual action to add the new client version which might include more mappings needed for a source. How will that be handled now? The adapters will auto update as they are part of the platform now so how will we know when we need to map more attributes due to adapter changes?

Beyond that, moving in the right direction!

[Matthew Challenger]

Been looking forward to this progress since Data Manager was announced. Great to see it's finally live.

[Sonia Mahabir Gandhi]

@Dirk Ronsmans Thanks for your comment!

To answer your questions:

• Could you elaborate a bit on when we might be seeing the changes in our instances?
  • We follow a phased rollout strategy, and initial rollout has already begun. Most instances should be seeing the new adapters live over the next few weeks.
• Will there be some kind of mechanism when a fetch/the process fails? The more we automate we still need to know when something goes wrong of course. Ideally this would feed in to JSM Operations but even just an email would already be great :)
  Normally everything should run smooth of course but you never know whether the source might throw an error/a token might have expired or revoked or if we need to add a new mapping due to adapter changes.
  • Currently, the only way to track failures is by going into the Audit logs under Object classes. The email notification on failure is good suggestion, and already in our backlog.
• Linking with that last comment, now we are able to watch the adapters marketplace app when new features are added to an adapter and it was manual action to add the new client version which might include more mappings needed for a source. How will that be handled now? The adapters will auto update as they are part of the platform now so how will we know when we need to map more attributes due to adapter changes?
  • Since these C2C adapters are not linked to the adapters marketplace app, we will be maintaining separate release notes and support documentation for these, and will send out posts to the Community when significant updates are made.