Skip to main content

How To Set Up and Use User Discovery

Written by Itamar Rotem

Faddom connects to your Active Directory domains and Microsoft Entra ID tenants to populate the User Inventory, allowing you to identify which users are accessing which servers and assisting with AD management. The interface lets you view your groups and their members while highlighting any empty groups. This functionality helps streamline Active Directory management by facilitating group cleanup and offering valuable insights such as identifying the top users per server and tracking which users are accessing your applications via the Client icon on maps.

Active Directory only: To use this feature, Faddom requires access to your Active Directory. If Faddom is deployed on Linux (via OVA or the Cloud Marketplace), a Windows Proxy is required to perform this task. Follow the guide How to Setup the Faddom Proxy to configure this. This step must be completed before configuring the Active Directory connection. If you already have a proxy set up for another feature such as Software Discovery, you can use the existing proxy without needing an additional one.

Setting Up Discovery

  1. Navigate to Settings > User Discovery
    ​​


    ​

  2. Click Add Domain or Tenant. For Microsoft Entra ID, see Setting Up Microsoft Entra ID below.
    ​

  3. Add the required details. You will need to do this per domain if you have multiple domains.
    ​

The user account you provide needs to be a member of the Event Log Readers Group, as Faddom gathers information via the AD Event Log. Protected Accounts cannot be used due to Microsoft restrictions, even if the account is a Domain Administrator.

When configuring the domain, you can enable Detect DCs Automatically to have Faddom resolve the domain name and get a list of domain controllers. Alternatively, you can specify which domain controllers to connect to manually. Toggle Enable Discovery on to populate the user data.

Discovery Schedule

You can configure when User Discovery runs by configuring the User Discovery entry in Settings > Configuration > Scheduler. Faddom supports time-based intervals including every 10 minutes, 30 minutes, or custom intervals. This is particularly useful in environments where Active Directory logs are wiped frequently, allowing you to capture user activity before the logs are cleared.

For Active Directory, ports 135 and 445 need to be opened from the Faddom proxy to the domain controllers. For more information, see What ports need to be open for Faddom to function?

Once added, you will see a list of configured domains. You can use the Edit icon to modify the details or the Delete icon to remove the connection.

To collect live user login and DNS data directly from your Active Directory servers, you can also install the Faddom Event Log Forwarder. See Setting up the Faddom Event Log Forwarder for details.

Setting Up Microsoft Entra ID

Available from 2026.3

Faddom reads users, groups, admin roles and last sign-in times from Microsoft Entra ID through Microsoft Graph. Optionally, it also reads which Azure VMs users logged into, from Log Analytics.

Before you start

Create an Azure credential under Settings > Data Sources > Azure. It can be one of two types:

  • Use Azure Access Key: an app registration with a client secret. Works with any Faddom proxy.

  • Use Azure Managed Identity: works only when the Faddom proxy runs on an Azure VM that has the identity attached. For a user-assigned identity, also enter its Client ID.

Required permissions

Permission

Type

Needed for

User.Read.All, GroupMember.Read.All

Microsoft Graph application permission

Users and groups (required)

RoleManagement.Read.Directory

Microsoft Graph application permission

Admin users by directory role (optional)

AuditLog.Read.All

Microsoft Graph application permission

Last sign-in (optional, requires Entra ID P1 or P2)

Organization.Read.All

Microsoft Graph application permission

Tenant name and domains (optional)

Log Analytics Reader

Azure role on each workspace

VM logins (optional)

When an optional permission is missing, discovery still runs:

  • Without RoleManagement.Read.Directory, admin users are found by admin groups.

  • Without AuditLog.Read.All, Last Login comes only from VM logins.

  • Without Organization.Read.All, domains are taken from the users' sign-in names.

Granting the permissions with an app registration

  1. In the Azure portal, open Microsoft Entra ID > App registrations > your app > API permissions > Add a permission > Microsoft Graph > Application permissions. Don't choose Delegated.

  2. Add the permissions you need, then click Grant admin consent. This requires a Global Administrator or Privileged Role Administrator.

  3. Note the client secret's expiry date. When it expires, discovery stops until you update the secret in the Azure credential.

Granting the permissions with a managed identity

Graph permissions can't be granted to a managed identity in the Azure portal. A Global Administrator or Privileged Role Administrator runs this once in Azure Cloud Shell (PowerShell), using the identity's Object (principal) ID. Remove any optional permissions you don't want.

Connect-MgGraph -Scopes "Application.Read.All","AppRoleAssignment.ReadWrite.All" $miId  = "<OBJECT-ID-OF-THE-MANAGED-IDENTITY>" $graph = Get-MgServicePrincipal -Filter "appId eq '00000003-0000-0000-c000-000000000000'" foreach ($perm in 'User.Read.All','GroupMember.Read.All','RoleManagement.Read.Directory','AuditLog.Read.All') {   $role = $graph.AppRoles | Where-Object { $_.Value -eq $perm -and $_.AllowedMemberTypes -contains 'Application' }   New-MgServicePrincipalAppRoleAssignment -ServicePrincipalId $miId -PrincipalId $miId -ResourceId $graph.Id -AppRoleId $role.Id }  # Check: lists the Graph permissions the identity now has Get-MgServicePrincipalAppRoleAssignment -ServicePrincipalId $miId |   ForEach-Object { $id = $_.AppRoleId; ($graph.AppRoles | Where-Object { $_.Id -eq $id }).Value }

To check in the portal, open Entra ID > Enterprise applications, set the filter to Application type = Managed Identities, open the identity, then Permissions.

