Autodesk LRT: What the License Reporting Tool Actually Does

What the LRT Is and Why It Exists

The Autodesk License Reporting Tool is a network-connected component embedded in Autodesk's subscription software products. It was introduced as part of Autodesk's transition from perpetual to subscription licensing — a commercial and compliance architecture shift that began in earnest in 2021 and was substantially complete by 2023.

LRT serves a dual commercial purpose for Autodesk: it enables the Named User licensing model (by tracking which specific users are consuming which products) and it provides Autodesk's compliance function with continuous telemetry data without requiring a formal audit notification to initiate data collection. By the time an audit letter arrives at an enterprise, Autodesk's compliance team may have 12–24 months of LRT data already analyzed.

The tool operates as a background service on every device where Autodesk subscription software is installed. It reports: product installations and versions, user authentication events (Named User logins), launch events by product, session duration data, and geographic location of usage. All of this data is transmitted to Autodesk's cloud infrastructure and aggregated against the customer's account record.

What LRT Reports to Autodesk

The specific data points transmitted by LRT are more extensive than most enterprise IT teams realize. Autodesk's compliance team receives a continuous feed that includes:

• Installation records: Every device where Autodesk software is installed, with product name, version number, and installation date.
• Named User authentication: Every user who authenticates to an Autodesk product using their Autodesk account, with timestamp and product.
• Session data: Duration and frequency of product usage by user and device.
• Geographic data: IP address-derived location of usage — relevant for multi-entity or global deployments where geographic scope restrictions apply.
• Version history: Historical record of which major and minor versions have been active on each device — used to identify potential perpetual/subscription overlap.

This data is cross-referenced against the customer's contracted Named User list and seat count. Discrepancies between LRT-reported users and the contracted user list generate compliance flags that are reviewed by Autodesk's compliance team on a regular cycle.

How LRT Overcounts — The Four Mechanisms

LRT is not a precise compliance measurement tool. It is a usage telemetry system designed primarily for product analytics and secondarily repurposed for compliance enforcement. The architecture creates four systematic overcounting mechanisms:

Mechanism 1: Background Service Processes

Autodesk software installs multiple background services that interact with the LRT system even when the application is not open. Desktop Connector, Autodesk Access, and several product-specific update services authenticate to Autodesk's servers using the last authenticated user's credentials — even when that user is not actively using the software. This creates launch event records that appear as active usage in LRT's compliance reporting.

Across our audit engagement portfolio, background service processes account for 8–12% of total LRT-reported usage events in typical enterprise deployments. In deployments with aggressive desktop connector configurations or large Vault/BIM 360 integrations, this figure can exceed 18%.

Mechanism 2: Inactive User Detection Gaps

The LRT's definition of an "active user" is anchored to authentication events — any Named User who has logged into any Autodesk product in the reporting period appears as an active user. This creates a systematic gap between LRT-reported Named Users and genuinely active users, because LRT has no mechanism to distinguish between:

• Users who have changed roles and no longer need Autodesk software but have not had their assignment reclaimed
• Users who accessed the software once for a peripheral task (reviewing a file, attending a collaboration session) but are not regular users
• Users who have left the organization but whose accounts have not been deactivated in Autodesk's system

Our data shows the average enterprise has 23% of its LRT-reported Named Users in one of these inactive or marginal categories. These users represent real compliance exposure in LRT's reporting but do not represent genuine need for dedicated Named User seats.

Mechanism 3: Shared Workstation Attribution

In manufacturing and AEC environments, shared workstations — CAD stations used by multiple users on different shifts — are common. LRT reports each unique Named User who accesses a shared workstation as a separate user event. In a deployment with 50 shared workstations and three-shift rotation, LRT may report 150 Named Users where only 50 concurrent seats are actually in use at any given time.

Autodesk's Named User licensing model does not explicitly prohibit shared workstations, but LRT's counting methodology treats each Named User authentication as a seat consumption event — creating an apparent compliance gap that does not reflect actual concurrent deployment.

