Uploaded image for project: 'Atlassian Guard'
  1. Atlassian Guard
  2. ACCESS-1497

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

    • 9
    • 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.

      At the moment, the Azure AD sync will use the Azure AD email address and the UPN as fallback for the synced Atlassian Account email address.

      SAML-SSO attribute setting in Azure AD allows to map the email address (unique user identifier) to certain attributes in Azure AD. User provisioning via SCIM also allows this.

      This can lead to duplicate accounts if the SAML-SSO attribute mapped is not the primary email as used by Azure AD sync.

      Suggestion
      To match Azure AD sync with SAML SSO and avoid duplicate accounts, allow the Atlassian Account email address to be mapped to an Azure AD attribute via Azure AD sync

          Form Name

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

            SET Analytics Bot made changes -
            Support reference count Original: 8 New: 9
            Nancy Lopez made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 987166 ]
            SET Analytics Bot made changes -
            Support reference count Original: 7 New: 8
            SET Analytics Bot made changes -
            Support reference count Original: 6 New: 7
            Neel Gandhi made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 967824 ]
            SET Analytics Bot made changes -
            Support reference count Original: 5 New: 6
            Holly Makris (Inactive) made changes -
            Status Original: Under Consideration [ 11774 ] New: In Progress [ 3 ]

            Per last comment: We will be adding the ability to sync user principal name (UPN) attributes as the primary identifier for users. This will be available by the end of 2024. We will update this ticket when this is available and provide links to support documentation.

            Holly Makris (Inactive) added a comment - Per last comment: We will be adding the ability to sync user principal name (UPN) attributes as the primary identifier for users. This will be available by the end of 2024. We will update this ticket when this is available and provide links to support documentation.
            Kat N made changes -
            Labels Original: guard-s8 New: RIBS-SHORT guard-s8

            We will be adding the ability to sync user principal name (UPN) attributes as the primary identifier for users. This will be available by the end of 2024. We will update this ticket when this is available and provide links to support documentation.

            Holly Makris (Inactive) added a comment - We will be adding the ability to sync user principal name (UPN) attributes as the primary identifier for users. This will be available by the end of 2024. We will update this ticket when this is available and provide links to support documentation.

              d056dd6d7b90 Holly Makris (Inactive)
              rmacalinao Ramon M
              Votes:
              26 Vote for this issue
              Watchers:
              23 Start watching this issue

                Created:
                Updated: