FSLogix profile containers can keep growing even when users save their files to OneDrive. This article explains why, and provides a troubleshooting workflow and prevention checklist for recurring profile quota and disk-full issues.
The guidance applies to pooled and personal host pools that store FSLogix profile containers on Azure Files, Azure NetApp Files, or another supported storage platform.
Note
OneDrive changes where user files are synchronized. It doesn't eliminate local profile growth from sync state, caches, application data, Outlook, Teams, browser data, temporary files, or virtual disk white space.
FSLogix profile containers store a user profile in a VHD or VHDX file. At sign-in, the container is attached to the session host and Windows treats it as the user's local profile. OneDrive is supported in virtual desktop environments, including non-persistent virtual desktops that use FSLogix. For details, see Microsoft Learn: Use the sync app on virtual desktops.
A profile container can fill up even when users save files to OneDrive, because the profile still contains user-specific data and cache. In addition, when data is deleted inside the container, the VHD or VHDX file doesn't necessarily shrink at the storage layer.
The following items commonly contribute to container growth:
-
OneDrive sync metadata and sync state
-
OneDrive files marked as locally available or pinned
-
Office cache
-
Outlook OST or cached mailbox data
-
Teams cache
-
Browser cache
-
The Downloads folder
-
Desktop, Documents, or Pictures content before Known Folder Move completes
-
Recycle Bin content
-
Application logs and temporary data
-
Line-of-business (LOB) application cache
-
Windows Search data
-
White space inside the VHD or VHDX file
When data is added to an FSLogix container, the VHD or VHDX file grows. When data is removed, the virtual disk contains more free space internally, but the file itself doesn't necessarily shrink. Nerdio Manager includes FSLogix shrink automation that reclaims unused white space from profile containers. For details, see FSLogix Shrink VHD/VHDX Containers (Scripted Action).
When many users hit the same profile limit on a similar cadence, the cause is often environmental rather than random. This pattern is common when users have the same quota, similar workloads, similar cache behavior, and no recurring shrink or hygiene process. Typical contributing factors are:
-
All users have the same FSLogix quota.
-
Users were migrated or created around the same time.
-
The same application cache grows at a similar rate for most users.
-
OneDrive, Teams, Outlook, or browser cache grows predictably over time.
-
VHD or VHDX files aren't compacted on a schedule.
-
A policy or software update changed cache behavior.
-
Storage reporting reflects the allocated container size rather than active user data.
Work through the following steps to find out what is driving growth and which remediation fits.
Locate the affected profiles and compare their sizes. For profile search and management options, see FSLogix Profile Management – Advanced Search. Capture enough information to determine whether the issue is isolated or systemic:
-
User name
-
Profile path
-
Container type (VHD or VHDX)
-
Current file size
-
Configured quota
-
Last modified time
-
Affected host pool
-
Whether the user is actively signed in
-
Whether the issue affects one user, many users, or all users
A large container can contain active user data, application cache, white space from deleted data, or a combination of all three. If there is significant white space, shrink maintenance can reclaim storage without increasing the user quota.
Confirm the following settings. For details, see FSLogix settings and configuration and FSLogix per-host pool customization.
-
Profile path
-
Container type
-
Profile size limit
-
Cloud Cache settings, if you use them
-
Office container settings, if you use them
-
Redirections configuration
-
FSLogix agent version
-
Whether Nerdio Manager is applying the intended settings to the host pool
Review the following OneDrive behaviors:
-
Files On-Demand status
-
Known Folder Move status for Desktop, Documents, and Pictures
-
Whether users pin large folders locally
-
Whether users save content outside OneDrive-managed folders
-
Sync health
-
Cache growth
-
User understanding of the Always keep on this device option
Review the cache behavior of the following:
-
Outlook cached mode and OST size
-
Teams cache
-
Office document cache
-
Search index behavior
-
Browser cache
-
Large Downloads folders
-
LOB application temporary paths
FSLogix redirections can reduce profile bloat by excluding selected paths from the container. Test redirections carefully. Good candidates are usually disposable cache or temporary paths. Poor candidates include application settings, authentication data, and information that users expect to persist.
Review the following storage metrics:
-
Capacity usage
-
Provisioned capacity, where applicable
-
IOPS and throughput
-
Latency
-
Quota alerts
-
Sudden growth patterns
-
Backup or snapshot behavior
-
Azure Files tier and performance limits
-
Azure NetApp Files capacity pool behavior, where applicable
If users can't sign in or receive temporary profiles, profile locking might be involved. Profile locks are more likely when users disconnect instead of signing out, when multiple host pools point to the same profile path, or when a session host fails to release the container cleanly. For details, see Troubleshoot FSLogix Profile Mount Errors and Troubleshoot FSLogix Profile VHD File Handles Issues.
Choose the remediation that matches what you found:
|
Option |
Use when |
Notes |
|---|---|---|
|
Run FSLogix shrink maintenance |
The container is large but contains reclaimable white space. |
This is the best first remediation when deleted or moved data didn't reduce storage consumption. See FSLogix Shrink VHD/VHDX Containers (Scripted Action). |
|
Increase the profile size limit |
The profile contains legitimate workload data that must persist. |
Don't use a quota increase as the only fix for unmanaged cache growth. |
|
Review OneDrive Files On-Demand and Known Folder Move |
Users store or pin large data locally. |
Clarify the difference between cloud-only and locally available file behavior. |
|
Add or update redirections |
A specific disposable cache path drives growth. |
Pilot before broad use, and document every excluded path. |
|
Reset the profile |
The profile is corrupt or unrecoverable. |
This is a last resort. Confirm that user data is protected before you delete a profile. For profile delete, archive, and restore options, see FSLogix Profile Management – Advanced Search. |
-
Schedule FSLogix shrink maintenance where appropriate.
-
Monitor profile size trends before users hit their quota.
-
Enable alerts for profile storage capacity.
-
Confirm OneDrive Files On-Demand behavior.
-
Review Known Folder Move adoption.
-
Educate users on the difference between cloud-only and locally available OneDrive files.
-
Review Teams, Outlook, browser, and LOB application cache behavior.
-
Use redirections for disposable cache only after testing.
-
Avoid profile resets as routine maintenance.
-
Review the FSLogix version during image updates.
-
Validate storage performance and capacity regularly.
Multiple users hit a 30 GB FSLogix profile limit every 60 to 90 days. Likely contributors include identical quotas, similar Microsoft 365 cache growth, OneDrive local cache, no scheduled shrink, and white space inside VHDX files.
To investigate, identify the largest profiles, check how much white space can be reclaimed, review OneDrive and cache behavior, and pilot redirections. Adjust quotas only after you understand the expected workload size.
Raise a support ticket for this item.
Comments (0 comments)