option to delete the Cloud Cache data from the FSLogix session located in the Program Data folder

Currently, FSLogix does not provide built-in options to automatically manage or delete cached data from the ProgramData/Cache folder after user logoff. The data remains in this folder, which can lead to space constraints on the system. To manage this data, you may need to implement a manual cleanup process or create a script that runs after user logoff to delete older cached data while ensuring that active session data is not affected.

It's important to ensure that any cleanup process does not interfere with the active session data to prevent data loss or corruption. You might consider scheduling a cleanup task during off-peak hours to minimize the impact on users.

References:

• Business continuity and disaster recovery options for FSLogix
• Troubleshooting issues with container size or low disk space

Hello $@chin,

Based on your describe, FsLogix Cloud Cache is working as designed — it doesn’t automatically clear out old cache data from ProgramData\FSLogix\Cache. The cache is meant to stay behind for resiliency, so cleanup has to be managed through settings or maintenance scripts. You’re not missing a hidden option; Microsoft expects admins to handle disk usage proactively.

The reason it persists is simple: Cloud Cache keeps local copies so sessions remain available even if cloud storage is slow or temporarily unreachable. That’s why files don’t disappear at logoff. Over time, though, this can fill up the C: drive in busy AVD environments.

To manage it, you can enable the CCDeleteLocalCacheOnLogoff registry setting to clear cache when users log off (though this reduces resiliency if they reconnect quickly). Alternatively, many admins use scheduled PowerShell scripts to remove stale files based on age, combined with monitoring tools like Azure Monitor to alert when disk space runs low.

Let me know how it goes, and if this answer helps, feel free to hit “Accept Answer” so others can benefit too 😊

Domic.