Skip to content

Atlassian Cloud for Regulated Industries

Atlassian Cloud and AI That Pass the Audit

We make data location, access and Rovo agents provable, so security, privacy and your auditors can sign off.

Why Governance Can't Wait

22
EU tech laws in the 2019–2024 term
70%
of EU cloud spend goes to three US hyperscalers
69%
of knowledge workers say their data isn't ready for AI
70+
ready-made sensitive-data detections in Guard

EU Regulation

Many Rulebooks, Different Deadlines, One Audit

According to the Business Software Alliance, the EU passed some 22 tech laws in 2019–2024 alone. They were written in parallel, so they overlap and sometimes conflict. A single security incident can trigger several reporting duties, each with its own definition, deadline and form.

  • NIS2 was due in national law by October 2024. As of July 2026, France, Spain, Ireland and the Netherlands still had none.
  • GDPR, NIS2 and the Cyber Resilience Act each define a reportable incident differently.
  • National cloud schemes such as Germany's BSI C5 or France's SecNumCloud add their own requirements, some of them about who owns the vendor.
  • The EU AI Act is expected to land as broadly as GDPR did, with fines on a similar scale.

What that means for you: your governance has to absorb new obligations without a fresh plan each time. That is how we set up Atlassian Cloud.

Atlassian Platform · As of October 2026

What the Platform Does Today, and What's Coming

Available today

Data in the EU

Data residency for your product data, Rovo included

Tenant isolation

Isolated Cloud as single-tenant SaaS, generally available – and, Atlassian admits, pricey for many

Finding sensitive data

Guard scans Jira, Confluence and attachments, with 70+ built-in patterns plus your own detections

AI agents

Agent accounts with their own identity and least-privilege access, an audit log and an off switch

Certifications

SOC, ISO 27001, BSI C5 and PCI DSS among others – now joined by ISO 42001 for AI management

Announced or on the roadmap

Data in the EU

EU AI inference in early access: answers come from models hosted in the EU

Tenant isolation

A sovereign offering Atlassian is shaping with customer design partners

Finding sensitive data

Semantic scanning and exact data match, announced for later this year

AI agents

An agent inventory, more agent audit logs and dynamic threat modelling for agents

Certifications

ISO 27017, ACN and ENS are due by the end of the year
Circular diagram with three arrows: Prepare, Build and Monitor looping around the AI governance frameworkAtlassian Team '26 Europe

How We Work

Four Steps to AI Governance That Grows With You

We work in the loop Atlassian itself recommends: prepare, draw the boundary, monitor, and tighten after every stage of rollout.

1
Prepare

Get Your Data AI-Ready

Together we define what counts as confidential, scan the whole site and let policies redact or flag what they find.

2
Build

Draw the Boundary

We settle three questions: who has access, what data the AI can see, and which actions an agent may take.

3
Monitor

Keep Sight of People and Agents

An overview, an agent inventory and an audit log show who ran which agent, when, and with what tools.

4
Repeat

Tighten and Repeat

New features and new obligations move the boundary, so the loop starts again after every stage of rollout.

TeamViewer slide "Clear answers created room to act" with two panels: trust and assurance, controlled enablementAtlassian Team '26 Europe / TeamViewer

Case in Point

TeamViewer Rolls Out Rovo in Stages

TeamViewer switched Rovo on in stages: search first, then chat, then agents. It started with the questions stakeholders were asking about security, privacy and responsible AI, and only widened access once those had answers.

  • Due diligence through the Atlassian Trust Center gave the security review a structured starting point.
  • Rovo went out by group rather than organisation-wide, so access could grow deliberately, one step at a time.
  • Every space got a clear owner and permission upkeep became an ongoing job. Historic permissions were deliberately not all fixed up front.
  • In third-level support, Rovo analysed ticket samples. People still did the interpreting and made the call.

Monthly active Rovo users grew roughly eightfold in the early rollout. Toni Soldat is clear that this is not yet proof of business value. Next on TeamViewer's list: the agent lifecycle and data protection.

Common Questions About Cloud Governance

What IT, security and privacy leads should settle before the next step.

Is data residency enough for digital sovereignty?

For many requirements, no. Data residency governs where data is stored. In its strictest tier, the planned Cloud and AI Development Act (CADA) could also require European capital and European staff. Atlassian says the text is not settled yet, so plan with options rather than one fixed assumption.

Is Isolated Cloud the answer?

For some organisations, yes: Isolated Cloud provides a dedicated, isolated environment. It does not automatically meet data sovereignty requirements, however. Check separately where data resides, which jurisdictions and access rules apply, and whether your specific security requirements are met. The dedicated environment also costs more than the regular cloud.

What does the EU AI Act change for how we use Atlassian?

It is risk-based and, since ChatGPT, has its own rules for AI models. The part people overlook is the AI literacy obligation for your staff. Training belongs in your governance just as much as the technical settings do.

Do we have to clean up every permission before Rovo?

TeamViewer didn't. The team controlled access by group, gave every space an owner and made permission upkeep an ongoing task. A permission check up front shows you where the real risk sits and what can safely wait.

Where should we start?

With three quick steps Atlassian also recommends: use the Trust Center for due diligence, set up custom detections for your sensitive terms, and open agent insights in Atlassian Administration. Add one question: what does sovereignty mean for you in practice? We work that out with you in the governance check.

How We Help

As an Atlassian Platinum Partner, we put the platform's governance building blocks to work in your organisation, from the first scan to policies that actually enforce.

01

Guard Premium and Classification

We turn your classification scheme into Guard policies and switch them on in stages: watch first, automate second.

See the Compliance Approach →
02

Check Permissions Before Rovo

The permission assessment shows which spaces and projects are too open before an AI starts reading them.

Go to the Assessment →
03

Migration With Governance Built In

For teams moving from Data Center to Cloud: we plan data residency, admin structure and policies as part of the move.

Explore Cloud Migration →
04

Roll Out Rovo and Agents

Group-by-group enablement, agent accounts with least privilege, and an audit log your security team can actually use.

Talk to Us →

Bring Your Audit Questions

In a first call we work out which of the announced features already cover your requirements, and where you need a bridge until the rest arrives.