• State Verified Answer
  • Replies 3 replies
  • Subscribers 113 subscribers
  • Views 188 views
  • Users 0 members are here
Options
Related

Matching users failure on 365 tenants

john wagenman
14 days ago

After adding our 365 tenants and performing successful discovery, we attempted to match one user by DisplayName as a test and it failed.

We also tried doing a CSV mapping by UPN which also failed. There doesn't appear to be any reason listed and the diagnostics only shows some simple data like the Org, Project and task ID.

I've gone over our consents and they appear to be in order. I'm not quite sure what else to check.

Was not able to find a topic in the forum that helped.

  • 0 14 days ago

    Hello John, 

    There could be multiple reasons for the match to have no succeeded but under normal circumstances the events for the task would give some additional details such as unable to match due to multiple objects with the same email address, not finding an object by identifier in the csv etc.. 

    The copy diagnostics button will copy the information that our support team requires to pull the task events and review what happened during the task. Under the Copy Diagnostic button you should see Events ().  If you click this it will bring you to the Events tab with all the details for what took place during the tasks operation.  

    If the events are not giving a clear picture on why the mapping is failing, please open a support case and one of our support engineers will be able to assist.

    support.quest.com/create-service-request

  • +1 7 days ago

    The problem ended up being on the back end. Somehow the discovery did not completely finish despite populating the accounts. Deleting all the accounts from the discovery and redoing the discovery solved these issues.

  • 0 6 days ago in reply to john wagenman

    Thank you for sharing what steps had been taken to resolve the issue.