[ACCESS-1560] Allow custom attribute mapping for Azure AD sync - Create and track feature requests for Atlassian products.

Support reference count:
28
Current Status:

Hide

Update December 17, 2024

We are happy to let you know that UPN sync for Entra is now available! We have rolled out to 50% with full launch by the end of this week.

You can find more information here:

https://support.atlassian.com/provisioning-users/docs/set-up-sync-settings/

https://support.atlassian.com/security-and-access-policies/docs/configure-saml-single-sign-on-with-an-identity-provider/

Please leave comments on this ticket with any questions or clarifications needed in the support documentation, we will make sure to address them.

Thank you!

Show
Update December 17, 2024 We are happy to let you know that UPN sync for Entra is now available! We have rolled out to 50% with full launch by the end of this week. You can find more information here: https://support.atlassian.com/provisioning-users/docs/set-up-sync-settings/ https://support.atlassian.com/security-and-access-policies/docs/configure-saml-single-sign-on-with-an-identity-provider/ Please leave comments on this ticket with any questions or clarifications needed in the support documentation, we will make sure to address them. Thank you!
Feedback Policy:

Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

Currently the mapping can't be customized.
Limitations of Azure AD for nested groups

It would be great if it can be customized like SCIM integration.

is duplicated by

ACCESS-1358 Make it possible to change the attribute mappings with Azure OSync

is related to

ACCESS-1497 Allow the Atlassian Account email address to be mapped to an attribute via Azure AD sync

mentioned in: Page Loading...; Page Loading...; Page Loading...; Page Loading...

(1 mentioned in)