Six Step series on how to set up Atlassian Access with User Provisioning

November 25, 2021

Welcome to our the first in our series of blog posts regarding Atlassian Access.

As Atlassian support Atlassian Server product ends in 2024, many organisations are moving to Atlassian Cloud and are using, or considering, Atlassian Access.

In this series of blog posts we will walk through the steps we typically see enterprises walk through to configure Atlassian Access.

This first blog post focuses on Benefits of Atlassian Access, steps for Domain Verification and Claiming Accounts.

Benefits of Atlassian Access

Atlassian Access is an organisation-wide subscription that connects your Atlassian cloud products to your identity provider, enabling identity and access management features for your domains.

  • Connect to your SAML SSO Provider
  • Automate User Provisioning
  • Enforce two-step verification
  • Organisation wide audit logs
  • and more …

As Atlassian Access is organisation wide, it applies to when users in your domain are using your Atlassian instances (eg. Jira/Trello/Confluence/etc) and when they are using other instances (eg. collaborating in a supplier or customer’s Atlassian instance). Through automatic product discovery, when new instances of Atlassian products are created, administrators receive notification.

We worked with an organisation that thought there might be about twenty staff with Atlassian accounts, there were close to 600. Those users were using just a username and password to verify their accounts, the organisation wanted Multi-Factor Authentication, which we enabled.

Domain Verification

The first step for an organisation is to verify their Domain with Atlassian.

What is a domain? A domain is the address of your website (eg. ) or email address after the @ symbol (eg. You can have one or more domains (eg. we have and

Domain verification can be done in three ways:

  1. Domain Name Service (DNS) - add TXT Record
  2. HTTPS - upload a file to the root of your website
  3. G Suite - connect your G Suite account

Most organisations we work with verify by DNS entry, so the post will walk through that process.

Verify by DNS Entry

Obtain the DNS Record details

  1. Navigate to your organization (sic) at, select Directory > Domains, this is your the Directory Domains page.
  2. From the DNS tab, copy the txt record to your clipboard.

Add the TXT Entry to your DNS.

Go to your DNS host and find the settings page for adding a new record or raise a ticket with your IT Help desk if they manage your DNS Host to perform the following steps:

  1. Select the option for adding a new record and paste the txt record to the Value field (may be named Answer or Description or something equivalent). Your DNS record may have the following fields:
    1. Record type: Enter 'TXT'
    2. Name/Host/Alias: Leave the default (@ or blank)
    3. Time to live (TTL): Enter ‘86400' or a value more suitable to your organisation’s standards
  2. Save the record.

Verify the Domain

  1. Return to the Directory Domains page
  2. Select Verify domain.
  3. Keep your TXT Record as the method, enter the domain you want to verify in the Domain field, and click Verify domain.

Depending on your DNS host, it may take up to 72 hours for your domain to verify and DNS changes to take effect. The domain you tried to verify will be listed in the Domains table, it will have an UNVERIFIED  status.

Once the domain has been verified the Domains table will be be updated with a status of VERIFIED.

Claim accounts

After verification of your domain the Atlassian accounts of anyone using a verified domain can be claimed and then becoming Managed Accounts.

Export accounts

To export and view details of the accounts (email address, last logged in, products used, etc):

  • On the Directory Domain Page, in Domains table, click Claim accounts.
  • From the Claim accounts screen that opens, you’ll see the number of accounts with your domain.

Select Export accounts to download a CSV file with details on the accounts.

Select Claim accounts to complete the domain verification process and claim those accounts for your organization [sic].

Next Post

In our next post we will walk through the process over connected Atlassian Access with Azure AD to enable SAML SSO. In later post we will walk through the process of implementing Authentication Policies.

Further Reading

If you are looking for read more information, than we recommend you to visit following support pages from Atlassian:

Contact Us

If you are considering Atlassian Access or need help with it or any of your other Atlassian products, please contact via our support portal.

Joy Grover
November 25, 2021
Agile, SDLC, Program Management, ITIL/Service Desk Support / Jira, Confluence, Atlassian Toolset, Bitbucket, Atlassian Dev Ops. Solutions include PPM, Compliance and Risk Management, HR, CRM and general business process support.
Privacy Policy
Cookie Policy

Our Social Networks

Know Business works with teams to deliver. That team could be small, from seven people to a large program of three hundred people. 
We also work with teams across organisations.
crosschevron-downarrow-right-circle linkedin facebook pinterest youtube rss twitter instagram facebook-blank rss-blank linkedin-blank pinterest youtube twitter instagram