How Autodesk Uses Telemetry Data — And What It Means for Compliance

What LRT Telemetry Actually Collects

Autodesk's telemetry infrastructure — commonly referred to by the Licence Reporting Tool (LRT) that underpins it — is a continuous, automated data collection system embedded in Autodesk's product delivery infrastructure. It operates independently of whether a user is aware of it and transmits data to Autodesk's servers on every product session.

The data collected covers six primary categories: product identity (which Autodesk products are installed and their version/build), device identity (network hostname, machine GUID, and operating system), user identity (which Named User account authenticated to access each product), session data (timestamp, duration, and features accessed), licence claim data (how each session was authorised — Named User assignment, Flex token, or legacy serial), and network context (IP address and domain — relevant for identifying contractor access from non-corporate networks).

The combination of these data types is what makes LRT powerful as an audit instrument. It does not just show that a product was used — it shows exactly who used it, from what device, for how long, and whether that access was covered by a valid licence assignment. Discrepancies between what was used and what was licensed are directly visible in the data without any inference required.

How Autodesk Uses LRT Data in Audit Engagements

Autodesk's SAM (Software Asset Management) engagement programme operates on a signal-based model. Rather than conducting random audits, Autodesk's analytics infrastructure monitors LRT data for patterns that indicate compliance risk — and triggers SAM engagement letters when those signals reach a threshold.

The most common trigger signals are: product usage without a corresponding Named User assignment (indicating unlicensed access), usage of products outside the contracted scope of an existing agreement (indicating out-of-scope access), usage count materially exceeding contracted licence count over a sustained period, and entity event signals — public M&A announcements, corporate restructuring filings, or changes in LRT data patterns consistent with a combined or modified entity.

The SAM engagement letter — the formal notification that an audit is being initiated — is typically sent after Autodesk has already analysed the LRT data and established that a compliance gap exists. By the time the letter arrives, Autodesk's team has a preliminary quantification of the finding. This information asymmetry is one of the reasons organisations that conduct proactive LRT self-reviews fare significantly better in audit outcomes: they are not negotiating against evidence they haven't seen themselves.

In the audit engagement itself, Autodesk's team requests an LRT export covering the period under review — typically 12–24 months. This export is cross-referenced against the customer's Named User assignments, contracted product scope, and licence entitlement records. Gaps are quantified at list pricing as a starting point, then negotiated. For guidance on how to navigate this process, see our Autodesk Audit Defence service.

Using LRT as a Proactive Compliance Tool

The most strategically important insight about LRT is that the data Autodesk's audit team would request in an engagement is already available to the customer. Every organisation with Autodesk software deployed can access their own LRT data through the Autodesk Account portal or through the LRT interface in the Autodesk Desktop App. The question is whether they look at it before Autodesk does.

Organisations that conduct quarterly LRT self-reviews — comparing actual usage data against Named User assignments and contracted scope — identify compliance gaps as they emerge rather than after they have accumulated. This allows remediation at a fraction of the cost: a compliance gap identified through an internal review can be addressed by purchasing missing licences at current pricing. The same gap identified in an audit is quantified at list pricing, potentially includes retroactive exposure for the full period, and is negotiated from a position of weakness.

LRT as a Cost Optimisation Tool

Beyond compliance risk management, LRT data is the most accurate source of information available for Autodesk cost optimisation. The data answers questions that procurement and IT asset management teams cannot reliably answer any other way: which licences are genuinely in use, which Named Users have been inactive for extended periods, which products are only used by a small fraction of assigned users, and whether the current product mix matches actual usage patterns.

Named User dormancy is one of the most consistent findings in LRT-based licence reviews. In enterprise environments, 15–22% of Named Users typically have not authenticated to any Autodesk product in the preceding 90 days. These dormant assignments represent licences being paid for without any value being delivered. Quarterly LRT-based reclamation — identifying dormant users and returning their assignments to the pool — is one of the simplest and most consistent Autodesk cost reduction levers available.

Product utilisation depth is the second major insight. LRT records not just which products are accessed but how frequently and for how long. An organisation paying for 200 Revit licences where LRT shows 140 used more than once per month and 60 used fewer than 4 times per year has a clear signal: the 60 infrequent users may be better served by Autodesk Flex tokens rather than full Named User subscriptions, potentially saving $58,000–$85,000 annually on those seats alone.

LRT in Restricted and Air-Gapped Environments

Government, defence, and regulated industry environments frequently restrict outbound data transmission for security reasons — which raises the question of how LRT telemetry operates in these contexts. The short answer is that Autodesk's agreement terms still require accurate usage reporting, regardless of network architecture.

For air-gapped environments, Autodesk provides an offline LRT export capability — usage data is collected locally and exported on portable media for periodic submission. This self-reporting obligation is explicit in enterprise agreement terms, and Autodesk's audit team treats gaps in self-reporting with the same scrutiny as unexplained LRT data gaps in standard deployments. Organisations in restricted environments should ensure their IT teams understand the self-reporting obligation and have a documented process for periodic LRT export and submission.

Attempting to block LRT transmission as a compliance strategy — rather than as a security necessity — is specifically inadvisable. Organisations that block LRT without a documented security justification are in technical violation of their agreement terms, and when an audit is initiated, the absence of LRT data is typically resolved against the customer. Autodesk's approach in these cases is to assume the worst-case usage scenario and require the customer to disprove it. This is a significantly worse negotiating position than the data showing a known, bounded compliance gap. For guidance on managing LRT in restricted environments as part of your audit defence strategy, contact our team.

Building an Ongoing LRT Review Programme

An effective LRT review programme requires three things: access, cadence, and action. Access means ensuring that the designated Autodesk Account administrator and IT/SAM team have current credentials to the Autodesk Account portal and understand how to generate and interpret LRT exports. Cadence means committing to quarterly reviews as a minimum — not annual, and not "when we think about it." Action means that LRT findings generate documented remediation steps with owners and timelines, not just a record of observation.

The quarterly LRT review should produce a three-part output: a Named User reclamation list (dormant users to be deactivated), a compliance gap register (products in use without licence assignment, for immediate remediation), and a renewal intelligence brief (usage trends informing the next renewal negotiation — whether to increase, decrease, or restructure product scope).

This programme is not complex to run, but it requires discipline. The organisations with the cleanest Autodesk compliance profiles are not necessarily the ones that started with the cleanest estates — they are the ones that review their data regularly and act on what they find. If you want independent support establishing or running this programme, our team can provide an initial LRT baseline review and governance framework design as part of a broader engagement. See our Autodesk ITAM Maturity Guide for the full governance framework.

Related Insights