Please add "Based in" for mapping with Azure AD / SCIM provisioning.

Hi everyone,

We noticed that this improvement wasn't delivered for a while and I am happy to share with you one more solution that may help you to achieve this goal (or complementary need of your company) - MindPro Sync, a new Marketplace app, where you can integrate OKTA, Azure AD, or OneLogin with Jira and JSM. 

With this integration, you can:

• Connect JIRA and JSM with your favorite Identity Provider (OKTA, Azure, or OneLogin);
• Select and map user attributes to be displayed in Jira issues or JSM requests (and portal), making ticket resolution faster;
• Use user attributes information from read-only custom fields to create JQL queries, filters, dashboards or to connect with other apps;
• Choose to display data for the issue Reporter or Assignee;
• Show user reporting hierarchy in Issues and JSM requests to facilitate escalation and approvals;
• Automatically assign approvers based on user hierarchy.

Available on Atlassian Marketplace for 30-days free: MindPro Sync

Check the app documentation: https://mindpro.atlassian.net/wiki/spaces/MAP/pages/1700298761/Mindpro+Sync 

Learn more at: mindproapps.com

Eduardo, 

MindPro - Atlassian Marketplace Partner

Thanks everyone for watching and commenting on this ticket. As part of an initiative to better consolidate customer feedback, we are closing this ticket as a duplicate. Please vote, watch and comment on ACCESS-822 going forward.

+1 on any attribute in AAD should be possible to map.

Phone number also is required for some of our customers. 

My 2 cents here:

• in an ideal world, we should allow to map any attribute that is present in the active directory, in this way we only synchronize what is strictly required.
• Also think different: instead of synchronizing, it would be perfect, if possible, that Access queries the AD tenant to retrieve the information on the fly, in this way Atlassian does not need to store this data, optimizing the infrastructure and reducing the synchronization activity. I am sure that while we need to retrieve the data profile - this activity is not constantly done to justify the whole dataset to be stored at Atlassian's infrastructure. 
• This could be an Atlassian Access Premium option only for those customer that need the feature.

Best regards

Claudio Ombrella
co-CEO Digilac Sàrl - Atlassian Silver Solution Partner
www.digilac.ch 

any attribute, especially Manager

Another vote for manager and office location (among other attributes).

+1 for manager and office location

Would be very helpful to have this - and an "other" email field 

+1 for a Location, address and the AD "Office" field