jordan.tait

How the Office 365 Connector Links Users

Discussion created by jordan.tait on Jun 27, 2019
Latest reply on Jun 27, 2019 by kishan.pant@chemtrolsinfotech.com

Applicable to the following Snow versions:

Snow License Manager 8.1 or above
Snow Integration Manager 5.3 or above

Snow Inventory Server 5.x or above

 

Please use the information available in this article to help understand what data is gathered via AD Discovery for Users
as well as the Office 365 connector. This will also provide an explanation if user linkage isn’t as high as expected within
Snow License Manager.

 

HOW THE OFFICE 365 CONNECTOR WORKS WHEN GATHERING DATA:

 

  • When AD discovery of users is enabled, the Inventory Server extracts information from Active Directory.
    This information includes the AD ObjectID, the primary e-mail address of the user, and the User Principal
    Name (UPN).
  • From the Microsoft Office-365 portal, the Office 365 Connector extracts UPN, ObjectID, and other e-mail
    addresses.
  • The linking required to create the connection between users in Office 365 and SLM occurs when the
    connector information is imported to SLM.

 

USERS WILL BE MARKED AS NOT LINKED IF:

 

  • User e-mail addresses have not been imported manually into SLM, which is mandatory for Inventory
    Server 3.
  • AD discovery of users is disabled for Inventory Server 5/6 or the Office 365 portal is not synchronised with
    the organisation's Active Directory.
  • The user doesn't exist in Snow License Manager. For example, the user's computer is not being
    inventoried because they’re a consultant or using a BYOD, etc…

 

THE USERS LINKING ORDER IS AS FOLLOWS:

 

  • It will try and match on the unique Object ID generated by Active Directory and present in Office 365 if it
    is synchronized with AD.
  • If this fails to find a match, it will try to match the AD primary email address to the Office 365 UPN (User
    Principle Name) or sign-in name.
  • If either of these are unavailable, e-mail addresses will need to be manually imported into Snow License
    Manager.

Outcomes