OneDrive for Business in Citrix: why it struggles, and how to fix it

OneDrive for Business is a poor fit for Citrix environments by architectural design. The OneDrive sync client assumes a persistent, single-user Windows machine; a Citrix desktop is usually neither of those things. Microsoft's FSLogix acquisition partially closes the gap, but leaves several permanent problems that no amount of configuration removes. Cloud Drive Mapper avoids the whole class of issue by not being a sync client at all: it presents SharePoint, OneDrive and Teams as virtual network drives, streaming content on demand.

Why doesn't the OneDrive sync client work well in Citrix?

The OneDrive sync client is built around one core assumption: it is running on a persistent Windows machine used by a single user, keeping a full local mirror of that user's cloud files in sync over time. Every design decision in the client flows from that assumption. Citrix desktops are typically non-persistent, often multi-user, and reset between sessions. Nothing about the sync client's design accommodates that.

The symptoms Citrix operators report most often: sync loops on login, ballooning profile sizes, files that appear locally but never propagate to the tenant, files that appear in the tenant but never propagate locally, mysterious sign-in failures on shared session hosts, and the general feeling that OneDrive is "there but not really working". None of these are bugs in the classical sense; they are the sync client operating outside its design envelope.

Microsoft acknowledged the problem some years ago. Because solving it properly would require a full rewrite of the sync client, they did the next best thing and acquired a company called FSLogix that had built a workable workaround.

What does FSLogix solve, and what does it not?

FSLogix works by redirecting the OneDrive cache into a per-user container (typically a VHD or VHDX file) that lives on shared storage and mounts into whichever Citrix session the user lands in. The container persists across sessions, so the sync client wakes up in each new session with the state it had at the end of the last one. Configured carefully, this reduces the most visible sync loops and lets OneDrive present a stable user experience across non-persistent hosts.

Configured carefully being the operative phrase. FSLogix is partial cover, not a fix, and five specific problems remain:

Sync overhead grows over time

Even with Files On-Demand enabled, the sync client still catalogues everything the user is subscribed to, and container sizes climb month over month. What was a minor overhead on day one becomes a real storage and I/O cost by day 365, especially when multiplied across the whole user base.

Multi-server Citrix deployments create conflicts

FSLogix behaves reliably in a single-server Citrix implementation. In organisations running multiple stacks or pools, the latent process of container reconciliation across sessions causes file conflicts that can be difficult to trace and recover from.

FSLogix has no clear roadmap

Microsoft acquired FSLogix to close a specific gap. The software receives security updates and stability fixes, but there is no signal that Microsoft is investing in significant new functionality. It exists, it works, and it stays where it is.

Uncontrolled OneDrive client updates

The OneDrive sync client auto-updates on the machine, which is convenient for consumer scenarios and awkward for enterprise Citrix operators with tight change-control processes. Occasionally an update reshapes behaviour in ways that require immediate response from the Citrix team.

No mapped drive letters for desktop applications

Many desktop applications, particularly the line-of-business software common in Citrix estates (CAD tools, accounting software, document management systems, healthcare EMR clients), require a real Windows drive letter to save data. The smart-sync folders the OneDrive client creates are not addressable by drive letter, so these applications cannot see the content that lives in them. This is the largest single reason organisations end up looking beyond the sync client for a Citrix answer.

These are not bugs to be fixed in a future release. They are permanent conceptual features of the FSLogix + OneDrive design.

How does Cloud Drive Mapper solve OneDrive in Citrix?

Cloud Drive Mapper is not a sync client. It presents SharePoint, OneDrive and Teams as virtual network drives with real Windows drive letters, talking directly to Microsoft Graph and streaming file content on demand rather than mirroring it locally. In a Citrix context this dissolves the whole class of sync-client problems: no container overhead, no cross-server reconciliation, no auto-update surprises, and applications that need drive letters get them.

CDM runs on any Windows Server 2016+ infrastructure and is compatible with the full Citrix range:

• Citrix Virtual Apps and Desktops
• Citrix DaaS
• Citrix XenApp and XenDesktop
• Citrix Workspace

Because CDM keeps no synced copy of your libraries, the local storage footprint inside each Citrix session is a fraction of what a OneDrive-plus-FSLogix arrangement requires, and there is no growth curve over time. That matters most on multi-session hosts and non-persistent desktops, where the cumulative footprint of a growing sync cache multiplied by concurrent users adds up quickly.

We are a Citrix Ready partner with hundreds of Citrix customers using Cloud Drive Mapper to integrate with their Microsoft 365 storage.

Frequently asked questions

Why doesn't the OneDrive sync client work well in Citrix?

The OneDrive sync client is designed around a persistent, single-user Windows machine that maintains a local mirror of the user's files. Citrix desktops are typically non-persistent, often multi-user, and reset between sessions. The client's fundamental assumptions do not hold in that environment, which is why users experience sync loops, profile bloat, missing files, sign-in failures and general unreliability.

Does FSLogix solve OneDrive in Citrix?

Partially. FSLogix (which Microsoft acquired specifically to close this gap) redirects the OneDrive sync cache into a per-user container that persists across sessions. It works when configured carefully, but the underlying sync client is still doing the work: profile containers grow over time, multi-stack Citrix deployments create conflicts, uncontrolled OneDrive updates disrupt users, and applications that need real drive letters still do not get them.

Does Cloud Drive Mapper work in Citrix DaaS?

Yes. Cloud Drive Mapper is compatible with Citrix DaaS, Citrix Virtual Apps and Desktops, Citrix XenApp and XenDesktop, and Citrix Workspace. It runs on any Windows Server 2016+ infrastructure. IAM Cloud is a Citrix Ready partner, and CDM is in production across hundreds of Citrix customer estates.

Can Cloud Drive Mapper give Citrix users mapped drive letters for their applications?

Yes. That is one of the core reasons CDM exists in Citrix environments. It presents SharePoint, OneDrive and Teams content as virtual network drives with real file paths, so legacy desktop applications that expect a Windows filesystem (CAD tools, accounting software, document management systems, and so on) work as they always have.

Do we need FSLogix if we deploy Cloud Drive Mapper in Citrix?

Not for OneDrive. Cloud Drive Mapper does not use the OneDrive sync client, so the sync-container problem FSLogix is solving does not exist under CDM. Many Citrix operators continue running FSLogix for wider profile-management reasons (Office Container, Profile Container for Windows profile state), and CDM is compatible with that; it just does not depend on it.

How much local storage does Cloud Drive Mapper use inside a Citrix session?

A fraction of what an OneDrive sync client plus FSLogix container consumes. Cloud Drive Mapper does not mirror content locally; it streams file content on demand and releases it after close. That makes it significantly lighter on the local disk footprint of each Citrix session, which matters most on multi-session hosts and non-persistent desktops.

Related solutions

• OneDrive for Business in Azure Virtual Desktop
• OneDrive for Business in Omnissa Horizon
• The OneDrive sync cache cost in VDI
• Copilot readiness in VDI environments
• Overcoming the OneDrive 300,000 file sync limit
• The "my app needs a real file path" problem
• How to enable folder redirection with OneDrive
• Cloud Drive Mapper for finance and insurance (VDI-heavy)
• Case study: US regional bank on Citrix

← Back to all solutions