Overview π₯
If the Privileged Users count on your Visual Insights dashboard is lower than expected, the most common cause is a dataset filter excluding certain users. Specifically, the Privileged Users widget relies on the modified dataset M365: Users, which frequently includes a Filter modifier applied to the Assigned Product field. This filter is designed to limit the data to users assigned specific products. However, if the filter does not encompass all possible product values or if it excludes users who currently have no product assigned, some privileged users will not appear in the widget.
This happens even though the source data for these users exists in the system. To resolve this issue, please review the filter settings on the Assigned Product field within the M365: Users dataset and ensure that it includes all relevant product values and accounts for users without assigned products. Adjusting the filter accordingly should result in a more accurate count of privileged users on your dashboard.
Why This Happens π€
The
M365: Usersmodified dataset uses a Filter modifier onAssigned Product.If not all product values are selected, users assigned to unselected products are excluded.
Some privileged users may also have no product assigned (they are privileged because of roles, not licenses). If the filter only allows users with selected products, users with blank Assigned Product will also be excluded.
Because the Privileged Users widget depends on this dataset, its count becomes smaller than the true privileged-user set.
Steps to Resolve π€©
Solution 1 : Edit the Modified Dataset Settings
Open Visual Insights
Go to Data Settings β Modified Filters
From the left menu choose Data Settings, then Modified Filters.
Edit the
M365: UsersDatasetOpen the Filter Modifier
Include All Assigned Products AND Users With No Product
In the filter editor, first ensure all available values for Assigned Product
To include the Users who do not have any assigned products but are Privileged, add an additional condition so the dataset also includes rows where
Assigned ProductIS BLANK.The logic must be an OR clause between the two conditions.
Save the modifier and dataset
Click Save and Close to apply the modifier. Click Save and Close again to update the dataset.
Wait for Sync and Verify
Allow a few minutes for the dataset to re-sync.
Refresh the Asset Inventory dashboard and confirm the Privileged Users widget shows the expected count.
Solution 2 : Disable the Modifier within Dataset settings
In Solution 1, at step 4, instead of editing the Modifier, choose the option to disable it entirely.
What to Expect After This Change π
Users with assigned products (all products you selected) will appear.
Users who donβt have any assigned product but are privileged due to role assignments will also be included because of the
IS BLANKcondition.The widget count should now align with the Microsoft 365 inspector or your role-based reports.
β
Extra Checks π
Confirm you edited the M365: Users dataset β not a copy or similarly named dataset.
Double-check that the two conditions are joined by OR. If the UI defaults to AND, users with blank Assigned Product will still be excluded.
Check Data Settings β Datasets for the Last Synced timestamp if results donβt appear immediately.
After the change, compare the updated widget numbers against the Microsoft 365 Inspector (or a manual export) to validate accuracy.
Contact Support π¨βπ»
If the issue persists after trying the above steps, please contact Liongard Support. When you open a support ticket, include:
Screenshot of the Filter modifier showing both conditions and the OR operator.
Screenshot of the
M365: Usersdataset name and its Last Synced timestamp.Dashboard screenshot showing the Privileged Users widget and its count.
Screenshot of the Privileged Users data (count) from the Liongard environment.
Any recent changes or the user who edited the dataset (if known).







