FSLogix container profile and issue withindexing

The described behavior matches known limitations and design aspects of FSLogix profile containers and how they interact with search and cloud storage (OneDrive/SharePoint) in non-persistent or containerized profiles.

Key points from the documented behavior:

1. FSLogix profile containers roam the user profile and provide high‑performance access to profile data in VDI and similar scenarios, but they do not change how Windows Search indexes remote/cloud content.
   • FSLogix stores the complete user profile in a VHD/VHDX and attaches it at sign‑in so it appears as a local profile, but indexing and search behavior are still governed by Windows and the storage provider.
   • FSLogix is primarily solving profile roaming and performance issues (for example, Outlook cached mode and OneDrive support in non‑persistent environments), not providing its own indexing engine.
2. For Microsoft 365/Office data, FSLogix’s Office 365/ODFC container is specifically designed to roam Outlook data and the Windows Search index for Outlook in non‑persistent environments.
   • In RDS/non‑persistent scenarios, the Office 365 container roams the Outlook .OST and its search index so Outlook search is immediately available across sessions.
   • This improvement is documented for Outlook search; there is no corresponding FSLogix feature in the provided material that extends or maintains Windows Search indexing for general OneDrive/SharePoint‑synced file system content in the same way.
3. OneDrive with FSLogix is supported and works by redirecting the default OneDrive path into the FSLogix profile container.
   • Users should select the default OneDrive location (C:\Users\%username%\). FSLogix redirects this into the container, and OneDrive disk‑space policies evaluate the FSLogix VHD size rather than the OS disk.
   • This ensures data and quota behavior are correct, but again does not introduce additional search/indexing logic beyond what Windows and OneDrive provide.
4. The documentation provided does not describe a supported configuration or setting in FSLogix that forces continuous or refreshed Windows Search indexing for OneDrive/SharePoint locations in single‑user Windows 11 with FSLogix profiles.
   • There is no documented FSLogix setting in the context that would “re‑trigger” or maintain Explorer search indexing for new/renamed files in those synced locations when using profile containers.
   • The only search‑specific enhancement described is for Outlook search via the Office 365 container.

Given the above, from the available documentation:

• FSLogix is functioning as a profile/container solution; it is not documented as responsible for maintaining or refreshing Windows Search indexing for OneDrive/SharePoint content in Explorer.
• The issue seen (indexing apparently only occurring at initial profile creation and not updating) is not addressed by any configuration or fix in the provided FSLogix documentation.
• The only search‑related FSLogix feature documented is Outlook search roaming via the Office 365 container in RDS/non‑persistent environments.

From the supplied material alone, there is no documented FSLogix configuration change or workaround that resolves the described Explorer search/indexing issue for OneDrive/SharePoint content in a single‑user Windows 11 25H2 + FSLogix profile container scenario.

Escalation to Microsoft Support, as already suggested by the presales consultant, is appropriate because the behavior differs between similar environments (AVD multi‑user vs single‑user) and is not covered by the current FSLogix guidance.

References:

• User profile management for Azure Virtual Desktop with FSLogix profile containers
• FSLogix FAQ
• Dealing with Outlook search in non-persistent Remote Desktop Services (RDS) environments
• Troubleshooting issues with container size or low disk space
• Troubleshooting issues with long or failed sign-ins