Executive Summary
Autodesk's Named User subscription model changed license portability fundamentally. Under the legacy concurrent license model, portability was implicit: the license traveled with the checkout, regardless of device or location. Under Named User, portability is tied to identity, not device — but the rules governing device limits, remote access, virtual environments, geographic access, and contractor use contain specific compliance requirements that enterprise deployments routinely misinterpret. This article maps the full portability rule set, identifies the five most common misinterpretation patterns that create audit exposure, and provides the governance framework for compliant portability management.
How Named User Portability Works
Autodesk's Named User licensing model attaches the license to an individual's Autodesk Identity — the account associated with the licensed user's Autodesk.com credentials. The fundamental portability principle is that the license travels with the identity, not the device. A licensed Named User can authenticate to Autodesk software on any device where the software is installed — there is no device registration requirement that permanently locks a license to a specific machine.
This identity-portable model has significant advantages over the legacy physical device licensing approach: users can work from office workstations, home offices, laptops, and client sites without administrative intervention or license transfers. The Named User model was specifically designed to accommodate modern hybrid and remote work patterns.
However, identity portability comes with specific rules governing simultaneous device access, geographic scope, virtual environment usage, and contractor/third-party access. Violations of these rules — which typically result from misunderstanding them, not from intentional circumvention — are among the most frequently cited findings in Autodesk compliance audits, appearing in 38% of enterprise audit preliminary findings.
Under concurrent network licensing, a license was "in use" only when actively checked out. Under Named User, a license is "assigned" permanently to an individual until explicitly reassigned. This means shared devices, contractor access, and guest users all consume Named User licenses even when usage is infrequent — a fundamental change that many governance frameworks have not caught up to.
Device Portability: The Three-Device Rule
Autodesk's standard Named User subscription terms permit each assigned Named User to install and activate Autodesk software on up to three devices. This three-device limit is a per-user limit, not an organization-wide limit — each licensed user may have up to three simultaneous installations of each licensed product.
The three-device limit is frequently misunderstood in two directions. Organizations sometimes assume that a single Named User license allows installation on any number of organization-owned devices — for example, deploying AutoCAD to every workstation in a department and allowing shared access. This is incorrect: the license authorizes installation on up to three devices specifically associated with the licensed individual, not unlimited deployment within the organization's fleet.
Conversely, some organizations assume that the three-device limit means only three devices may ever have Autodesk installed — missing that devices can be retired and replaced, and that the limit is simultaneous activations rather than historical installations. A user who upgrades their workstation is not violating the limit by having a brief overlap; they are violating it if they maintain four permanent simultaneous installations without deactivating one.
Device Deactivation Management
In enterprise environments with frequent hardware refresh cycles, device deactivation management becomes a compliance requirement. When a workstation is retired, the Named User's device activation count must be decremented — either through formal deactivation in the Autodesk Admin Console or through Autodesk's device management interface. Organizations with 500+ users and regular hardware refresh cycles that do not manage deactivation typically accumulate "phantom" device activations that trigger LRT overcount events.
The correct governance practice is to include Autodesk device deactivation as a step in the IT hardware refresh checklist — executed before the old device is wiped and retired. Organizations that implement this as a standard process reduce device-related compliance gaps by an average of 14% within the first hardware refresh cycle.
Remote Access and Hybrid Work Portability
Autodesk's Named User licensing supports remote work scenarios explicitly: a licensed user working from home on a personally-owned device is using their Named User license in an authorized manner, provided the usage occurs under their assigned identity. The license does not require that the device be organization-owned or managed.
The compliance complications arise in specific remote access architectures rather than simple remote work scenarios:
Named User on Personal Device (Remote Work)
A licensed employee accessing Autodesk software on their personal home computer under their assigned Named User identity. This is fully supported — the license is tied to the identity, not the device, and personal device use is not restricted. Standard enterprise security policies (VPN, MDM for company data) apply but do not affect license compliance.
Remote Desktop to Licensed Workstation
A licensed user remotely accessing their own assigned corporate workstation via RDP or similar tools. The session uses the same Named User identity as the device assignment — this is one device of the user's three-device allowance, and remote access does not create an additional device activation event provided the user authenticates under the same identity.
Shared Remote Desktop Session (Multiple Users)
A single workstation with Autodesk installed that multiple different users access via remote desktop under their own individual credentials. Each user authenticating to the Autodesk installation is a Named User event for their identity — regardless of how the access occurs. All users accessing Autodesk on a shared remote workstation require their own Named User licenses.
VDI/Terminal Services Access
Access to Autodesk via Virtual Desktop Infrastructure or Terminal Services depends on the VDI architecture. Dedicated VDI (each user has their own persistent virtual machine) functions like remote desktop access — one device for one user's three-device count. Shared VDI pools where multiple users authenticate to shared images require Named User licenses for each authenticating user, as each authentication event is recorded by LRT against the individual's identity.
Concurrent Access to Same Installation
Two different Named Users authenticating to the same Autodesk installation simultaneously — even on the same physical device or virtual machine — requires two Named User licenses. The Named User model does not permit concurrent license sharing regardless of the underlying infrastructure.
Site License / Unlimited User Models
Some EBA and enterprise agreements include site license provisions that modify the standard Named User one-license-per-person model. These provisions must be explicitly stated in the agreement — site licensing is not implied by Named User subscription terms and cannot be inferred from volume purchasing. Organizations operating under assumed site license models without explicit contractual provision are exposed to significant finding risk.
Geographic Portability and Multi-Region Use
Autodesk Named User licenses issued under a standard subscription agreement have global portability for the licensed individual. A Named User may access their assigned Autodesk licenses from any country in which Autodesk makes its products available — the license does not restrict geographic usage to the country of purchase.
However, geographic portability interacts with two compliance complications that enterprise organizations must manage:
Regional Entity Coverage
Enterprise agreements — particularly EBAs and master subscription agreements — define a "Covered Entity" scope that determines which legal entities within an enterprise group can use licenses purchased under that agreement. An agreement purchased by a US parent company for its US operations may explicitly or implicitly exclude non-US subsidiaries. A French subsidiary employee authenticating to Autodesk under the parent's agreement creates a compliance event if the French entity is not within the covered entity scope.
This is one of the most common compliance gaps in multinational organizations: local employees are added to the Autodesk Admin Console under the global agreement without verifying whether their legal entity is covered. Resolving this requires either expanding the covered entity definition at renewal or establishing regional sub-agreements for non-covered entities. The global licensing guide covers multi-entity agreement architecture in detail.
Export Control Considerations
Certain Autodesk products — particularly simulation, analysis, and defense-adjacent design tools — may be subject to US export control regulations (EAR/ITAR) that restrict geographic access. Organizations in defense, aerospace, and dual-use industries must verify whether their Autodesk product suite includes products with geographic access restrictions before enabling global Named User portability for all users.
White Paper: Autodesk Named User Migration Guide
The transition from legacy multi-user licensing to Named User created specific portability compliance gaps. This white paper maps those gaps, the contractual protections available during migration, and the governance framework for ongoing compliance.
Download Free →Contractor and Third-Party License Portability
Contractor and third-party access is among the most frequently mismanaged portability scenarios in enterprise Autodesk deployments. The fundamental rule is straightforward: any individual who uses Autodesk software — regardless of employment relationship — must have a Named User license assigned to their identity.
The portability implications are significant. Contractors often work across multiple client environments, may use their own devices, and have variable engagement durations. Each of these factors creates compliance complexity:
- Contractor-owned licenses: A contractor who holds their own Autodesk subscription license may use that license for work performed for a client organization, provided the license is assigned to their identity (not the client's license pool) and the agreement terms do not restrict commercial sub-contracting use. However, if the client organization's agreement requires that all users working under that agreement use licenses purchased under that agreement, the contractor's personal license may not satisfy the compliance requirement.
- Client-provisioned contractor licenses: When a client organization provisions a Named User license to a contractor under the client's agreement, that license is consumed as a named user under the client's agreement for the duration of the contractor engagement. The license must be formally reclaimed when the contractor engagement ends — this reclamation is not automatic and is a significant compliance gap in organizations without formal contractor offboarding processes.
- Consultant access for project work: Consultants accessing client Autodesk environments for limited-scope project work — reviewing models, running analysis, providing technical input — require Named User licenses for the duration of that access. The occasional nature of the access does not reduce the licensing obligation. Organizations that enable short-term project access without provisioning licenses accumulate compliance exposure with every project team engagement.
| Access Scenario | License Requirement | Common Compliance Error | Audit Finding Frequency | Remediation |
|---|---|---|---|---|
| FTE remote (personal device) | One Named User license | None (well understood) | Low | N/A |
| Shared workstation (sequential) | One license per user | Treating as single license use | High (34%) | Assign licenses to all users, dedicate machines to users |
| VDI shared pool | One license per accessing user | Treating as concurrent model | Very High (52%) | Dedicated VDI or license all pool users |
| Contractor (client-provisioned) | One Named User per contractor | Not reclaiming at engagement end | High (41%) | Formal offboarding process with license reclamation |
| Multi-region subsidiary | Must be within covered entity scope | Adding users without verifying entity coverage | Medium (23%) | Expand covered entity definition or regional sub-agreement |
| Service accounts / automation | Agreement-dependent | Treating automated processes as licensed | Medium (18%) | Document service account purpose, negotiate exclusion |
Portability Compliance Governance
Managing portability compliance at scale requires governance processes that address the primary risk scenarios identified above. A practical governance framework for enterprise portability compliance has four operational components:
1. Named User Assignment Lifecycle Protocol
Define a formal process for Named User license assignment and deprovisioning that is integrated with HR and IT provisioning workflows. Assignment should be triggered by the same event as user onboarding and IT access provisioning. Deprovisioning should be triggered by employment termination, contractor end date, and role changes that eliminate Autodesk access requirements. The Named User assignment best practices article details the four-step lifecycle protocol.
2. VDI Access Architecture Review
Audit the current VDI or remote desktop architecture against Named User portability rules. Identify whether Autodesk is deployed to shared pools or dedicated machines, whether multiple users access the same VDI instances, and whether access logs reflect the assignment records in Autodesk's Admin Console. Remediate architecture gaps that create compliance exposure — typically by moving from shared pool to dedicated VDI assignment, or by licensing all users with access to shared pools.
3. Contractor Access Registry
Maintain an active registry of contractor Named User license assignments, including contractor identity, engagement start date, scheduled end date, and assigned license. Schedule automated review reminders 30 days before each contractor end date to confirm reclamation or engagement extension. This registry function is simple to implement and eliminates the primary source of contractor-related compliance gaps.
4. Quarterly Portability Compliance Review
Incorporate a portability compliance check into the quarterly Named User review process: verify device activation counts are within three per user, confirm VDI architecture is consistent with assignment records, validate contractor assignments against active engagement records, and verify multi-region users are within covered entity scope. This quarterly cadence catches portability gaps before they accumulate into material audit exposure.
Portability rules — particularly VDI deployment terms, covered entity definitions, and contractor licensing requirements — are negotiable at renewal for enterprise buyers. Organizations with $1M+ annual Autodesk spend can negotiate VDI deployment clarifications, expanded covered entity scope, and contractor day-rate access provisions that reduce structural compliance risk without changing operational practice. The license negotiation service includes portability term negotiation as a standard engagement component.
Identify Your Portability Compliance Gaps
Our advisors review VDI architecture, contractor access configurations, and multi-region deployments against Named User portability rules — and identify audit exposure before Autodesk's compliance team does. Independent, objective, not affiliated with Autodesk.
Schedule Consultation Audit Defense