Microsoft has released Feature Update 25H2 for SharePoint Server Subscription Edition. Expands security and document capabilities, introduces Document Intelligence and moves five previously introduced features to Standard release.
The update was released as part of the September CU, KB5002784, build 16.0.19127.20100. The 25H2 features will also be included in subsequent public updates.
New features and promotion to Standard release
Feature Update 25H2 introduces the following changes:
| Feature | Status in 25H2 | What it provides |
|---|---|---|
| Per-Database Connection Encryption Settings | New in Standard release | Allows separate connection encryption settings for content and service application databases. |
| New web part editing experience powered by CKEditor lib v5 | New in Standard release | Replaces CKEditor 4 with version 5 for newly created Text and Events web parts. |
| New PowerShell Cmdlet to Validate Defender and AMSI Integration | New in Standard release | Adds the diagnostic Test-DefenderAndAmsiWorkProperly cmdlet to verify Defender and AMSI integration. |
| Support JWE encrypted tokens from Entra ID | New in Early release | Supports processing encrypted JWE authentication tokens issued by Microsoft Entra ID. |
| Drag and drop functionality for web parts in publishing sites | New in Early release | Allows dragging web parts between sections and changing their order on publishing sites in modern browsers. |
| Modern People Card | New in Early release | Displays a user card with profile and contact information in lists and libraries. |
| Document Intelligence | New in Early release | Adds AI document summarization through Azure OpenAI. Requires Azure resources, configuration and feature activation. |
| AMSI Body Scan Defaults to “Full Mode” | New in Early release | Sets Full Mode as the default mode for AMSI scanning of HTTP request bodies. |
| Enhance Document Virus Check with AMSI Option | New in Early release | Enables document malware scanning during upload and download through an AMSI-compatible solution. |
| New enhancements for the Text web part | New in Early release | Adds more accessible tables and expands image insertion, including uploads and pasting from the clipboard. |
| Support for automatic machine key rotation | Promoted to Standard release | Automates regular ASP.NET machine-key replacement through the Machine Key Rotation Job. |
| Dynamic customer survey by One Customer Voice | Promoted to Standard release | Replaces the original OCV survey with dynamic surveys with configurable questions and frequency. |
| Create new Office files in client apps | Promoted to Standard release | Allows creating documents from a library in desktop Office applications even when OOS is unavailable. |
| Support for request body scan in AMSI | Promoted to Standard release | Extends AMSI scanning to HTTP request bodies with Balanced and Full modes. |
| Cloud Hybrid Search upgrade | Promoted to Standard release | Upgrades Cloud Hybrid Search. Requires farm patching and Cloud SSA reonboarding to Microsoft 365. |
For automatic machine-key rotation, the September CU changes the schedule from monthly to weekly and adds execution after each update cycle. AMSI request-body scanning moves to Standard release, while making Full Mode the default remains a new Early release capability in this version.
Standard release versus Early release
Standard release is the default farm setting. Features reach this ring after additional validation in Early release. Early release provides earlier access to new features and is supported by Microsoft for production use, although their behaviour may change before promotion to Standard release. See the release rings documentation for details.
To validate changes first, use Early release in a test farm. Check custom solutions and common user workflows, and prepare documentation and user support. Keep production in Standard release if you do not need early access to new features. Continue installing security updates regularly when using Standard release.
How to change the farm setting
Go to Central Administration → System Settings → Feature release preference. The setting applies to the entire farm. After changing it, run the SharePoint Products Configuration Wizard on every server in the farm. This is also required when switching through PowerShell.


