| Service | Microsoft Docs article | Related commit history on GitHub | Change details |
|---|---|---|---|
| SharePoint | Employee Resource Template | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/employee-resource-template.md | This template features content focused on an LGBTQ+ employee resource group but As the site collection admin, you may not be the person customizing the site, so you'll need to assign a few site owners. Owners have administrative privileges on the site so they can modify site pages, content, and branding. 1. Select **Share** in the right-hand corner of the site. -2. Add users, Office 365 Groups, or security groups to give them access to the site. +2. Add users, Microsoft 365 Groups, or security groups to give them access to the site. 3. Assign users as a Site owner to allow permission to customize the site. 4. Include the site URL in the Share message, and then select **Share.** After the site has been provisioned and site owners have been added, it's time t  -- **Home page ΓÇô** The landing page features a unique theme, colorful images, and more inspirational content that is relevant and engaging. Content here is inspired by a LGBTQ+ employee resource group but can be adapted to other types of groups. Customize the Text, News, Events, and Quick Links web parts to make this site your own. +- **Home page ΓÇô** The landing page features a unique theme, colorful images, and more inspirational content that is relevant and engaging. Content here is inspired by an LGBTQ+ employee resource group but can be adapted to other types of groups. Customize the Text, News, Events, and Quick Links web parts to make this site your own. - **Page template ΓÇô** A page template with a unique theme can be found in the siteΓÇÖs contents to help create news posts and pages for the site more quickly. - **News web part ΓÇô** Pre-populated news posts were created using the page template. - **Events web part ΓÇô** Pre-populated events from different employee resource groups highlight more opportunities to learn and practice allyship. |
| SharePoint | External Sharing Overview | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/external-sharing-overview.md | When you or your users create Microsoft 365 groups (for example in Outlook, or b ## What happens when users share When users share with people outside the organization, an invitation is sent to the person in email, which contains a link to the shared item.-- **Recipients who sign in** |
| SharePoint | Hispanic Erg Template | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/hispanic-erg-template.md | This template features content focused on a Hispanic and Latinx employee resourc As the site collection admin, you may not be the person customizing the site, so you'll need to assign a few site owners. Owners have administrative privileges on the site so they can modify site pages, content, and branding. 1. Select **Share** in the right-hand corner of the site. -2. Add users, Office 365 Groups, or security groups to give them access to the site. +2. Add users, Microsoft 365 Groups, or security groups to give them access to the site. 3. Assign users as a Site owner to allow permission to customize the site. 4. Include the site URL in the Share message, and then select **Share.** |
| SharePoint | Feature Release Rings | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/administration/feature-release-rings.md | + + Title: "Feature release rings" ++++ Last updated : 09/12/2022+audience: ITPro +f1.keywords: +- NOCSH ++ms.localizationpriority: medium ++- IT_Sharepoint_Server +- IT_Sharepoint_Server_Top +ms.assetid: 88317397-e0cb-47c7-9093-7872bc685213 +description: "Learn about the feature release rings." ++++# Feature release rings +++## Overview ++In previous versions of SharePoint Server, such as SharePoint Server 2019 and SharePoint Server 2016, new feature experiences were introduced at the launch of major new versions. Those versions would be serviced with new security and quality improvements via monthly Public Updates. On rare occasions, new feature experiences may be introduced via a Public Update as well. However, customers would typically have to wait for the next major version of SharePoint Server to be released to get additional feature experiences that weren't part of the initial launch. ++SharePoint Server Subscription Edition brings a more agile approach to how new feature experiences are introduced to SharePoint Server customers. Instead of waiting for the next major version of SharePoint Server to be released, new feature experiences will now be introduced to SharePoint Server Subscription Edition on a regular basis via Feature Updates. Customers will have access to these new feature experiences as soon as they're ready and will have control over how they're made available in their SharePoint farm deployments. ++## Introducing feature updates ++Organizations often desire predictability for when new features are introduced to the products they use. Microsoft will bundle new feature experiences for SharePoint Server Subscription Edition together in **Feature Updates** so that they can be introduced on a predictable schedule. **Feature Updates** will be introduced twice a year, once in the spring and once in the autumn. Feature updates will be incorporated into the monthly **Public Updates**, alongside the typical security and quality updates that customers are used to. Once a new **Feature Update** is released, it will be included in all **Public Updates** going forward. ++Feature Updates will be named based on the calendar year and which half of the year they were released. For example, the feature update released in the autumn of calendar year 2022 is called **SharePoint Server Subscription Edition Version 22H2**. A feature update released in the spring of calendar year 2023 is called **SharePoint Server Subscription Edition Version 23H1**. ++In addition to the desire for predictability of new feature releases, organizations desire the ability to manage the introduction of those new features into their environments. This gives organizations time to train their users and support staff on any new functionality, perform compatibility testing of those new feature experiences with existing customer scenarios, and develop new business processes to take full advantage of the new feature experiences. ++To meet this need, new feature experiences introduced in Feature Updates will be grouped into the following feature release rings: ++- Early release +- Standard release ++### Early release ++In the **Early release** ring, new feature experiences will be enabled in your SharePoint farm as soon as they're ready. These experiences are supported for production use but may change before they're included in the Standard release ring. ++Enable **Early release** to: ++- Use new feature experiences in a production environment as soon as possible. +- Perform compatibility testing and explore new feature experiences in a test environment and provide feedback to Microsoft. +- Prepare your internal help desk and user documentation for new feature experiences. ++### Standard release ++In the **Standard release** ring, new feature experiences are enabled in your SharePoint farm once they're ready for all customers to use by default. These feature experiences are supported for production use and have received additional validation during **Early release**. Enable **Standard release** if you prefer to minimize changes to your SharePoint experience and are willing to wait longer for new feature experiences. **Standard release** is the default feature release ring. ++## Selecting feature release preference ++SharePoint Server Subscription Edition farms are part of the Standard release ring by default. At any time, customers can choose to move from the Standard release ring to the Early release ring, or from the Early release ring to the Standard release ring. New feature experiences will be enabled or disabled based on the feature release selected for the SharePoint farm. ++Follow these steps to select a feature release preference for your SharePoint farm: ++1. Browse to **SharePoint Central Administration**. +2. Click **System Settings**. +3. Click **Feature release preference**. +4. Select either **Early release** or **Standard release (Default)**, and then click **OK**. +5. Run **SharePoint Products Configuration Wizard** on each server in your SharePoint farm to ensure all features recognize the new feature release preference. ++> [!NOTE] +> Currently, the feature release preference cannot be configured using a PowerShell cmdlet. + |
| SharePoint | Configure Properties Of The Search Box Web Part | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/search/configure-properties-of-the-search-box-web-part.md | By default, the Search Box Web Part is used on the home page for the Search Cent >- [Plan browser support](../install/browser-support-planning.md) >- [Accessibility for SharePoint 2013](../accessibility-guidelines.md) >- [Accessibility features in SharePoint 2013 Products](https://go.microsoft.com/fwlink/p/?LinkId=246501)->- [Keyboard shortcuts](https://go.microsoft.com/fwlink/p/?LinkID=246504) +>- [Keyboard shortcuts](https://support.microsoft.com/office/keyboard-shortcuts-in-sharepoint-online-466e33ee-613b-4f47-96bb-1c20f20b1015) >- [Touch](/windows/win32/wintouch/windows-touch-gestures-overview) ## Configure properties of the Search Box Web Part |
| SharePoint | Configure Properties Of The Search Navigation Web Part | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/search/configure-properties-of-the-search-navigation-web-part.md | For more information, see the following resources: - [Accessibility features in SharePoint 2013 Products](https://go.microsoft.com/fwlink/p/?LinkId=246501) -- [Keyboard shortcuts](https://go.microsoft.com/fwlink/p/?LinkID=246504)+- [Keyboard shortcuts](https://support.microsoft.com/office/keyboard-shortcuts-in-sharepoint-online-466e33ee-613b-4f47-96bb-1c20f20b1015) - [Touch](/windows/win32/wintouch/windows-touch-gestures-overview) |
| SharePoint | Configure Properties Of The Search Results Web Part | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/search/configure-properties-of-the-search-results-web-part.md | By changing the properties and query in the Search Results Web Part you can you >- [Plan browser support](../install/browser-support-planning.md) >- [Accessibility for SharePoint 2013](../accessibility-guidelines.md) >- [Accessibility features in SharePoint 2013 Products](https://go.microsoft.com/fwlink/p/?LinkId=246501)->- [Keyboard shortcuts](https://go.microsoft.com/fwlink/p/?LinkID=246504) +>- [Keyboard shortcuts](https://support.microsoft.com/office/keyboard-shortcuts-in-sharepoint-online-466e33ee-613b-4f47-96bb-1c20f20b1015) >- [Touch](/windows/win32/wintouch/windows-touch-gestures-overview) ## Configure properties of the Search Results Web Part |
| SharePoint | Configure Trust For Search Between Two Sharepoint Server Farms | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/search/configure-trust-for-search-between-two-sharepoint-server-farms.md | In order for SendingFarm to be able to get search results from the search index >- [Plan browser support](../install/browser-support-planning.md) >- [Accessibility for SharePoint 2013](../accessibility-guidelines.md) >- [Accessibility features in SharePoint 2013](https://go.microsoft.com/fwlink/p/?LinkId=246501)->- [Keyboard shortcuts](https://go.microsoft.com/fwlink/p/?LinkID=246504) +>- [Keyboard shortcuts](https://support.microsoft.com/office/keyboard-shortcuts-in-sharepoint-online-466e33ee-613b-4f47-96bb-1c20f20b1015) >- [Touch](/windows/win32/wintouch/windows-touch-gestures-overview) **To configure ReceivingFarm to trust SendingFarm** |
| SharePoint | Export And Import Customized Search Configuration Settings | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/search/export-and-import-customized-search-configuration-settings.md | Before you begin this operation, review the information in [Overview of customiz >- [Plan browser support](../install/browser-support-planning.md) >- [Accessibility for SharePoint 2013](../accessibility-guidelines.md) >- [Accessibility features in SharePoint 2013 Products](https://go.microsoft.com/fwlink/p/?LinkId=246501)->- [Keyboard shortcuts](https://go.microsoft.com/fwlink/p/?LinkID=246504) +>- [Keyboard shortcuts](https://support.microsoft.com/office/keyboard-shortcuts-in-sharepoint-online-466e33ee-613b-4f47-96bb-1c20f20b1015) >- [Touch](/windows/win32/wintouch/windows-touch-gestures-overview) ## Export customized search configuration settings from a site collection |
| SharePoint | Configure Amsi Integration | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/security-for-sharepoint-server/configure-amsi-integration.md | + + Title: "Configure AMSI integration with SharePoint Server" ++++ Last updated : 09/12/2022+audience: ITPro +f1.keywords: +- NOCSH ++ms.localizationpriority: medium ++- IT_Sharepoint_Server +- IT_Sharepoint_Server_Top +ms.assetid: 763613ac-83f4-424e-99d0-32efd0667bd9 +description: "Learn to secure environments and respond to associated threats from the attacks through AMSI." +++# Configure AMSI integration with SharePoint Server +++## Introduction ++The cybersecurity landscape has fundamentally changed, as evidenced by large-scale, complex attacks, and signals that [human-operated ransomware](/security/compass/human-operated-ransomware) are on the rise. More than ever, it's critical to keep your on-premises infrastructure secure and up to date, including SharePoint Servers. ++To help customers secure their environments and respond to associated threats from the attacks, we're introducing integration between SharePoint Server and the Windows +[Antimalware Scan Interface](/windows/win32/amsi/antimalware-scan-interface-portal) (AMSI). AMSI is a versatile standard that allows applications and services to integrate with any AMSI-capable anti-malware product present on a computer. ++## AMSI integration with SharePoint Server ++When an AMSI-capable antivirus or anti-malware solution is integrated with SharePoint Server, it can examine the content of `HTTP` and `HTTPS` requests made to the server and prevent dangerous requests from being processed by SharePoint Server. Any AMSI-capable antivirus or anti-malware program that is installed on the server performs the scan as soon as the server starts to process the request. The purpose of AMSI isn't to replace current server-level antivirus/anti-malware defenses; it solely scans the `HTTP` and `HTTPS` protocols. ++## Prerequisites ++Before enabling AMSI integration, check the following prerequisites on each SharePoint Server: ++- Windows Server 2016 or higher +- SharePoint Server Subscription Edition Version 22H2 or higher +- Microsoft Defender with AV engine version at 1.1.18300.4 or higher (alternatively, a compatible AMSI-capable third-party antivirus/antimalware provider) ++## Activate/Deactivate AMSI for SharePoint Server ++The AMSI integration with SharePoint Server is deactivated by default. ++Follow these steps to activate/deactivate the AMSI integration per web application: ++1. Open **SharePoint Central Administration**, and click **Application Management**. +2. Under **Web Applications**, select **Manage web applications**. +3. Click the web application for which you want to enable the AMSI integration, and select **Manage Features** in the toolbar. +4. On the **SharePoint Server Antimalware Scanning** screen, click **Activate** to turn on AMSI intergration, or click **Deactivate** to turn off AMSI integration. ++Alternatively, you can activate AMSI integration for a web application by running the following PowerShell commands: ++```powershell +Enable-SPFeature -Identity 4cf046f3-38c7-495f-a7da-a1292d32e8e9 -Url <web application URL> +``` +Or deactivate AMSI integration for a web application via this PowerShell command: ++```powershell +Disable-SPFeature -Identity 4cf046f3-38c7-495f-a7da-a1292d32e8e9 -Url <web application URL> +``` ++## Other references ++**Performance effects of using Microsoft Defender as the primary AMSI solution** ++By default, [Microsoft Defender Antivirus](https://support.microsoft.com/windows/stay-protected-with-windows-security-2ae0363d-0ada-c064-8b56-6a39afb6a963) (MDAV), an AMSI-capable solution, is automatically enabled and installed on endpoints and devices that are running Windows 10, Windows Server 2016, and later. If you haven't installed an antivirus/anti-malware application, SharePoint Server AMSI integration will work with MDAV. If you install and enable another antivirus/anti-malware application, MDAV will automatically turn off. If you uninstall the other app, MDAV will automatically turn back on, and the SharePoint Server integration will work with MDAV. ++The benefits of using MDAV on SharePoint Server include: +- MDAV fetches signatures that match malicious content. If Microsoft learns about an exploit that can be blocked, a new MDAV signature can be deployed to block the exploit from affecting SharePoint. +- Using existing technology to add signatures for the malicious content. +- Using the expertise of Microsoft's malware research team for adding signatures. +- Using best practices that MDAV already applies for adding other signatures. ++There may be a performance impact on the web application because AMSI scanning uses CPU resources. There's no distinct performance impact observed from AMSI scanning when tested with MDAV and no changes to be made to the existing documented SharePoint Server antivirus exclusions. Each antivirus provider develops their own definitions that utilize AMSI technology. Therefore, your level of protection remains dependent on how quickly your specific solution can be updated to detect the latest threats. ++**Microsoft Defender version via the command line** +> [!NOTE] +> If you are using Microsoft Defender, you can use the command line and ensure to update the signatures with the latest version. ++1. Launch `Command Prompt` as an Administrator. +2. Navigate to `%ProgramData%\Microsoft\Windows Defender\Platform\<antimalware platform version>`. +3. Run `mpcmdrun.exe -SignatureUpdate`. ++This will determine your current engine version, check for updated definitions, and report. ++```powershell +Copyright (C) Microsoft Corporation. All rights reserved. +C:\ProgramData\Microsoft\Windows Defender\Platform\4.18.2105.5-0>MpCmdRun.exe -SignatureUpdate +Signature update started . . . +Service Version: 4.18.2106.6 +Engine Version: 1.1.18300.4 +AntiSpyware Signature Version: 1.343.1364.0 +AntiVirus Signature Version: 1.343.1364.0 +Signature update finished. No updates needed +C:\ProgramData\Microsoft\Windows Defender\Platform\4.18.2105.5-0> +``` + |
| SharePoint | Access Services In Sharepoint Server | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/technical-reference/access-services-in-sharepoint-server.md | Download and install: - [System Center Monitoring Pack for SharePoint Server 2013](https://go.microsoft.com/fwlink/p/?LinkId=272568) -- [System Center Monitoring Pack for SharePoint Foundation 2013](https://go.microsoft.com/fwlink/p/?LinkId=272567)+- [System Center Monitoring Pack for SharePoint Foundation 2013](https://www.microsoft.com/download/details.aspx?id=35590) Use the following information to resolve the Access Services error messages: One or more of the following might be the cause: #### Other Resources -[System Center Monitoring Pack for SharePoint Foundation](https://go.microsoft.com/fwlink/p/?LinkId=272567) +[System Center Monitoring Pack for SharePoint Foundation](https://www.microsoft.com/download/details.aspx?id=35590) [System Center Monitoring Pack for SharePoint Server 2013](https://go.microsoft.com/fwlink/p/?LinkId=272568) |
| SharePoint | Machine Translation Service In Sharepoint Server | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/technical-reference/machine-translation-service-in-sharepoint-server.md | Download and install: - [System Center Monitoring Pack for SharePoint Server 2013](https://go.microsoft.com/fwlink/p/?LinkId=272568) -- [System Center Monitoring Pack for SharePoint Foundation 2013](https://go.microsoft.com/fwlink/p/?LinkId=272567)+- [System Center Monitoring Pack for SharePoint Foundation 2013](https://www.microsoft.com/download/details.aspx?id=35590) Use the following to resolve alerts about the Machine Translation service: Resolution 5: Create a new Machine Translation Service application #### Other Resources -[System Center Monitoring Pack for SharePoint Foundation](https://go.microsoft.com/fwlink/p/?LinkId=272567) +[System Center Monitoring Pack for SharePoint Foundation](https://www.microsoft.com/download/details.aspx?id=35590) [System Center Monitoring Pack for SharePoint Server 2013](https://go.microsoft.com/fwlink/p/?LinkId=272568) -[System Center Monitoring Pack for SharePoint Server 2016](https://go.microsoft.com/fwlink/?LinkID=746863&clcid=0x409) +[System Center Monitoring Pack for SharePoint Server 2016](https://go.microsoft.com/fwlink/?LinkID=746863&clcid=0x409) |
| SharePoint | Search In Sharepoint Server | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/technical-reference/search-in-sharepoint-server.md | Download and install: - [System Center Monitoring Pack for SharePoint Server 2013](https://go.microsoft.com/fwlink/p/?LinkId=272568) -- [System Center Monitoring Pack for SharePoint Foundation 2013](https://go.microsoft.com/fwlink/p/?LinkId=272567)+- [System Center Monitoring Pack for SharePoint Foundation 2013](https://www.microsoft.com/download/details.aspx?id=35590) Use the following to resolve alerts about the search issues: Check and restart the schema service or OM. **Alert Name:** Query Processing: QueryParsing Scope Cache Availability - **Summary:** Query parsing could not work for the particular query because the query rules for the indicated Search Service service Aapplication was not available. + **Summary:** Query parsing could not work for the particular query because the query rules for the indicated Search Service service application weren't available. ### Cause Ensure that the following components are up and running: **Alert Name:** Search Analytics: Timer job cannot resolve Link database - **Summary:** The timer job will check that all Link database partitions are available before it tries to start the search analytics analysis.Symptoms:If the Link database partitions are unavailable when it is time to start a new analysis run, the start try will be aborted. New Link database checks followed by a new start try will be performed in the next timer job polls (every 10 minutes). + **Summary:** The timer job will check that all Link database partitions are available before it tries to start the search analytics analysis. Symptoms: If the Link database partitions are unavailable when it is time to start a new analysis run, the start try will be aborted. New Link database checks followed by a new start try will be performed in the next timer job polls (every 10 minutes). ### Cause One or more of the following might be the cause: - There is a Search service application in the system. - - The Analytics processingcomponent is functioning correctly. + - The Analytics processing component is functioning correctly. - There are no networking issues. Verify other System Center Operations Manager monitors and see whether any paren - There is no problem with disk space. -- There is no metwork connectivity issue.+- There is no network connectivity issue. - The usage analytics timer job is running. One or more of the following might be the cause: **Summary:** Background or symptoms: -1. The information written to the reporting API or database is used if the cache files must be rebuilt. When usage analytics cannot write to the reporting API, this means that the recommendations and data is not updated. Counts presented to the user are therefore out of date, and old or wrong data will also be presented next time that the cache is rebuilt. +1. The information written to the reporting API or database is used if the cache files must be rebuilt. When usage analytics cannot write to the reporting API, this means that the recommendations and data aren't updated. Counts presented to the user are therefore out of date, and old or wrong data will also be presented next time that the cache is rebuilt. 2. The Reporting API could not be read so that no cache files could be created and the analysis will therefore not be run. Running the analysis in this state would in effect overwrite the current data. If persistent or recurring, check the host controller and restart if it is neces #### Other Resources -[System Center Monitoring Pack for SharePoint Foundation](https://go.microsoft.com/fwlink/p/?LinkId=272567) +[System Center Monitoring Pack for SharePoint Foundation](https://www.microsoft.com/download/details.aspx?id=35590) [System Center Monitoring Pack for SharePoint Server 2013](https://go.microsoft.com/fwlink/p/?LinkId=272568) |
| SharePoint | New And Improved Features In Sharepoint Server Subscription Edition 22H2 Release | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/what-s-new/new-and-improved-features-in-sharepoint-server-subscription-edition-22h2-release.md | + + Title: "New and improved features in SharePoint Server Subscription Edition Version 22H2" +++++audience: ITPro +f1.keywords: +- NOCSH ++ms.localizationpriority: high ++- IT_Sharepoint_Server +- IT_Sharepoint_Server_Top +- Strat_SP_server ++description: "Learn about the new features and updates to existing features in SharePoint Server Subscription Edition Version 22H2." +++# New and improved features in SharePoint Server Subscription Edition Version 22H2 +++Learn about the new features and updates introduced in the SharePoint Server Subscription Edition Version 22H2 feature. ++## Summary of the features ++The following table provides a summary of the new features introduced in the SharePoint Server Subscription Edition Version 22H2 feature update. ++|**Feature**|**Release rings**|**More information**| +|:--|:--|:--| +|**Feature release rings** <br/> |Standard release <br/> |For more information, see [Feature release rings](#feature-release-rings). <br/> | +|**AMSI integration** <br/> |Standard release <br/> |For more information, see [AMSI integration](#amsi-integration). <br/> | +|**Copy and move improvement in modern document library** <br/> |Early release <br/> |For more information, see [Copy and move improvement in modern document library](#copy-and-move-improvement-in-modern-document-library).<br/> | +|**Bulk editing in modern lists** <br/> |Early release <br/> |For more information, see [Bulk editing in modern lists](#bulk-editing-in-modern-lists).<br/> | +|**Column formatting enhancement** <br/> |Early release <br/> |For more information, see [Column formatting enhancement](#column-formatting-enhancement).<br/> | +|**Button web part** <br/> |Early release <br/> |For more information, see [Button web part](#button-web-part). <br/> | +|**Choose the default site language in the modern self-service site creation pane** <br/> |Early release <br/> |For more information, see [Choose the default site language in the modern self-service site creation pane](#choose-the-default-site-language-in-the-modern-self-service-site-creation-pane). <br/> | +|**New SharePoint RESTful ListData.svc implementation** <br/> |Early release <br/> |For more information, see [New SharePoint RESTful ListData.svc implementation](#new-sharepoint-restful-listdatasvc-implementation). <br/> | ++## Detailed description of features ++This section provides detailed descriptions of the new and updated features in SharePoint Server Subscription Edition Version 22H2. ++### Feature release rings ++As Microsoft delivers on its promise of an evergreen experience for SharePoint Server Subscription Edition, we recognize that organizations desire the ability to manage the introduction of new feature experiences into their environments. To meet this need, new feature experiences introduced in SharePoint Server Subscription Edition Version 22H2 will be grouped into feature release rings. ++The two rings in this version are as follows: ++- Early release +- Standard release ++In the **Early release** ring, new feature experiences will be enabled in your SharePoint farm as soon as they're ready. These experiences are supported for production use but may change before they're included in the Standard release ring. ++Enable **Early release** to: ++- Use new feature experiences in a production environment as soon as possible. +- Perform compatibility testing and explore new feature experiences in a test environment and provide feedback to Microsoft. +- Prepare your internal help desk and user documentation for new feature experiences. ++In the **Standard release** ring, new feature experiences are enabled in your SharePoint farm once they're ready for all customers to use by default. These feature experiences are supported for production use and have received additional validation during **Early release**. Enable Standard release if you prefer to minimize changes to your SharePoint experience and are willing to wait longer for new feature experiences. **Standard release** is the default feature release ring. ++Customers can switch between these two feature release rings at any time. However, you must run the SharePoint Products Configuration Wizard on every server in your SharePoint farm after changing this setting. The Wizard will perform a repair operation to ensure all features recognize the new setting. ++To learn more about this feature, see [Feature release rings](../administration/feature-release-rings.md). ++### AMSI integration ++The cybersecurity landscape has fundamentally changed, as evidenced by large-scale, complex attacks, and signals that [human-operated ransomware](/security/compass/human-operated-ransomware) are on the rise. More than ever, it's critical to keep your on-premises infrastructure secure and up to date, including SharePoint Servers. ++To help customers secure their environments and respond to associated threats from the attacks, we're introducing integration between SharePoint Server and the Windows +[Antimalware Scan Interface](/windows/win32/amsi/antimalware-scan-interface-portal) (AMSI). AMSI is a versatile standard that allows applications and services to integrate with any AMSI-capable anti-malware product present on a computer. ++When an AMSI-capable antivirus or anti-malware solution is integrated with SharePoint Server, it can examine the content of `HTTP` and `HTTPS` requests made to the server and prevent dangerous requests from being processed by SharePoint Server. Any AMSI-capable antivirus or anti-malware program that is installed on the server performs the scan as soon as the server starts to process the request. The purpose of AMSI isn't to replace current server-level antivirus/anti-malware defenses; it solely scans the `HTTP` and `HTTPS` protocols. ++To learn more about this feature, see [Configure AMSI integration with SharePoint Server](../security-for-sharepoint-server/configure-amsi-integration.md). ++### Copy and move improvement in modern document library ++SharePoint Server Subscription Edition Version 22H2 enhances the modern document library experience by supporting copying and moving files across document libraries. In the new experience, when a user picks a file or multiple files and triggers a **copy** or **move** operation, the user will have the option to pick a destination outside the current document library. +- **Copy** will allow users to pick a destination location in different subsites, in different site collections, and in different web applications. +- **Move** will allow users to pick a destination location in different document libraries in the same site. ++If the same term store is used in both the source and destination locations, the metadata of the file will be maintained rather than being copied or moved. ++> [!NOTE] +> A document's version history will be preserved during move operations, but it won't be preserved during copy operations for the new copy of the document. ++To learn more about this feature, see [Move or copy files in SharePoint](https://support.microsoft.com/office/move-or-copy-files-in-sharepoint-00e2f483-4df3-46be-a861-1f5f0c1a87bc). ++### Bulk editing in modern lists ++SharePoint Server Subscription Edition Version 22H2 improves the bulk editing experience for list items in the modern lists. The users can now select multiple list items in a modern list and then click the new **Edit** button in the list toolbar. This will open an expanded editing pane where the user can update fields for all the selected list items at once. ++To learn more about this feature, see [Bulk edit list item properties](https://support.microsoft.com/office/bulk-edit-list-item-properties-1521a373-b011-4a26-8fc9-016b491ee932). ++### Column formatting enhancement ++SharePoint Server Subscription Edition Version 22H2 allows you to customize how fields in SharePoint lists and libraries are displayed to the users. This feature gives you the capability to visualize data in various different ways to meet your needs, from applying color and other formatting to quickly understand the data at a glance, to powerful custom actions based on the state of the data. With a rich and flexible set of potential customizations, column formatting makes working with SharePoint lists and libraries much more engaging. This feature enhances the column formatting capabilities of the modern UX by adding support for Excel-style expressions and also supports Abstract Syntax Tree (AST) expressions. ++To learn more about this feature, see [Use column formatting to customize SharePoint](https://support.microsoft.com/office/column-formatting-1f927342-2bed-4745-b727-ff8b7ff96b22). ++### Button web part ++When you add a modern page to a site, you add and customize web parts, which are the building blocks of your page. The Button web part lets you easily add a button to your page with your own label and link. You can create an actionable button inside modern pages by adding it through the toolbox. ++To learn more about this feature, see [Use the Button web part](https://support.microsoft.com/office/use-the-button-web-part-d2e37c48-11e8-45b9-8d9e-abdaa97c2a7a). ++### Choose the default site language in the modern self-service site creation pane ++Previously, when creating a new site via the SharePoint start page, users couldn't select the default language of the site. The newly created site would use the default language of the web application. Starting in SharePoint Server Subscription Edition Version 22H2, a language selection control has been added to the modern site creation pane. Users can now create new sites with a specific language by selecting the desired language with that control. ++### New SharePoint RESTful ListData.svc implementation ++*ListData.svc* has been rebuilt so that it no longer depends on the WCF Data Services components while maintaining compatibility with the functionality of the prior design. When your farm is in the **Early release** ring, the new design is activated. You can go back to the original architecture if the *ListData.svc* web service exhibits unexpected behavior by switching the farm back to the **Standard release** ring. |