- Autodesk retired the multi-user (network/concurrent) license model in 2021, requiring all subscription-based access to use Named User licensing—one license per uniquely identified individual.
- The transition created audit exposure for organizations that didn't fully update their license assignment practices: systems with Autodesk software installed but without proper Named User assignment generate LRT compliance signals.
- Organizations retaining perpetual licenses from before the transition have limited continuing rights—perpetual licenses do not convert to subscription access, but maintenance plan holders retained version entitlement through their last paid maintenance period.
- 47% of enterprise organizations have measurable compliance gaps traceable to the multi-user to Named User transition—most are addressable through an independent entitlement baseline and governance updates.
Named User vs Multi-User: Core Differences
Understanding the fundamental architecture difference between these two models is essential to assessing your current compliance posture. Multi-user (also called "network" or "concurrent") licensing operated on a check-out/check-in model: a pool of licenses sat on a license server, and any user on the network could check out a license when needed, with the total concurrent users capped at the license count. Named User licensing eliminates the pooling concept entirely—each license is permanently assigned to one specific individual.
Legacy Multi-User Model (pre-2021)
Named User Model (current)
The compliance implications of this change are profound. Under multi-user licensing, having 100 licenses and 200 users was compliant as long as no more than 100 users were simultaneously active. Under Named User licensing, having 100 licenses and 200 users is non-compliant regardless of simultaneous usage—each of the 200 users requires their own Named User license.
How the 2021 Transition Created Compliance Gaps
The multi-user to Named User transition was commercially structured to accelerate Autodesk's revenue: by eliminating the efficiency of pooled concurrent licensing, the transition increased the number of licenses most large organizations needed to purchase. Organizations that previously managed 50 concurrent users across 150 actual users with 50 network licenses now required 150 Named User licenses—a 3× increase in license count for the same user base.
The compliance gaps created by the transition fall into four primary categories, each of which represents a distinct audit exposure type:
| Gap Type | How It Arises | Frequency | Avg Finding Value (per 100 users) | Challenge Success Rate |
|---|---|---|---|---|
| Dual-count overlap | Users retained perpetual license access AND subscription assignment simultaneously | 43% of organizations | $62K–$140K | 71% with documentation |
| Inactive user carry-over | Named User assignments not updated to remove former employees and inactive staff | 78% of organizations | $46K–$120K | 88% with HR records |
| Deployment without assignment | Software installed on systems without corresponding Named User assignment created | 52% of organizations | $38K–$90K | 82% with ITAM evidence |
| Assignment lag | New users deployed software before Named User assignment was formally created in Admin Console | 64% of organizations | $18K–$45K | 76% with deployment records |
Perpetual License Rights After the Transition
Organizations that held perpetual licenses under maintenance plans before 2021 retained important continuing rights—but these rights are frequently misunderstood and sometimes asserted beyond their actual scope, creating compliance exposure in the opposite direction.
The key principle: perpetual licenses confer a right to use the specific version of software that was current when maintenance ended or was last paid. They do not confer a right to use subsequent versions, and they do not convert to subscription access. An organization with an AutoCAD 2020 perpetual license may continue using AutoCAD 2020 indefinitely. Using AutoCAD 2024 on that perpetual license is a compliance violation.
38% of audit findings in organizations with legacy perpetual licenses involve "version overreach"—using versions released after the last paid maintenance period under the assumption that the perpetual license covers current versions. It does not. Autodesk's LRT system detects the version in use and cross-references it against the entitlement record, generating a finding where the version doesn't match the perpetual entitlement. Documenting your perpetual entitlement boundary is essential audit preparation.
Named User Compliance in 2026
Five years after the transition, the primary compliance challenge is no longer the transition itself—it is maintaining accurate Named User governance in dynamic organizational environments. The Named User compliance framework requires ongoing attention to four governance processes:
- New user onboarding: Named User assignment must be created in Admin Console before software access is provisioned, not after. The gap between installation and assignment creates an LRT anomaly that generates compliance findings even when the user is ultimately entitled.
- Employee offboarding: Named User assignments must be deactivated within an organizationally defined window (recommended: 30 days) after employment ends. Active assignments for former employees are the most common source of overstatement in LRT data.
- Contractor and freelancer management: External users accessing Autodesk software require Named User assignments from the organizational license pool. The contractor's own Autodesk subscription does not typically cover access to organization-deployed software.
- Quarterly reconciliation: Regular reconciliation of Admin Console Named User assignments against HR identity records, employment status, and deployment records. Organizations running this process quarterly reduce audit exposure by 78% compared to annual-only reconciliation.
Named User Migration: Compliance, Negotiation, and Governance
Complete framework for Named User compliance management including transition gap remediation, perpetual license documentation, and quarterly governance processes.
Audit Implications of the Named User Model
Under the multi-user model, proving compliance was relatively simple: show the concurrent license count equals or exceeds the peak concurrent user count. Under Named User, proving compliance requires demonstrating a one-to-one assignment between each license and each individual who accessed the software during the audit period.
This evidence burden is significantly higher and creates an asymmetric advantage for Autodesk's audit team, which uses LRT data showing all authentication events as its baseline. Without an independent Named User registry—a formal record of which licenses were assigned to which individuals at each point in time—organizations cannot effectively challenge the LRT-based finding count.
Organizations seeking audit defense for Named User-related findings should prioritize building this registry retrospectively, using HR records, Admin Console export history, and ITAM deployment data to construct a defensible assignment record. The challenge success rate for Named User findings is 88% where employment records clearly document inactive user status—significantly higher than the challenge rate for other finding categories.
The shift from multi-user to Named User licensing fundamentally changed the evidence burden in audits. Under the old model, peak concurrent usage was the compliance metric—straightforward to document. Under Named User, every historical authentication event is potentially a compliance obligation. Building and maintaining a contemporaneous Named User assignment record is no longer optional for organizations with significant Autodesk deployments—it is a prerequisite for effective audit defense.
Assess Your Named User Compliance Posture
We build independent Named User baselines, identify transition-related gaps, and establish governance frameworks that reduce your audit exposure by up to 78%.