| Service | Microsoft Docs article | Related commit history on GitHub | Change details |
|---|---|---|---|
| SharePoint | Deploy And Configure On Macos | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/deploy-and-configure-on-macos.md | Use the following keys to preconfigure or change settings for your users. The ke - [DefaultFolderLocation](deploy-and-configure-on-macos.md#defaultfolderlocation) - [DisableAutoConfig](deploy-and-configure-on-macos.md#disableautoconfig) - [DisableFirstDeleteDialog](deploy-and-configure-on-macos.md#disablefirstdeletedialog)-- [DisableCustomRoot](deploy-and-configure-on-macos.md#disablecustomroot) - [DisableFirstDeleteDialog](deploy-and-configure-on-macos.md#disablefirstdeletedialog) - [DisableFREAnimation](deploy-and-configure-on-macos.md#disablefreanimation) - [DisableOfflineMode](#disableofflinemode) The example for this setting in the .plist file is: <integer>1</integer> ``` -### DisableCustomRoot --This setting lets you block users from changing the location of the OneDrive folder on their computer. --If you set this setting's value to **True**, the Change location link is hidden in OneDrive Setup. The OneDrive folder is created in the default location, or in the custom location you specified if you enabled [DefaultFolderLocation](deploy-and-configure-on-macos.md#defaultfolderlocation). --The example for this setting in the .plist file is: --```xml -<key>DisableCustomRoot</key> -<(Bool)/> -``` - ### DisableFirstDeleteDialog When a user deletes local files from a synced location, a warning message appears that the files are no longer available across all the devices of the user and on the web. This setting lets you hide the warning message. |
| SharePoint | Trim Versions | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/trim-versions.md | description: "This article provides guidance on how to trim existing versions fr # Trim existing versions from site, library, or OneDrive > [!CAUTION]-> Versions deleted using trimming jobs are permanently deleted. This deletion workflow bypasses the normal recycle bin retention and deleted versions cannot be recovered. +> Versions deleted using trimming jobs are permanently deleted. This deletion workflow bypasses the normal recycle bin retention and deleted versions cannot be recovered. To prevent unwanted data loss, it's highly recommended to [run an impact analysis](tutorial-run-what-if-analysis.md) before trimming activity. As a SharePoint admin in Microsoft 365, you can queue a job to trim existing versions on a site, library, or OneDrive user account to reduce the version storage footprint of your site. You can also align existing version storage with updated version history limits by scheduling a job to trim existing versions or align existing version storage with updated Version history limits.<br> There are several things you need to consider before you decide to trim existing Version history on a site or library. Version availability is critical for recovery scenarios like undoing unwanted changes. Versions deleted using trimming jobs are permanently deleted and can't be recovered from recycle bin. As a SharePoint admin in Microsoft 365, you can queue a job to trim existing ver :::image type="content" source="media/version-history/trimming-workflows.png" lightbox="media/version-history/trimming-workflows.png" alt-text="Diagram of trimming workflows."::: +> [!NOTE] +> Trim jobs are background jobs that are influenced by factors such as the volume of file versions to be evaluated, service health, and other jobs being processed on the farm. They are also subject to off-peak hour processing logic. The progress of a trim job can always be tracked. + ## Review impact by running ΓÇÿWhat-ifΓÇÖ analysis Before committing to trim existing versions, you can review the impact of the purge action by running a ΓÇÿWhat-ifΓÇÖ analysis operation. Running a ΓÇÿWhat-ifΓÇÖ operation will follow these steps: |