AutoCAD and OneDrive: what breaks, and how to fix it

AutoCAD is built to run against a network drive. It expects stable paths for XREFs, real-time exclusive locks on DWGs, and a filesystem that answers instantly when it asks a question. The OneDrive sync client does none of that. This piece walks through the specific mechanisms that break when AutoCAD runs on OneDrive-synced storage, explains why they break, and lays out the practical fix options for teams that want AutoCAD to work reliably against Microsoft 365.

What breaks when you run AutoCAD on the OneDrive sync client?

The issues cluster into six specific patterns. Most CAD teams recognise at least three of them within their first month of putting DWG data on OneDrive.

XREFs fail to resolve

When you open a parent drawing, AutoCAD walks the XREF list and asks the filesystem for each referenced DWG. With Files On-Demand enabled, those XREFs are placeholder stubs that OneDrive hydrates on request. AutoCAD's XREF loader assumes the referenced file is immediately available; the sync client's hydrate-on-demand behaviour breaks that assumption. Users see broken references on drawings that were fine the day before.

File locking is unreliable

AutoCAD creates a .dwl and .dwl2 lock file alongside each opened DWG so other AutoCAD instances know the drawing is in use. The sync client sees those lock files as ordinary new files and starts syncing them to the cloud. A second user opening the same DWG from a different machine may not see the lock in time, opens the drawing, and now both users have unsaved changes to the same file. Whoever saves last wins, and the other person's work is lost.

Saves are slow, and get slower as files grow

Every save triggers a full re-upload of the entire DWG. On a 200MB drawing over a domestic broadband connection, that is a coffee break per save. Multiplied across a working day, the productivity cost is severe, and the pain scales with drawing size.

"File in use" errors that no-one is holding

The sync client scans files, reads them, and briefly holds them open during upload. If AutoCAD tries to open a file that OneDrive is mid-upload on, the open fails with a generic "file in use" error. The user closes and retries; sometimes it works, sometimes not. Nobody can point at who is holding the file.

Conflict files everywhere

When two changes to the same DWG cannot reconcile, OneDrive creates a "Conflict copy from <username> on <date>.dwg". CAD teams end up with three or four versions of the same drawing and no clear canonical one. Merging changes between DWG files is essentially manual, because CAD data is not diff-mergeable.

Sheet Set Manager and plot pipelines fall over

AutoCAD's Sheet Set Manager builds .dst files that reference dozens of sheets, layouts and plot styles by path. If any of those files are cached stubs or in flux, the sheet set fails to load. Batch-plot workflows that iterate through a sheet set suffer the same problem, silently skipping or erroring on files the client had not finished syncing.

Why the OneDrive sync client isn't built for AutoCAD

The mismatch is architectural, not a bug. The OneDrive sync client is designed for documents: relatively small files, single-editor patterns, tolerance for eventual consistency, no strong locking requirement. AutoCAD is designed for engineering-grade file operations: large files, precise locking, real-time path resolution, and dependent-file webs that break if any one path drifts.

Autodesk's guidance has consistently favoured network storage over consumer-style sync clients for AutoCAD data. Sync-client folders are not a supported configuration for shared AutoCAD workflows, and Autodesk's own knowledge base lists them as a known source of file-corruption and file-locking issues.

We have written a longer piece on this general class of problem: Desktop applications and real file paths. AutoCAD is one of the clearest cases, but the same underlying mismatch affects Inventor, most GIS tools, iManage, Sage, and any other application that assumes it has a real filesystem to work against.

What are the fix options?

Three approaches come up in most CAD-plus-M365 conversations. Each has trade-offs.

Keep DWGs on a local drive or on-premises file server

Works, and preserves the network-drive behaviour AutoCAD expects. The trade-off is that it keeps a file server (and the backup, replication and DR arrangements around it) in place indefinitely. If the file server is the last workload holding you back from a full Microsoft 365 migration, this option is the status quo you were trying to leave.

FSLogix profile containers (VDI only)

Only relevant in Citrix, Azure Virtual Desktop, Windows 365 Cloud PC or Omnissa Horizon. Contains the sync problem inside a per-user VHD; it does not remove it. XREF timing and file-locking issues still surface within the container, and the container itself grows over time.

A drive-mapping approach (Cloud Drive Mapper)

Presents SharePoint, OneDrive and Teams as a real Windows drive letter. AutoCAD sees a network drive, XREFs resolve immediately, file locking uses SharePoint's native check-out, and there is no sync client in the picture. This is the approach the rest of this page is about.

