Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Are existing internal groups retained when Access integrated with AD?

Hi

We're thinking of adding Atlassian Access to our Cloud Jira/Confluence setup and integrating it with our Azure AD.

What will happen to our existing groups which are used in many places - permissions, roles, workflows etc? Will they be retained and still accessible separately from the groups imported from Azure AD?

Any tips on best practice as regards deprecating the existing internal groups and switching to groups provisioned from AD?

Thanks

1 answer

1 accepted

0 votes
Answer accepted
Dave Meyer Atlassian Team Sep 12, 2020

Hi @Julia Foden ,

Your existing "local" Atlassian groups that you've already created remain as-is, and permissions and other references to them are never affected. The directory syncing with Azure AD pushes groups from Azure AD as "new" groups by default. If you push groups from Azure AD that have the same name as existing local groups, you will be given the option to merge memberships of the group and manage the group membership via Azure AD (see https://confluence.atlassian.com/cloud/user-provisioning-959305316.html#Userprovisioning-Resolvegroupconflicts)

Any tips on best practice as regards deprecating the existing internal groups and switching to groups provisioned from AD?

This really depends on how many existing groups you have and how extensively they are used. I would say typically for customers that have pretty extensive roles and workflows that reference existing groups, the first thing to target is using externally managed groups for product access (i.e. which users actually have a seat in Jira and Confluence) because this helps ensure that when a user is deactivated in Azure AD, they no longer consume a Jira/Confluence license. Then customers typically replace local groups with external groups for permissions and stuff on an as-needed basis.

Cheers,

Dave 

Thank you Dave

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Atlassian Access

Resources + Q&A from "What's new in Atlassian Access" webinar

Hi Community! Thank you to all those who joined our What’s new in Atlassian Access webinar last week! We received so many great questions about existing functionality and newly released features of...

744 views 0 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you