Skip to main content

Best practices for Azure AD Discovery integration

This section describes some best practices for a seamless integration with the Azure AD Discovery connector.

Azure AD user consolidation with Inventory Agent users​

The Azure AD connector has the ability to report and retrieve both on-prem synched users and Cloud-only users to Snow Inventory, to display in Snow License Manager. However, a character match is necessary to merge these users with the users from other sources in the Snow Inventory Server/Snow License Manager. Consequently, to avoid creating duplicate data when managing the cloud-only users from this connector in comparison to the agent data, it is recommended to do the following:

  1. In the Cloud-only users section of the connector, ensure that the Domain matches the domain of the agent username: euse \ user.

  2. In the Cloud-only users section of the connector, ensure that the Azure AD DisplayName matches the account name of the agent username: euse \ user.

Synchronizing the naming conventions between the OS account names and the Azure AD display names is necessary to produce a match in this way.

Azure AD user linking with Adobe and M365 Cloud users​

To allow the possibility of linking the Azure AD users with Adobe or M365 SaaS users, ensure a matching UserPrincipalName.

Using the Snow Inventory Extractor tool​

To review the resulting data that comes from the Azure AD discovery connector before exporting it to the Inventory Server, do the following:

  1. In your Snow Integration Manager instance, select the Inventory file handling and then select Save to local Inventory server.

  2. Browse the desired destination folders for your incoming inventory and discovery files.

  3. Perform the steps required for a manual aggregation of the Azure AD connector. See Configure the Azure AD Discovery connector.

  4. Using the Snow Inventory Extractor tool, open the resulting snowpack. For information on how to download and use the tool, refer to Snow Inventory File Extractor tool on Flexera Community. You must sign in to Flexera Community to access this article.