How Cloud Drive Mapper fixes AutoCAD on Microsoft 365

Five specific things change when AutoCAD runs against a CDM-mapped drive:

Real Windows drive letters and stable paths

CDM maps SharePoint document libraries as drive letters (M:, X:, whatever you configure). Paths that AutoCAD stores inside XREFs stay valid across sessions and across users, because the drive letter and the path structure below it are consistent for everyone in the organisation.

XREFs load synchronously

No hydration wait, no smart-sync stub. When AutoCAD asks the filesystem for a referenced DWG, CDM streams the file content and returns to AutoCAD as if the file were on a local share. Even large XREF webs resolve on first open.

File locking uses SharePoint check-out

When a user opens a DWG through CDM, the file is checked out in SharePoint automatically. Any second user opening the same drawing sees "checked out by <user>" and receives a read-only copy. There is no way for two users to end up with unsaved changes to the same file at the same time.

Saves are streamed, not fully re-uploaded

CDM streams changed blocks directly to SharePoint, so a small edit to a large drawing writes a small amount of network traffic, not the whole file. Save times for CAD-scale files fall significantly compared to the sync client's full-file re-upload model.

No conflict copies

Because the file is checked out at open, there is nothing for OneDrive to conflict on. Second users read-only wait until check-in. Version history is preserved by SharePoint's native versioning, so previous states are recoverable in the ordinary way.

AutoCAD-specific configuration notes

Nothing exotic is required. Point AutoCAD's XREF search paths, plot style paths, sheet set libraries and project files at the CDM-mapped drive rather than at a local OneDrive folder. If your teams currently use a mixture of local OneDrive folders and network paths, migrate to the CDM drive-letter path once and remove the local references. XREFs stored with local paths will not resolve through CDM until they are re-pathed.

CDM supports AutoCAD in the following deployment models:

• Windows desktops (direct)
• Citrix Virtual Apps and Desktops
• Citrix DaaS
• Azure Virtual Desktop (AVD)
• Windows 365 Cloud PC
• Omnissa Horizon (formerly VMware Horizon)

Cloud Drive Mapper is used across construction, engineering and architectural practices to run AutoCAD and the wider Autodesk suite directly against Microsoft 365 storage.

Frequently asked questions

Does Autodesk support AutoCAD running against the OneDrive sync client?

Autodesk's guidance has consistently favoured network storage over consumer-style sync clients for AutoCAD project data. Sync-client folders are not a supported configuration for shared AutoCAD workflows, and Autodesk's own support articles list them as a known source of file-corruption and file-locking issues.

Does Cloud Drive Mapper work with all AutoCAD versions and other Autodesk products?

Yes. CDM presents Microsoft 365 storage as a standard Windows drive letter, so AutoCAD interacts with it the same way it would a traditional network share. All modern AutoCAD versions work with CDM, along with the wider Autodesk portfolio including Inventor, Civil 3D and Plant 3D.

What happens to XREFs saved with paths pointing at the old OneDrive folder?

They will not resolve until they are re-pathed to the CDM-mapped drive. AutoCAD's XREF Manager supports batch re-pathing, or the paths can be edited directly with the -XREF command. Once the DWG has been re-saved against the mapped drive letter, the paths stay stable across sessions and users.

Can multiple users work on the same DWG through CDM?

Not simultaneously, because DWG is a binary format and nothing does real-time co-authoring on binary CAD files well. CDM uses SharePoint's native check-out mechanism, so the first user to open a DWG gets exclusive edit access and other users get read-only. This mirrors the file-server model CAD teams have used for years.

Does CDM work with AutoCAD's Sheet Set Manager and batch plotting?

Yes. Sheet Sets (.dst), DWT templates, plot style tables (CTB and STB) and page setup files all resolve through the mapped drive letter. Batch-plot workflows that iterate across a sheet set behave the same way against CDM as they would against a network share.

What about very large DWG files (200MB and above)?

CDM streams file content on open and streams only the changed blocks on save. Open times depend on the customer's link to Microsoft 365, but a well-connected office typically opens large drawings quickly. Save cost is proportional to the size of the change, not the size of the file, which is a significant improvement over the sync client's full-file re-upload model.

Related solutions

• Desktop applications and real file paths (the underlying problem class)
• OneDrive for Business in Citrix (for VDI-hosted CAD environments)
• Overcoming the OneDrive 300,000 file sync limit (CAD estates frequently hit this)
• Cloud Drive Mapper for construction
• Case study: Shropshire Homes

← Back to all solutions