| Service | Microsoft Docs article | Related commit history on GitHub | Change details |
|---|---|---|---|
| SharePoint | Allow Or Prevent Custom Script | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/allow-or-prevent-custom-script.md | description: Learn how global and SharePoint admins can change the custom script # Allow or prevent custom script -As a Global Administrator or SharePoint Administrator in Microsoft 365, you can allow custom script as a way of letting users change the look, feel, and behavior of sites and pages to meet organizational objectives or individual needs. If you allow custom script, all users who have "Add and Customize Pages" permission to a site or page can add any script they want. (By default, users who create sites are site owners and therefore have this permission.) +As a Global Administrator or SharePoint Administrator in Microsoft 365, you can allow custom script as a way of letting users change the look, feel, and behavior of sites and pages to meet organizational objectives or individual needs. If you allow custom script, all users who have _Add and Customize Pages_ permission to a site or page can add any script they want. (By default, users who create sites are site owners and therefore have this permission.) > [!NOTE] > For simple ways to change the look and feel of a site, see [Change the look of your SharePoint site](https://support.office.com/article/06bbadc3-6b04-4a60-9d14-894f6a170818). As a Global Administrator or SharePoint Administrator in Microsoft 365, you can By default, script is not allowed on most sites that admins create using the SharePoint admin center as well as all sites created using the New-SPOSite PowerShell command. Same applies to OneDrive, sites users create themselves, modern team and communication sites, and the root site for your organization. For more info about the security implications of custom script, see [Security considerations of allowing custom script](security-considerations-of-allowing-custom-script.md). > [!IMPORTANT]-> If SharePoint was set up for your organization before 2015, your custom script settings might still be set to "Not Configured" even though in the SharePoint admin center they appear to be set to prevent users from running custom script. In this case, users won't be able to copy items between SharePoint sites and between OneDrive and SharePoint. On the <a href="https://go.microsoft.com/fwlink/?linkid=2185072" target="_blank">Settings page in the SharePoint admin center</a>, to accept the custom script settings as they appear, select **OK**, and enable cross-site copying. For more info about copying items between OneDrive and SharePoint, see [Copy files and folders between OneDrive and SharePoint sites](https://support.office.com/article/67a6323e-7fd4-4254-99a8-35613492a82f). +> If SharePoint was set up for your organization before 2015, your custom script settings might still be set to _Not Configured_ even though in the SharePoint admin center they appear to be set to prevent users from running custom script. In this case, users won't be able to copy items between SharePoint sites and between OneDrive and SharePoint. On the <a href="https://go.microsoft.com/fwlink/?linkid=2185072" target="_blank">Settings page in the SharePoint admin center</a>, to accept the custom script settings as they appear, select **OK**, and enable cross-site copying. For more info about copying items between OneDrive and SharePoint, see [Copy files and folders between OneDrive and SharePoint sites](https://support.office.com/article/67a6323e-7fd4-4254-99a8-35613492a82f). ## To allow custom script on OneDrive or user-created sites > [!NOTE] > This feature will be removed during H1 calendar year 2024. Once removed, it will no longer be possible to allow custom script on OneDrive sites. -In the <a href="https://go.microsoft.com/fwlink/?linkid=2185219" target="_blank">SharePoint admin center</a>, you can choose to allow users to run custom script on OneDrive (referred to as "personal sites") or on all classic team sites they create. For info about letting users create their own sites, see [Manage site creation in SharePoint](manage-site-creation.md). +In the <a href="https://go.microsoft.com/fwlink/?linkid=2185219" target="_blank">SharePoint admin center</a>, you can choose to allow users to run custom script on OneDrive (referred to as _personal sites_) or on all classic team sites they create. For info about letting users create their own sites, see [Manage site creation in SharePoint](manage-site-creation.md). > [!CAUTION] > Before you allow custom script on sites in your organization, make sure you understand the [security implications](security-considerations-of-allowing-custom-script.md). In the <a href="https://go.microsoft.com/fwlink/?linkid=2185219" target="_blank" - **Allow users to run custom script on self-service created sites**. -  + :::image type="content" alt-text="Screenshot of custom script section of settings page in SharePoint admin center." source="media/a96d5c23-6389-4343-81cb-7f055617f6e8.png" lightbox="media/a96d5c23-6389-4343-81cb-7f055617f6e8.png"::: > [!NOTE] > Because self-service site creation points to your organization's root site by default, changing the Custom Script setting allows custom script on your organization's root site. For info about changing where sites are created, see [Manage site creation in SharePoint](manage-site-creation.md). In the <a href="https://go.microsoft.com/fwlink/?linkid=2185219" target="_blank" > [!CAUTION] > Before you allow custom script on sites in your organization, make sure you understand the [security implications](security-considerations-of-allowing-custom-script.md). -To allow custom script on a particular site (previously called "site collection") immediately, follow these steps: +To allow custom script on a particular site (previously called _site collection_) immediately, follow these steps: 1. [Download the latest SharePoint Online Management Shell](https://go.microsoft.com/fwlink/p/?LinkId=255251). > [!NOTE]- > If you installed a previous version of the SharePoint Online Management Shell, go to Add or remove programs and uninstall "SharePoint Online Management Shell." + > If you installed a previous version of the SharePoint Online Management Shell, go to Add or remove programs and uninstall **SharePoint Online Management Shell**. 2. Connect to SharePoint as a [Global Administrator or SharePoint Administrator](./sharepoint-admin-role.md) in Microsoft 365. To learn how, see [Getting started with SharePoint Online Management Shell](/powershell/sharepoint/sharepoint-online/connect-sharepoint-online). If you change this setting for a classic team site, it will be overridden by the ## Manage custom script from SharePoint admin center > [!NOTE]-If you do not see the new options in SharePoint tenant admin center, the feature is not enabled in your tenant yet. Every customer will have this new set of capabilities enabled by end of June 2024 +> If you do not see the new options in SharePoint tenant admin center, the feature is not enabled in your tenant yet. Every customer will have this new set of capabilities enabled by end of June 2024 Tenants administrators have a set of tools available in SharePoint tenant administration to manage custom script within their organization. Specifically, tenant administrators can do the following:-* verify custom script status -* change custom script settings -* persist custom script settings ++- verify custom script status +- change custom script settings +- persist custom script settings ### Verify custom script status-A new "Custom script" column is now available in the "Active sites" page under "Sites". - -The column can be added to any view. A new "Custom script allowed sites" is also available to provide an easy access to all the sites where custom script is enabled: - +A new **Custom script** column is now available in the **Active sites** page under **Sites**. +++The column can be added to any view. A new **Custom script allowed sites** is also available to provide an easy access to all the sites where custom script is enabled: + ### Change custom script settings-In the "Active sites" page, upon selecting a site, under "settings", a "Custom scripts" setting is available for administrators: - ++In the **Active sites** page, upon selecting a site, under **settings**, a **Custom scripts** setting is available for administrators: + Administrators can control custom script settings for a specific site; deciding if they want to allow or block custom script on a specific site:- + By default, any changes to custom script settings for a specific site only last for a maximum of 24 hours. After that time, the setting will reset to its original value for that specific site. ### Persist custom script settings+ To prevent SharePoint in resetting custom script settings to its original value to the whole tenant follow these steps: 1. [Download the latest SharePoint Online Management Shell](https://go.microsoft.com/fwlink/p/?LinkId=255251). To prevent SharePoint in resetting custom script settings to its original value ``` > [!NOTE]-This setting affects all sites. There are no options to preserve changes to custom script settings only on some specific sites. This parameter will be available until November 2024. After that date, it will no longer be possible to prevent SharePoint in resetting custom script settings to its original value for all sites. +> This setting affects all sites. There are no options to preserve changes to custom script settings only on some specific sites. This parameter will be available until November 2024. After that date, it will no longer be possible to prevent SharePoint in resetting custom script settings to its original value for all sites. ## Features affected when custom script is blocked The following site settings are unavailable when users are prevented from runnin | Site feature | Behavior | Notes | |:--|:--|:--|-|Save Site as Template <br/> |No longer available in Site Settings <br/> |Users can still build sites from templates created before custom script was blocked. <br/> | -|Save document library as template <br/> |No longer available in Library Settings <br/> |Users can still build document libraries from templates created before custom script was blocked. <br/> | -|Save list as template <br/> | No longer available in List Settings <br/> |Users can still build lists from templates created before custom script was blocked. <br/> | -|Solution Gallery <br/> |No longer available in Site Settings <br/> |Users can still use solutions created before custom script was blocked. <br/> | -|Theme Gallery <br/> |No longer available in Site Settings <br/> |Users can still use themes created before custom script was blocked. <br/> | -|Help Settings <br/> |No longer available in Site Settings <br/> |Users can still access help file collections available before custom script was blocked. <br/> | -|Sandbox solutions <br/> |Solution Gallery is no longer available in Site Settings <br/> |Users can't add, manage, or upgrade sandbox solutions. They can still run sandbox solutions that were deployed before custom script was blocked. <br/> | -|SharePoint Designer <br/> |Pages that are not HTML can no longer be updated. <br/> Handling List: **Create Form** and **Custom Action** will no longer work. <br/> Subsites: **New Subsite** and **Delete Site** redirect to the **Site Settings** page in the browser. <br/> Data Sources: **Properties** button is no longer available. <br/> |Users can still open some data sources. To open a site that does not allow custom script in SharePoint Designer, you must first open a site that does allow custom script. <br/> | -|Uploading files that potentially include script <br/> |The following file types can no longer be uploaded to a library <br/> .asmx <br/> .ascx <br/> .aspx <br/> .htc <br/> .jar <br/> .master <br/> .swf <br/> .xap <br/> .xsf <br/> |Existing files in the library are not impacted. <br/> | -|Uploading Documents to Content Types <br/>|Access denied message when attempting to attach a document template to a Content Type. <br/>|We recommend using Document Library document templates. | -|Publishing of SharePoint 2010 Workflows <br/>|Access denied message when attempting to publish a SharePoint 2010 Workflow. <br/>| | +|Save Site as Template |No longer available in Site Settings |Users can still build sites from templates created before custom script was blocked. | +|Save document library as template |No longer available in Library Settings |Users can still build document libraries from templates created before custom script was blocked. | +|Save list as template | No longer available in List Settings |Users can still build lists from templates created before custom script was blocked. | +|Solution Gallery |No longer available in Site Settings |Users can still use solutions created before custom script was blocked. | +|Theme Gallery |No longer available in Site Settings |Users can still use themes created before custom script was blocked. | +|Help Settings |No longer available in Site Settings |Users can still access help file collections available before custom script was blocked. | +|Sandbox solutions |Solution Gallery is no longer available in Site Settings |Users can't add, manage, or upgrade sandbox solutions. They can still run sandbox solutions that were deployed before custom script was blocked. | +|SharePoint Designer |Pages that are not HTML can no longer be updated. <br/> Handling List: **Create Form** and **Custom Action** will no longer work. <br/> Subsites: **New Subsite** and **Delete Site** redirect to the **Site Settings** page in the browser. <br/> Data Sources: **Properties** button is no longer available. |Users can still open some data sources. To open a site that does not allow custom script in SharePoint Designer, you must first open a site that does allow custom script. | +|Uploading files that potentially include script |The following file types can no longer be uploaded to a library <br/> .asmx <br/> .ascx <br/> .aspx <br/> .htc <br/> .jar <br/> .master <br/> .swf <br/> .xap <br/> .xsf |Existing files in the library are not impacted. | +|Uploading Documents to Content Types |Access denied message when attempting to attach a document template to a Content Type. |We recommend using Document Library document templates. | +|Publishing of SharePoint 2010 Workflows |Access denied message when attempting to publish a SharePoint 2010 Workflow. | | The following web parts and features are unavailable to site admins and owners when you prevent them from running custom script. | Web part category | Web part | |:--|:--|-|Business Data <br/> |Business Data Actions <br/> Business Data Item <br/> Business Data Item Builder <br/> Business Data List <br/> Business Data Related List <br/> Excel Web Access <br/> Indicator Details <br/> Status List <br/> Visio Web Access <br/> | -|Community <br/> |About This Community <br/> Join <br/> My Membership <br/> Tools <br/> What's Happening <br/> | -|Content Rollup <br/> |Categories <br/> Project Summary <br/> Relevant Documents <br/> RSS Viewer <br/> Site Aggregator <br/> Sites in Category <br/> Term Property <br/> Timeline <br/> WSRP Viewer <br/> XML Viewer <br/> | -|Document Sets <br/> |Document Set Contents <br/> Document Set Properties <br/> | -|Advanced <br/> |Embed <br/> | -|Forms <br/> |HTML Form Web Part <br/> | -|Media and Content <br/> |Content Editor <br/> Script Editor <br/> Silverlight Web Part <br/> | -|Search <br/> |Refinement <br/> Search Box <br/> Search Navigation <br/> Search Results <br/> | -|Search-Driven Content <br/> |Catalog-Item Reuse <br/> | -|Social Collaboration <br/> |Contact Details <br/> Note Board <br/> Organization Browser <br/> Site Feed <br/> Tag Cloud <br/> User Tasks <br/> | -|Master Page Gallery <br/> |Can't create or edit master pages <br/> | -|Publishing Sites <br/> |Can't create or edit master pages and page layouts <br/> | +|Business Data |Business Data Actions <br/> Business Data Item <br/> Business Data Item Builder <br/> Business Data List <br/> Business Data Related List <br/> Excel Web Access <br/> Indicator Details <br/> Status List <br/> Visio Web Access | +|Community |About This Community <br/> Join <br/> My Membership <br/> Tools <br/> What's Happening | +|Content Rollup |Categories <br/> Project Summary <br/> Relevant Documents <br/> RSS Viewer <br/> Site Aggregator <br/> Sites in Category <br/> Term Property <br/> Timeline <br/> WSRP Viewer <br/> XML Viewer | +|Document Sets |Document Set Contents <br/> Document Set Properties | +|Advanced |Embed | +|Forms |HTML Form Web Part | +|Media and Content |Content Editor <br/> Script Editor <br/> Silverlight Web Part | +|Search |Refinement <br/> Search Box <br/> Search Navigation <br/> Search Results | +|Search-Driven Content |Catalog-Item Reuse | +|Social Collaboration |Contact Details <br/> Note Board <br/> Organization Browser <br/> Site Feed <br/> Tag Cloud <br/> User Tasks | +|Master Page Gallery |Can't create or edit master pages | +|Publishing Sites |Can't create or edit master pages and page layouts | ## Best practice for communicating script setting changes to users Before you prevent custom script on sites where you previously allowed it, we recommend communicating the change well in advance so users can understand the impact of it. Otherwise, users who are accustomed to changing themes or adding web parts on their sites will suddenly not be able to and will see the following error message. - Communicating the change in advance can reduce user frustration and support calls. |
| SharePoint | Document Library Version History Limits | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/document-library-version-history-limits.md | Version history limits are applied in the following ways: In the following example, default organization limits are applied to new libraries created on marketing and sales sites as these sites do not have site level limits applied. Legal site has site level limits applied and broken inheritance from the organization defaults. Libraries created in the legal site follow the limits applied at the legal site level. The following figure shows the workflow of applying a version limit on new document libraries. When a new library is created, site level setting check is performed. If no site setting is defined, the organization default setting is applied to new libraries. There are two version history settings that admins can use to configure version ### Automatic Setting -Automatic setting is recommended for optimized version storage. It combines the data recovery benefits that version history offers while optimizing for its storage. For admins, this setting offers the most optimal storage option without having to estimate the version count or age limits needed to meet the diversified need of their end users.<br> +Automatic setting is recommended for optimized version storage. It combines the data recovery benefits that version history offers while optimizing for its storage. For admins, this setting offers the most optimal storage option without having to estimate the version count or age limits needed to meet the diversified need of their end users.<br> For more information, see [version storage under automatic limits](plan-version-storage.md#understand-version-storage-under-automatic-limits). ### Manual setting -The manual setting allows admins to set count limits on the number of major versions or to set expiration and count limits. When this option is selected, the admins can configure it in the following ways. +The manual setting allows admins to set count limits on the number of major versions or to set expiration and count limits. When this option is selected, the admins can configure it in the following ways. For more information, see [setting the right limits for your organization](plan-version-storage.md#determine-right-count-or-expiration-version-limits). - **Major version limit with expiration period**: Versions are deleted after exceeding either the set number of major versions or after the set period of time. For example, if you configure a library to store 500 major versions with a 365-day expiration, the system stores no more than 500 versions, and automatically deletes any version older than 365 days. - **Major version limits with no expiration period**: Versions are deleted after they exceed the set number of major versions. For example, if a library is configured to store 500 major versions, no more than 500 versions is stored for each file or item. -The UI doesn't allow a value less than 100 major versions or less than 30 days expiration time limits to be set, but it's possible to set the system to store fewer versions using public APIs. For reliability, any value less than 100 versions or less than 30 days expiration time limit isn't recommended and can result in the user activity causing an inadvertent data loss. > [!NOTE]-> If time version history limits are configured on a library, the file version expiration date is stamped on a version at creation time. The expiration date set on a file version is determined from the SnapshotDate of the version which is the date a version became a historical version. The SnapshotDate might be estimated if the version was snapshotted before January 1, 2023. +> - The UI doesn't allow a value less than 100 major versions or less than 30 days expiration time limits to be set, but it's possible to set the system to store fewer versions using public APIs. For reliability, any value less than 100 versions or less than 30 days expiration time limit isn't recommended and can result in the user activity causing an inadvertent data loss. +> +> - If time version history limits are configured on a library, the file version expiration date is stamped on a version at creation time. The expiration date set on a file version is determined from the SnapshotDate of the version which is the date a version became a historical version. The SnapshotDate might be estimated if the version was snapshotted before January 1, 2023. |
| SharePoint | Manage Teams Sharepoint Experiences | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/manage-teams-sharepoint-experiences.md | Teams-connected sites include additional information to indicate the connection  -In the site, the **Go to channel** link is available in the command bar when viewing document libraries. For the parent site, this link redirects to Teams and the general channel for the team. For the channel sites, it links to the channel in teams. +In the site, the **In channels** section is available in the command bar when viewing document libraries. You can select to open each channel's folder. When hovering over each folder, you can select the Teams icon next to folder to navigate to the Teams channel. For example, the Teams icon next to the "General" folder leads you to Teams and the general channel for the team. - --In the parent team site, the **Go to channel** link will be available in the command bar when viewing document libraries. -- --Additionally, from teams and channels in Microsoft Teams, you can select the ellipsis (...) at the top-right of the channel and then **Open in SharePoint** to navigate to the Teams connected team site or channel site in SharePoint. +Additionally, from teams and channels in Microsoft Teams, you can select the **Files** tab at the top of the channel and then **Open in SharePoint** to navigate to the Teams connected team site or channel site in SharePoint. ## Manage settings and permissions |
| SharePoint | Plan Version Storage | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/plan-version-storage.md | Take an example of a file where 500 versions were created in May, June, and July ## Understand version storage under automatic limits -When this option is selected, SharePoint employs an algorithm* behind the scenes. This algorithm deletes (thins out) intermittent older versions that are least likely to be needed, while preserving sufficient high-value versions. More versions in the recent past and fewer further back in time - in case restores are required. The algorithm is based on the design principle that the restore value of a version degrades as the version ages and offers end users' access to most of the recently created versions with fewer older versions. --In other words, SharePoint thins out low-value versions on your behalf to reduce the impact of versions on your quota consumption while maintaining your ability to recover from file deletion/corruption events. In addition, this method better protects you than does a count limit setting from a ransomware attack that creates many versions that would fill up your version queue. --*The algorithm behind automatic version history limits is based on the design principle that restore value of a version that degrades as the version ages. When Automatic limit is selected, SharePoint deletes (thins out) intermittent older versions that are least likely to be used, while preserving sufficient high-value versions. This ensures users have access to more versions in the recent past and fewer farther back in time in case restores are required. +The algorithm behind automatic version history limits is based on the design principle that restores value of a version that degrades as the version ages. When Automatic limit is selected, SharePoint deletes (thins out) intermittent older versions that are least likely to be used, while preserving sufficient high-value versions. In case restores are required, it ensures that users have access to more versions in the recent past and fewer farther back in time. Version storage under Automatic setting is determined by the following algorithm: |
| SharePoint | Provision Neo Hub | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/provision-neo-hub.md | description: "Overview of the Microsoft New Employee Onboarding sites" # Overview of the Microsoft New Employee Onboarding sites -There are three (3) new templates for New Employee Onboarding (NEO) to help organizations improve their onboarding process. The NEO sites are designed to deliver a flexible and consistent experience. The NEO sites can be used on their own, or together. +There are three (3) templates for New Employee Onboarding (NEO) to help organizations improve their onboarding process. The NEO sites are designed to deliver a flexible and consistent experience. The NEO sites can be used on their own, or together. The NEO sites help organizations by: NEO processes often fall short for both the new hires and the organization. Only New employee onboarding involves multiple levels within an organization, including preonboarding, corporate onboarding, and departmental onboarding. Each onboarding level provides its own unique value, contributing to a comprehensive onboarding experience each new employee should experience. -Research has shown Preonboarding new hires, after they sign their acceptance letter but before they officially join the company, can lead to higher performance and better retention rates. To deliver a flexible and consistent onboarding experience, NEO sites consist of three different SharePoint site templates, that are designed to work alone or as one cohesive and familiar experience for new hires. +Research has shown preonboarding new hires, after they sign their acceptance letter but before they officially join the company, can lead to higher performance and better retention rates. To deliver a flexible and consistent onboarding experience, NEO sites consist of three different SharePoint site templates that are designed to work alone or as one cohesive and familiar experience for new hires. |Preonboarding site|Corporate onboarding site|Departmental onboarding site| |::|::|::| |
| SharePoint | Restricted Sharepoint Search | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/restricted-sharepoint-search.md | Restricted SharePoint Search is off by default. If you decide to enable it, Cop - Files that the users viewed, edited, or created. > [!NOTE]-> The limit of up to 100 SharePoint sites includes Hub sites, but not their sub-sites. When you enable Hub sites, the sub-sites under a Hub site are included in the allowed-list but do not count towards the 100-site limit. This approach allows for greater flexibility while still adhering to the existing constraints. When you are picking Hub sites, make sure all the child sites have proper permissions. +> The limit of up to 100 SharePoint sites includes Hub sites, but not their associated sites. When you enable Hub sites, the associated sites of a Hub site are included in the allowed-list but do not count towards the 100-site limit. This approach allows for greater flexibility while still adhering to the existing constraints. When you are picking Hub sites, make sure all the associated sites have proper permissions. The following diagram shows an example of an HR Hub site with eight associated sites:- --Among these eight associated sites: --- Five sites Diversity and Inclusion, Education Credits, Talent Acquisition, Training, and Employee Benefits inherit the HR Hub site permission settings. These five sites have the same permissions the HR Hub site has.-- Two (HR Team site and Benefits site) are private Teams channel sites. Their corresponding Teams channel owners are sites owners in SharePoint and channel members are site members.-- One (Manager Portal) is restricted. Users not in a specified group can't access this site or its content, even if they have permissions to the HR Hub site.+ All eight associated sites plus the HR Hub site are counted as one site in the allowed-list. Let's consider Alex Wilber, a marketing specialist at Contoso Electronics. Before the organization uses Restricted SharePoint Search, Alex can see not only his own personal contents, like his OneDrive files, chats, emails, contents that he owns or visited, but also content from some sites that haven't undergone access permission review or Access Control Lists (ACL) hygiene, and doesn't have data governance applied. For example, Contoso Electronics has a budgeting site with important business information. Most people don't know about this site, so the site owner hasn't set up proper permissions and hasn't followed correct data governance process. The site might be open to some users who aren't allowed to see it, such as Alex. When Alex asks Copilot for some budgeting information, Copilot gets information from the budgeting site. |
| SharePoint | Set Default Org Version Limits | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/set-default-org-version-limits.md | Take an example of Contoso with an existing marketing site with a set of librari > [!IMPORTANT] > - Changes made to organization-level version history limits apply to new SharePoint libraries and OneDrive user accounts created since the change was made. The changes can take upto 24 hours to be reflected on new libraries created. -> - Changes made to organization-level version history limits don't update the history limits on existing document libraries. You can [update settings on existing libraries on individual site](document-library-version-history-limits.md#version-storage-behavior) or libraries. The ability to apply version history limits to existing document libraries at the organization level is not supported. +> - Changes made to organization-level version history limits will not update the limits applied to existing document libraries. To update the existing library settings, you can [set version limits for existing libraries on a site](site-version-limits.md) or [set version limits on a library](library-version-limits.md). The ability to apply version history limits to existing document libraries at the organization level is not supported. > - Changes made to the organization-level version history limits will not trim existing version history to the new limits. To delete existing versions, you can [trim existing versions from a site, library or OneDrive](library-version-limits.md#manage-version-history-limits-for-a-library-using-powershell). The ability to trim existing versions at the organization level is not supported. > - Default Version History limits for your organization is set to Manual version history limits with 500 major version count limit and no expiration. > - Organization-level Document Library version limit settings can be used to configure version settings on libraries only ([List template Base Type = 1](/openspecs/sharepoint_protocols/ms-wssts/8bf797af-288c-4a1d-a14b-cf5394e636cf)). List version settings, creation of major and minor versions, or content approval workflows need to be [configured at individual library or list level](https://support.microsoft.com/en-us/office/enable-and-configure-versioning-for-a-list-or-library-1555d642-23ee-446a-990a-bcab618c7a37). |
| SharePoint | Site Version Limits | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/site-version-limits.md | The following table enumerates the various progress status that can be reported ## Learn More: - [Tutorial: Manage Version history limits for a Site, Library, or OneDrive account (Preview)](tutorial-manage-version-limits.md)-- Manage Version history limits for a Site using [**Set-SPOSite**](/powershell/module/sharepoint-online/set-sposite)-- Review progress of settings update on existing libraries in a Site using Get-SPOSiteVersionPolicyJobProgress-- Cancel an in-progress settings update job using Remove-SPOSiteVersionPolicyJob +- Manage Version history limits for a Site using [Set-SPOSite](/powershell/module/sharepoint-online/set-sposite) +- Track progress of version settings update request for existing document libraries on a site using [Get-SPOSiteVersionPolicyJobProgress](/powershell/module/sharepoint-online/get-spositeversionpolicyjobprogress) +- Cancel further processing of version settings update on existing document libraries on the site collection using [Remove-SPOSiteVersionPolicyJob](/powershell/module/sharepoint-online/remove-spositeversionpolicyjob) + |
| SharePoint | Trim Versions | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/trim-versions.md | Version trimming workflows allow you to select and apply one of the trimming mod **Automatic trim mode:** Applies Automatic algorithm to delete existing versions. Depending on the version age, the job will permanently delete versions or set expiration time according to the automatic version storage algorithm.+ > [!TIP]-> Review the [tutorial to run impact analysis of of setting automatic version history limits](tutorial-run-what-if-analysis.md#run-impact-analysis-of-setting-automatic-version-history-limits) to understand version deletion and expiration criteria. +> Consider [performing a 'What-if' analysis](tutorial-run-what-if-analysis.md#run-impact-analysis-of-setting-automatic-version-history-limits) to understand versions that either will be deleted or have expiration time set on them under the Automatic trim mode. ## Queue trim job and track progress |
| SharePoint | Tutorial Generate Version Usage Report | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/tutorial-generate-version-usage-report.md | After configuring the `TargetExpirationDate` values for your report, you can cho ### Option one: Analyze the report using Excel -Open the shared Excel workbook **AnalyzeReportFile_Template.xlsx**. You can find the following worksheets in it. +Open the shared Excel workbook [AnalyzeReportFile_Template.xlsx](https://download.microsoft.com/download/b/f/e/bfed7844-b840-4854-8897-1272e914ccdd/AnalyzeReportFile_Template.xlsx). You can find the following worksheets in it. - **Configuration**: Use this worksheet to set the date range for generating the different report views. - **Dataset**: This worksheet is the raw dataset imported from the report file. Various reporting summary views are constructed from this dataset. |
| SharePoint | Tutorial Manage Version Limits | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/tutorial-manage-version-limits.md | In this tutorial, you will learn how to manage the version history limits for a - Review your **organizationΓÇÖs recovery objectives** and **version storage use quota targets** along with the **site-specific version storage needs** to evaluate if a break of inheritance of version settings at site, library, or OneDrive account level is needed. - If needed **run an impact analysis** with the desired setting, to understand the impact the new setting would have using current version storage usage patterns.-- For site version settings, evaluate the scope of document libraries that should be updated. Depending on business need, you can choose one of the following:+- For setting site level version limits, evaluate the scope of document libraries that should be updated. Depending on business need, you can choose one of the following: - Update new libraries only without impacting existing library settings. - Update existing libraries only and inherit organization default settings for new libraries. - Update both existing and all new libraries for consistent version storage at the site level. |