Users’ FSLogix profile VHDX files are growing due to large Outlook OST files and OneDrive cached content. You want to reduce profile bloat and improve logon times without losing Microsoft 365 app functionality. What should you configure?

Enabling the FSLogix Office Container (ODFC) alongside the Profile Container is the most effective solution. ODFC is specifically designed to handle large, frequently accessed Microsoft 365 data like Outlook OST files and OneDrive cached content. By setting IncludeOutlook=1 and IncludeOneDrive=1, these large files are moved out of the primary Profile Container and into a separate ODFC container. This reduces the size of the Profile Container, leading to faster logons and less profile bloat, while maintaining full Microsoft 365 functionality. Disabling the Profile Container entirely and relying solely on ODFC is incorrect because ODFC is designed to complement, not replace, the Profile Container for general user data. Redirecting Outlook data to the local C: drive would cause data loss upon session termination in non-persistent environments and wouldn't roam with the user. Manually mounting VHDs for OST files is complex and not a scalable or integrated solution. Enabling legacy Windows roaming profiles alongside FSLogix is not recommended, as it can lead to conflicts and performance issues, and FSLogix is the modern, preferred solution for profile management in AVD.