• Type: Suggestion
• Resolution: Unresolved
• Component/s: User Sync - Initial SCIM Setup
• Labels:

  None

[ACCESS-2041] Support additional attributes for Azure AD sync (Osync)

SET Analytics Bot made changes - 24/Jul/2025 4:03 AM

Support reference count

Original: 2

New: 3

Derrick Nguyen made changes - 23/Jul/2025 11:54 AM

Description

Original: h3. Problem Definition It is now possible to sync attributes such as *nickname* and *location* via SCIM: https://support.atlassian.com/provisioning-users/docs/sync-user-attributes-to-your-organization In the case of SCIM, it is possible to configure custom mappings, but in the case of Azure AD sync it is not h3. Suggested Solution Provide support for the *nickname* and *location*(basedIn) attributes for Azure AD sync h3. Why this is important Syncing additional attributes will help admins better manage their users   h3. Workaround No known workarounds aside from using SCIM

New: h3. Problem Definition It is now possible to sync attributes such as *nickname* and *location* via SCIM: https://support.atlassian.com/provisioning-users/docs/sync-user-attributes-to-your-organization In the case of SCIM, it is possible to configure custom mappings, but in the case of Azure AD sync it is not h3. Suggested Solution Provide support for the *nickname* and *location*(basedIn) attributes for Azure AD sync h3. Why this is important Syncing additional attributes will help admins better manage their users   h3. Workaround * Change to SCIM provisioning: [Switch from Azure AD for nested groups to SCIM|http://support.atlassian.com/provisioning-users/docs/switch-from-azure-ad-for-nested-groups-to-scim](nested group syncing not supported via SCIM) *OR* * Use the API: https://developer.atlassian.com/cloud/admin/user-management/rest/api-group-profile/#api-users-account-id-manage-profile-patch to update the "location" value - as of *July 2025*, user attributes can be updated via API even if the end user's Atlassian account is locked in the UI due to provisioning sync

SET Analytics Bot made changes - 02/May/2025 4:00 AM

Support reference count

Original: 1

New: 2

SET Analytics Bot made changes - 07/Mar/2025 4:00 AM

Support reference count

New: 1

Derrick Nguyen made changes - 22/Nov/2024 7:21 AM

Component/s

Original: IdP SSO - Google Cloud (G Suite) [ 53304 ]

Derrick Nguyen made changes - 22/Nov/2024 7:20 AM

Description

Original: h3. Problem Definition It is now possible to sync attributes such as *nickname* and *location* via SCIM: https://support.atlassian.com/provisioning-users/docs/sync-user-attributes-to-your-organization In the case of SCIM, it is possible to configure custom mappings, but in the case of Google sync it is not h3. Suggested Solution Provide support for the *nickname* and *location*(basedIn) attributes for Google sync h3. Why this is important Syncing additional attributes will help admins better manage their users   h3. Workaround No known workarounds aside from using SCIM

New: h3. Problem Definition It is now possible to sync attributes such as *nickname* and *location* via SCIM: https://support.atlassian.com/provisioning-users/docs/sync-user-attributes-to-your-organization In the case of SCIM, it is possible to configure custom mappings, but in the case of Azure AD sync it is not h3. Suggested Solution Provide support for the *nickname* and *location*(basedIn) attributes for Azure AD sync h3. Why this is important Syncing additional attributes will help admins better manage their users   h3. Workaround No known workarounds aside from using SCIM

Derrick Nguyen made changes - 22/Nov/2024 7:19 AM

Link

New: This issue is cloned from ACCESS-2040 [ ACCESS-2040 ]

Derrick Nguyen created issue - 22/Nov/2024 7:19 AM