Mechanism 4: Version Misclassification

Enterprises that migrated from perpetual to subscription licensing frequently have both old perpetual versions and current subscription versions installed on the same device estate. LRT reports the subscription software as active Named User consumption — correctly — but may also flag the perpetual version as an active installation, creating an apparent dual-consumption record. In many cases, the perpetual software has not been launched; it is simply installed on the device pending decommissioning.

Overcount Mechanism	Typical Frequency	Avg Named User Overcount	Challengeability
Background service processes	89% of deployments	8–12%	High (system logs)
Inactive user detection gaps	100% of deployments	15–25%	High (identity system)
Shared workstation attribution	Mfg/AEC (67%)	Varies by shift model	Medium (operational evidence)
Version misclassification	Post-migration (78%)	5–15% where applicable	High (installation logs)
Geographic attribution errors	Global deployments (44%)	3–8%	Medium (network logs)

LRT Data in Audit Proceedings

When Autodesk's compliance team presents preliminary findings, the document is constructed almost entirely from LRT data. The findings will reference specific users, dates, and products with apparent precision. This precision is misleading — it reflects LRT's data collection accuracy, not the accuracy of the compliance assessment. LRT can accurately record that a specific user authenticated to AutoCAD on a specific date; it cannot accurately determine whether that user had a valid Named User assignment at that time, whether the authentication was from a background service, or whether the user has since been deactivated.

Enterprises entering audit proceedings without an independent entitlement baseline face a fundamental evidentiary asymmetry: Autodesk has months of LRT telemetry, and the enterprise has the contract. The contract establishes entitlement, but it does not establish what was deployed — and that deployment question is where LRT's overcounting creates inflated findings.

Building an Independent Entitlement Baseline

The most effective counter to LRT-inflated findings is an independent entitlement baseline — a documented record of your actual Named User assignments, active deployment count, and product landscape built from your own ITAM tooling and identity management systems, not from LRT.

A complete independent baseline requires four data sources:

1. ITAM deployment scan. Run a software inventory scan using your ITAM tool (ServiceNow, Flexera, Snow, or equivalent) to identify every device with Autodesk software installed, including version and installation date. This is your independent installation record.

2. Identity management export. Pull a current export from your identity provider (Active Directory, Okta, Azure AD) of all users with Autodesk product licenses assigned, including account status, last login date, and department. This identifies your active user universe independent of LRT.

3. Autodesk admin console data. Export your Named User assignments from Autodesk's Account Portal. This is Autodesk's own record of your contracted assignments — distinct from LRT telemetry. Discrepancies between the admin console and LRT findings are directly challengeable.

4. Employment records reconciliation. Cross-reference your Named User list against current employment records to identify departed employees whose Autodesk accounts have not been deactivated. These are your highest-value reclamation targets — and documenting the reclamation action with a timestamp creates a clear audit record.

The resulting baseline — ITAM deployment data + identity management user list + admin console assignments + employment verification — produces an independent view of your actual entitlement position. This is the data you bring to audit proceedings, not LRT data.

Using Your Baseline in Audit Proceedings

When Autodesk presents preliminary findings based on LRT data, your challenge strategy maps each LRT-reported "non-compliant" user against your independent baseline. Users appearing in LRT but absent from your independent active user list fall into one of four challengeable categories:

• Background service process attribution (no human user involved)
• Inactive user (employment ended, role changed, or account not used in 90+ days)
• Shared workstation — authentication count exceeds concurrent usage
• Version overlap — perpetual installation counted against Named User entitlement

Each category requires different documentation. Background service challenges require system logs showing the service account activity. Inactive user challenges require identity system data showing account status and last authentication date. The Autodesk Audit Rights white paper provides specific guidance on the evidence standards required for each challenge category.

Enterprises that execute this challenge process systematically achieve an average 35% reduction in preliminary findings. For an end-to-end walkthrough of the challenge and settlement process, the Complete Guide to Autodesk Software Audits covers the full proceedings structure from notification through settlement.