Open Question about configurations and drift

July 6, 2026

Hello fellow admins,

I have an open question for the community... How are other admins are keeping an eye on, or better yet managing, configuration drift, especially for those in regulated industries? For example, is your instance validated, or are you otherwise required to track configurations (e.g., workflows, permissions, fields, etc.) through a validated system to prove state and or prove your configs aren't drifting. If so, how are you doing that? What tools are you using (Microsoft Suite, internally developed, 3rd party apps, etc.)?

I'd love to hear from other admins in the cloud space, maybe even connect to share ideas and solutions.

6 comments

Hi @Gabriel Roth -- I have experience with this in the life sciences industry. I recommend third-party apps for this purpose. Currently, I am using Revyz. In the past, I've used Salto. There may be other solutions I haven't tried.

Tools like those provide a lot of helpful functionality to support configuration management. In regard to configuration drift specifically, you can capture baselines (snapshots) of your configurations and compare them against the current state at any time.

Like • Gabriel Roth likes this

Hi @Gabriel Roth , good discussion question. Like @Aaron Morris , I also use Revyz/Spin.ai Command Center for Jira, which actually has configuration drift-specific tools and other tools to help admins review, identify, and manage our configurations. You might check whichever 3rd-party your org uses, it probably has helpful tools. I'd also suggest reviewing some of the "site hygiene" articles in the Community, here are some of my regular go-to articles:

Good luck!

Like • like this

hi @Gabriel Roth

In regulated environments, configuration drift is fundamentally a governance challenge, not just a technical one. Rely on controlled change processes, configuration baselines, periodic audits, and evidence-based approvals to maintain platform integrity.

Large banks generally follow similar governance patterns regardless of whether they’re using Atlassian Cloud or Data Center. The focus is on proving control, traceability, and auditability rather than relying on the platform alone.

Like • like this

Hi @Gabriel Roth !

This is exactly what we built Solcoro for (solcoro.com). We track and monitor environment health over time, and our drift analysis tools identify exact changes/drift in your configs; no need to spend hours manually digging.

Happy to showcase the platform if you'd like!

Best,

Peter Kerrigan

Like • Gabriel Roth likes this

I think Jira has pretty good REST API. You can keep original configuration in readonly text file and perform audit once per month by forming a new file with curl or a python script and making diff.

I have something similair for project access rights. We are not allowed to add individual users to projects. Script checks users through REST API and if user is added to any project Security team gets notified.

@Gabriel Roth one potential thing to review with your quality / compliance teams is if you need an entire *instance* to be validated or if you can validate specific *spaces*. If you're able to perform a baseline risk assessment at the instance level and then only validate spaces with a higher level of risk, that could save you some time / documentation for the less risky spaces (e.g. general task tracking). You'd still likely want to be cognizant of instance-level settings that could impact all spaces, but hopefully the general concept makes sense.

One warning about the 3rd party apps discussed here - they are fundamentally reliant on Atlassian tooling and APIs to copy / promote configurations. Atlassian is in the process of but hasn't yet fully built out full configuration management capabilities in cloud. In my past evaluations of 3rd party apps, there were some glaring gaps that ended up being dealbreakers. Your mileage may vary.