How To: Atlassian Access - Verify a Domain to Manage Accounts

[#1]

This guide will walk you through the process of verifying your company domain with your Atlassian Organization so that you can claim ownership of the accounts for your users that use your domain for their Atlassian accounts and if subscribed to Atlassian Access, you can apply additional security policies to domain managed accounts.

For your convenience, there is a video version of this guide at the bottom of this article this will show you how to follow these steps.  Also, each of the headings are hyperlinked to the specific time interval in the companion video where that topic is covered.

Before you begin there are some things you will need or assumptions I will be making about what you have access to change as a part of this tutorial. If you don’t have the ability to change or update something that is included in this guide you will either need to find someone that has the ability to perform certain steps or can give you the access you need to perform those steps.

Prerequisites:

• You are going to need to be an Atlassian Organization Administrator for you Atlassian Cloud Organization.

• I’m making the assumption in this guide that you will be verifying your domain over DNS.

• You are going to need to have access to add settings to you company domain DNS records. (This will likely be someone within you IT team)

• Your domain cannot have already been verified against another Atlassian Cloud Organization.

• You may need to wait up to 72 hours from the time you have applied your DNS settings change before you can verify your domain.

Getting the DNS record from your Atlassian Organization Settings:

• First, you will need to get to your Atlassian Cloud Organization Admin page. You can accomplish this by going to admin.atlassian.com or by selecting the Administration option in the top left “waffle“ menu of any Atlassian Cloud product where you are an Organization Admin.

• Next, you are going to want to navigate to Settings → Domains. Before you start, make sure you don’t see the domain you wish to verify listed already.
  

• Then, you want to make sure you are on the DNS tab, then copy the TXT record you need to add to your DNS settings.

Adding the TXT record to your DNS settings:

• Next, you need to go to your domain management portal. (If this isn’t something you have access to, you need to send the TXT record to someone who does, also be sure to let them know to set the name to “@“ and the TTL to 86400 seconds).
  

• Once you have added this value and confirmed that it saved correctly, go back to the Atlassian Organization Administration screen.

Verifying your domain once DNS has been updated:

• Then, click the “Verify Domain“ button.
  

• In the popup, select the “TXT Record“ method and enter the name of the domain you wish to verify.

• Then, click the verify domain button.

Viewing your managed accounts:

• Finally, you can go to the Directory → Managed Accounts menu options to see the accounts that you have claimed.
  Before:
  
  After:

  

[Pramodh M]

Wow @Jimmy Seddon You really are a gift!! 

Thanks for all the valuable contribution 🙂

[Jimmy Seddon]

Thank you @Pramodh M!  I really appreciate the kind words.

[Eric Johanson]

Any reason why it takes 72 hours to verify that the TXT records exists?  The site mxtoolbox.com can see the TXT record in a few seconds.

[serviceaccountdatacan]

Digicert will not allow @ for the name. If I leave it blank will it still verify? -Nevermind in your video you say you can leave it blank. TY!