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.
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.
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.
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. knowbusiness.com.au ) or email address after the @ symbol (eg. email@example.com). You can have one or more domains (eg. we have knowbusiness.com.au and knw.bz).
Domain verification can be done in three ways:
Most organisations we work with verify by DNS entry, so the post will walk through that process.
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:
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.
After verification of your domain the Atlassian accounts of anyone using a verified domain can be claimed and then becoming Managed Accounts.
To export and view details of the accounts (email address, last logged in, products used, etc):
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].
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.
If you are looking for read more information, than we recommend you to visit following support pages from Atlassian:
If you are considering Atlassian Access or need help with it or any of your other Atlassian products, please contact via our support portal.