Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-15146

Entra ID Users adapter change: Ability to support Manager ,Department and other Important fields

XMLWordPrintable

    • 384

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

      Problem

      When using Data Manager Adapter Data Manager - Entra ID User Adapter to import users from Entra ID (Azure) to Assets , few fields like Manager, Department are not supported yet.

      These fields are Important for Assets to add Approvers and manager the users effectively.

      Suggested Solution

      Please add more attributes like Hire date, Company name, Status, employeeType, Extension Attributes 1-15, sponsors, company (critical for service desk operation that work with different companies), status, Manager, Department attributes as supported fields in Data Manager - Entra ID User Adapter

      Also, it would be best instead of adding individual attributes to allow the user to choose from ALL the attributes on user objects available.

      Why This Is Important

      This will provide important fields like Manager to use in Assets Automation etc.

      Workaround

      Either use CSV Imports or use App What data does the Assets - Microsoft Entra ID app import? to import Department and Manager attribute.

            [JSDCLOUD-15146] Entra ID Users adapter change: Ability to support Manager ,Department and other Important fields

            Martin T. added a comment -

            We would need the following essential fields to be imported from Entra ID User to Data Manager:

            • “On-premises sync enabled”
            • “On-premises domain name”

            Martin T. added a comment - We would need the following essential fields to be imported from Entra ID User to Data Manager: “ On-premises sync enabled ” “ On-premises domain name ”

            Isaac Moore added a comment - - edited

            This is not just an issue for the Entra ID User connector but also the Intune connector. There are multiple data source fields missing which I would consider essential to our operations.

            Isaac Moore added a comment - - edited This is not just an issue for the Entra ID User connector but also the Intune connector. There are multiple data source fields missing which I would consider essential to our operations.

            Timothy Brown added a comment -

            It would be nice to pull Employee ID, and Address data. Or at least some way to change the json to pull in more fields.

            Timothy Brown added a comment - It would be nice to pull Employee ID, and Address data. Or at least some way to change the json to pull in more fields.

            Arjun Vurtur Nagaraja added a comment -

            Also, it would be helpful if the groups of the users can be pulled in too.
            Groups, group owners and other data.

            Arjun Vurtur Nagaraja added a comment - Also, it would be helpful if the groups of the users can be pulled in too. Groups, group owners and other data.

            Aaron Geister_Sentify added a comment - - edited

            This needs to be included for many teams and businesses to actually use the data to connect specific function with in CMDB for approvals and change management etc. 
            Other connectors for asset can pull that data why wouldn't ADM be able to do this?

            Aaron Geister_Sentify added a comment - - edited This needs to be included for many teams and businesses to actually use the data to connect specific function with in CMDB for approvals and change management etc.  Other connectors for asset can pull that data why wouldn't ADM be able to do this?

            Andreas Krupp added a comment -

            Addition to "why this is important":

            • Static Adapters will never be able to keep up with the changes in all the other tools, they are connecting too
            • Therefore the solution must be more generic so that the Atlassian Team can focus on more and better functionality, and customers can focus on their data

            Andreas Krupp added a comment - Addition to "why this is important": Static Adapters will never be able to keep up with the changes in all the other tools, they are connecting too Therefore the solution must be more generic so that the Atlassian Team can focus on more and better functionality, and customers can focus on their data

              Unassigned Unassigned
              e8ddb9406228 Arvind Kishore
              Votes:
              46 Vote for this issue
              Watchers:
              29 Start watching this issue

                Created:
                Updated: