Overview
The Microsoft Entra Users Collector retrieves user and licence allocation information from Microsoft Entra using the Microsoft Graph API.
This collector provides visibility into user accounts and assigned licences, enabling organisations to validate subscriptions, allocate costs, and reconcile licence usage within Varibill.
The collector retrieves unrated allocation data, meaning no monetary values are supplied by the source system. Pricing and billing calculations are applied within Varibill based on configured contracts and pricing rules.
This is a discrete (snapshot) collector, meaning each execution retrieves the current state of users and licence assignments at the time of collection rather than accumulating historical records.
For general instructions on creating and running Source Collectors, see: Varibill Cloud Source Collectors - Setup and Configuration Guide.
Collector Summary
| Source Collector Name | Entra Users - Version 6.0 |
| Collection Behavior | Discrete |
| Data Rating Model | Unrated |
| Vendor Name | Microsoft |
|---|---|
| Product | Microsoft Entra (Azure Active Directory) |
| Purpose | The Microsoft Entra Users 6.0 Source Collector retrieves user licence allocation data from Microsoft Entra for billing and validation within Varibill. |
Data Collected
The Microsoft Entra Users 6.0 collector retrieves unrated user licence allocation data from Microsoft Entra. This includes individual user allocation data registered to Entra licences per user.
Snapshot Collection Behavior
The Microsoft Entra Source Collector is a discrete collector, meaning it captures data as a point-in-time snapshot of the current state within Microsoft Entra.
This means the collector does not retrieve historical licence changes from the past. Instead, each execution captures the licences and assignments that exist at the moment the collector runs.
Over time, repeated executions build a timeline of licence activity. By comparing snapshots between runs, Varibill can detect:
New licences assigned
Licences removed
Changes in user license tier registry assignments
Because historical licence events are not retrieved from Microsoft Entra, it is recommended that the collector runs on a regular schedule (we recommend daily) to ensure accurate tracking of licence changes.
How Billing Is Derived
Billing is calculated from the accumulated snapshots collected over time.
For example:
If a licence is assigned to a user today, the next collector run will detect the new licence and billing can begin from that point.
If a licence is removed, the following snapshot will detect its absence and billing can stop accordingly.
This process enables Varibill to produce accurate billing timelines without requiring historical data extraction from Microsoft systems.
Important! The Entra Users 6.0 collector reflects the state of Microsoft Entra at the time it runs. More frequent execution improves billing accuracy for environments with frequent licence changes.
Prerequisites
Before configuring this collector, you must:
- Create an Application Registration in Microsoft Entra
- Configure the required Microsoft Graph API permissions
- Grant Admin Consent for the configured permissions
- Create a Client Secret
- Capture the following values:
- Tenant ID
- Client ID (Application ID)
- Client Secret
Configuration Parameters
| Parameter | What it is | Where to find it |
|---|---|---|
| Entra Tenant ID | Identifies your Microsoft Entra tenant. | Azure Portal → Entra ID → Overview → Tenant ID |
| Entra Application (client) ID | Identifies the application registration used for authentication. | Azure Portal → App registrations → Your app → Overview → Application (client) ID |
| Entra (client) Secret Key | Credential used by Varibill to authenticate against Microsoft APIs. | Azure Portal → App registrations → Your app → Certificates & secrets → Client secrets |
Microsoft Entra References
The following resources may assist with locating values or configuring your Microsoft Entra application registration.
Microsoft Documentation (External)
- Where to find your Microsoft Entra Tenant ID
- How to register an application in Microsoft Entra to obtain an Application (client) ID
- How to create a Client Secret
- How to grant Admin Consent for permissions
Configuration Steps
Step 1: Prepare Microsoft Entra
- Create an application registration in Microsoft Entra
- Configure the required API permissions for the app registration
- Grant Admin Consent for the configured permissions
- Create a Client Secret
- Copy the Tenant ID, Client ID, and Client Secret
Step 2: Configure the Collector in Varibill
- In the Varibill Client Application, open the Source Collector configuration screen
- Enter the captured values:
- Tenant ID
- Client ID
- Client Secret

- Save the collector configuration
Step 3 — Run the Collector
Run or schedule the collector according to your standard Source Collector process. For detailed execution steps, see: Varibill Cloud Source Collectors - Setup and Configuration Guide.
Troubleshooting
If the collector fails to connect to Microsoft Entra, verify that:
- The Tenant ID is correct
- The Client ID is correct
- The Client Secret is valid and not expired
- Admin Consent has been granted
Related Documentation
- Introduction to Varibill Cloud Source Collectors
- Varibill Cloud Source Collectors - Setup and Configuration Guide
- How to Add a New Source Collector
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article