Atlassian Jira Cloud Saml Setup and Managed Accounts

Sneha Kona

When I am doing a saml setup for our Atlassian Jira cloud using Azure Active Directory and by providing company domain, its not only pulling our company Jira users but also the private atlassian accounts of all the jira users using same work-email with company domain example (raj.johnpal@companydomain.ca) 

My question here 

1. Will all those private atlassian accounts of other products of my jira users also get charged for "Atlassian Access".

2. If I dont want those other Atlassian products account such as (Trello, Bitbuket etc) of my Jira users to be shown in my Managed Accounts which is exceeding user count 600+ users , what could be the options to remove them.

 

Victor Law - Ricksoft

Hi @Sneha Kona

1. Will all those private atlassian accounts of other products of my jira users also get charged for "Atlassian Access".

All the Atlassian accounts with email addresses from your Atlassian Access's verified domains become managed accounts, which will be charged by default. You must manually assign user accounts to the non-billable policy.

Just a side note: the user accounts not assigned with the paid policy will NOT be able to enforce MFA and the paid features from Atlassian Access.

You may refer to the following doc for more reference:

https://support.atlassian.com/security-and-access-policies/docs/understand-authentication-policies/

If I dont want those other Atlassian products account such as (Trello, Bitbuket etc) of my Jira users to be shown in my Managed Accounts which is exceeding user count 600+ users , what could be the options to remove them.

You can assign the user accounts using the non-billable policy mentioned above.

Alternatively, I strongly recommend reviewing the user account's last login activities regularly and deactivating those user accounts that are no longer active.

Thank you.