Assign Azure roles (Log Analytics Reader, Reader) as usual: on the resource, open Access control (IAM) > Add role assignment > Members > Managed identity.

A user-assigned identity is recommended. You grant its permissions once, and you can attach it to any proxy VM later. A system-assigned identity is deleted with its VM.

Note: A VM can keep using its old managed identity token for up to 24 hours after permissions are granted. To apply them immediately, stop (deallocate) and start the VM.

Adding the tenant in Faddom

  1. Go to Settings > User Discovery > + Add Domain or Tenant and choose Microsoft Entra ID.

  2. Select the Azure credential. To add or edit credentials from here, click Manage Azure credentials. Then select the proxy. For a managed identity, choose the proxy that runs on the VM with the identity.

  3. Make sure Enable Discovery is on, then click Save. Faddom checks access and names the tenant after its primary domain.

  4. Click Run Now, or wait for the next scheduled User Discovery.

Admin users: Entra ID users count as admins when they have one of the roles in the Entra ID admin roles parameter, under User Discovery parameters. By default these are Global Administrator, Privileged Role Administrator, Privileged Authentication Administrator and Security Administrator. Only active, tenant-wide role assignments count. PIM-eligible assignments and roles scoped to administrative units don't.

Collecting VM logins (optional)

  1. Run Azure discovery first. Logins are only shown for VMs that Faddom has discovered.

  2. On each VM, install the Azure Monitor Agent and add a data collection rule that sends sign-in events to a Log Analytics workspace:

    • Linux: Syslog, facilities auth and authpriv (LOG_AUTH, LOG_AUTHPRIV), level Info or higher.

    • Windows: Security events (SecurityEvent table), including event ID 4624.

  3. Give the Azure credential the Log Analytics Reader role on the workspace.

  4. In Faddom, edit the tenant, turn on Collect VM Logins, and enter the workspace ID in Log Analytics workspace IDs, one per line. Use the GUID from the workspace's Overview page, not the workspace name.

Only users who log in with their Entra ID accounts are shown. On Linux that means Microsoft Entra login, for example with az ssh vm. Users need the Virtual Machine User Login or Virtual Machine Administrator Login role. Local accounts such as azureuser are not shown.

The first sync reads the last 24 hours, and later syncs continue from the previous one. The agent doesn't send events from before it was installed. New logins appear in the workspace after about 5 to 10 minutes.

Network

The proxy needs outbound HTTPS (443) to:

  • login.microsoftonline.com: sign-in with an app registration

  • graph.microsoft.com: users, groups, roles, sign-ins

  • api.loganalytics.io: VM logins

  • management.azure.com: Azure discovery

With a managed identity, the proxy also gets tokens from 169.254.169.254 on the VM itself. Faddom always connects to that address directly, never through a configured network proxy.

Troubleshooting

  • "Microsoft Graph denied access": a required permission or admin consent is missing. For a managed identity, see the 24-hour note above.

  • "Could not sign in to Entra ID": check the tenant ID, client ID and secret, and whether the secret has expired. For a managed identity, check that the proxy runs on the VM with the identity and that the Client ID is correct.

  • "No access to Log Analytics workspace ...": add the Log Analytics Reader role. New role assignments can take a few minutes to apply.

  • "Log Analytics workspace ... was not found": enter the workspace ID (GUID), not the name.

  • Last Login is empty: add AuditLog.Read.All. This requires Entra ID P1 or P2.

  • Admin Users count looks wrong: adjust the Entra ID admin roles parameter.

  • No VM logins: check that:

    • the VM was discovered;

    • users logged in with Entra ID accounts;

    • the agent and data collection rule send to the workspace;

    • the logins are less than 24 hours old (first sync).

Limitations

  • One managed identity reads only the tenant its VM belongs to.

  • Guest users are listed, but without an email unless one is set on the account.

  • Entra ID sign-in records don't say which VM a user logged into, so VM logins come only from Log Analytics.

Viewing the Results

Inventory

You can see users and groups in the Faddom Inventory by selecting Users or Groups and opening the properties of the relevant Active Directory object. Expand groups to see the users in each group, and click on a user to see which other groups they belong to. Faddom also shows you which users have higher permissions (members of admin groups in Active Directory, or admin directory roles in Entra ID) as well as any empty groups in your AD.

Search

You can use the Search function to search by user. Enter a username and it will begin to autofill. Selecting a username will show which servers and applications that user has accessed, as well as when the login occurred.

Server Properties

You can also see user information by navigating to the Security tab in Server Properties. Click on a server from a map, search, or properties icon from any list view. Expand the properties and click on the Security tab to view the Security Dashboard for that server. You will see a list of users, and clicking on one will open the User Profile.​

User Profile

The User Profile contains two tabs. User Activity shows the applications and servers the user accessed. User Details shows the details recorded in Active Directory, including name, email address, location, groups, and manager.

Tracking user changes

Faddom monitors your Active Directory environment and tracks changes to users and groups, giving your IT and security teams visibility into evolving user access.

Recently detected changes

The "Users & Groups" dashboard in the Inventory displays a "Recently Detected Changes" counter. Selecting it opens a filtered view showing all detected changes, including the user name, account, groups, event type such as group membership changes, event date, and last login. You can filter this view by time period.

User inventory columns

The users list now includes two additional columns:

  • First Seen - the date Faddom first detected the user in your environment

  • Last Login - the date and time of the user's most recent login

Notifications for user changes

Faddom generates notifications when users become inactive. To receive alerts, set up a notification subscription and select Inactive User from the subscription options.

Did this answer your question?