Assign product access automatically with Azure User Provisioning

Question

Hi all,

We just implemented user provisioning via Azure AD. I created a test account and performed a Provision on demand. The user was created in the Directory Users, however he was not allocated the Product Access required. We have an enterprise application called Atlassian SSO, which links the user provisioning. I also added the Group product access under the Atlassian SSO, but no luck.

Any help would be appreciated!

Kieren _SmolSoftware_ · Answer

They could, absolutely. That’s the same as option 1. If it’s just one group that has all the users you want to grant access to, then just apply product access to that one group.

But make sure you include that group in any project or global permissions you need to use.

Instead of getting an invite, you should just include the Jira/Confluence URL in your staff onboarding training. There’s no way to automatically create invites for users added via SCIM.

Matthew.Bonanno · Answer

All users who are given the Atlassian SSO group are created in Atlassian, however they don't receive an invite since they don't have any product access. I assumed that if the Atlassian SSO group from Microsoft is syncing into Atlassian, they would get the product access from the Atlassian SSO group in Atlassian.

Kieren _SmolSoftware_ · Answer

Hey @Matthew.Bonanno

I think you have three options:

1. Choose some of the sync’d groups that you’ve created in the Atlassian Directory, and assign them product access to the products you want. The pro of this is you’re maintaining product access directly from your sync’d groups. The cons are; you’ll need to monitor for any new groups that are created with new users in them from Azure AD, and grant those groups access as will. And you’ll need to ensure all these groups are granted access to your various Jira projects, and Jira global permissions. It can be a fair bit of work to keep ontop of.

2. You manually add the users to the jira-users-siteName group, after they’ve been sync’d. This group is already set up with all the correct default project and global Jira permissions. This can also be a lot of work if you have new users joining and existing users needing to be removed. You could try writing a script using the Jira and Organization APIs to do this for you faster.

3. You install a marketplace app like Admin Automations to keep particular AD groups in sync with the default Atlassian groups. It’s the same solution as #2, but it’s automated.

It really comes down to how complex your project settings and global permissions are.

I hope that helps!

-Kieren

Co-Founder @ Admin Automations | Ex-Atlassian