Introduction Tips working with document set. Document sets are basically folders in the background Column formatting to display folder name into the library Document set is a folder in the backend, hence could apply the following Json to see which document set a file has been moved to. { "$schema": "https://developer.microsoft.com/json-schemas/sp/v2/column-formatting.schema.json", "elmType": "div", "txtContent": "=replace(replace(replace([$FileRef],[$FileLeafRef],''),'/sites/test/Shared Documents/',''),'/','')" } View to see all the document sets Limitations Nested document sets not allowed A file don’t belong to two document sets Advantages Apply metadata to files within the document set Manage as a logical grouping of files Do SharePoint document sets: when and why to use them covers usage and benefits of document sets.

Follow this post to set up Azure AI Search with SharePoint as a datasource, including how to target a specific library rather than only the default document library. Read post How to index SharePoint content using Azure AI Search for Copilot agents for detailed set up, this post covers only the different ways to connect to SharePoint content. SharePoint datasource container options Azure AI Search supports three container modes for SharePoint sources:

I tested SharePoint auto-trimming behavior against files with and without retention labels. The results show that files without a retention label are trimmed as expected, while files with a retention label behave more like retention policy items and keep versions longer. For non-retention-label files, SharePoint trims old versions once the version count grows. Auto-trimming bypasses the recycle bin and removes older minor/major versions. However, files with retention labels appear to retain versions instead of trimming them.