diff --git a/.github/workflows/generate-preview-links.yml b/.github/workflows/generate-preview-links.yml
index 6deb553ebd2f3..f29384314db28 100644
--- a/.github/workflows/generate-preview-links.yml
+++ b/.github/workflows/generate-preview-links.yml
@@ -13,6 +13,7 @@ jobs:
     runs-on: ubuntu-latest
     permissions:
       statuses: read
+      checks: write
       pull-requests: write
     steps:
       - name: Harden Runner
@@ -23,3 +24,4 @@ jobs:
       - uses: dotnet/docs-tools/actions/preview-link-generator@main
         with:
           repo_token: ${{ secrets.GITHUB_TOKEN }}
+          annotate_file_warnings: true
diff --git a/docs/ai/evaluation/snippets/evaluate-ai-responses/TestAI.csproj b/docs/ai/evaluation/snippets/evaluate-ai-responses/TestAI.csproj
index e0bc3e7de0354..26ba83c069668 100644
--- a/docs/ai/evaluation/snippets/evaluate-ai-responses/TestAI.csproj
+++ b/docs/ai/evaluation/snippets/evaluate-ai-responses/TestAI.csproj
@@ -11,13 +11,13 @@
   <ItemGroup>
     <PackageReference Include="Azure.AI.OpenAI" Version="2.1.0" />
     <PackageReference Include="Azure.Identity" Version="1.21.0" />
-    <PackageReference Include="Microsoft.Extensions.AI.Abstractions" Version="10.8.3" />
-    <PackageReference Include="Microsoft.Extensions.AI.Evaluation" Version="10.8.0" />
-    <PackageReference Include="Microsoft.Extensions.AI.Evaluation.Quality" Version="10.8.0" />
-    <PackageReference Include="Microsoft.Extensions.AI.OpenAI" Version="10.8.3" />
-    <PackageReference Include="Microsoft.Extensions.Configuration" Version="10.0.10" />
-    <PackageReference Include="Microsoft.Extensions.Configuration.UserSecrets" Version="10.0.10" />
-    <PackageReference Include="Microsoft.NET.Test.Sdk" Version="18.8.1" />
+    <PackageReference Include="Microsoft.Extensions.AI.Abstractions" Version="10.9.0" />
+    <PackageReference Include="Microsoft.Extensions.AI.Evaluation" Version="10.9.0" />
+    <PackageReference Include="Microsoft.Extensions.AI.Evaluation.Quality" Version="10.9.0" />
+    <PackageReference Include="Microsoft.Extensions.AI.OpenAI" Version="10.9.0" />
+    <PackageReference Include="Microsoft.Extensions.Configuration" Version="10.0.11" />
+    <PackageReference Include="Microsoft.Extensions.Configuration.UserSecrets" Version="10.0.11" />
+    <PackageReference Include="Microsoft.NET.Test.Sdk" Version="18.9.0" />
     <PackageReference Include="MSTest" Version="4.3.3" />
   </ItemGroup>
 
diff --git a/docs/ai/evaluation/snippets/evaluate-safety/EvaluateResponseSafety.csproj b/docs/ai/evaluation/snippets/evaluate-safety/EvaluateResponseSafety.csproj
index 8c917a2c6cc4d..3ce3438fac17a 100644
--- a/docs/ai/evaluation/snippets/evaluate-safety/EvaluateResponseSafety.csproj
+++ b/docs/ai/evaluation/snippets/evaluate-safety/EvaluateResponseSafety.csproj
@@ -11,14 +11,14 @@
   <ItemGroup>
     <PackageReference Include="Azure.AI.OpenAI" Version="2.1.0" />
     <PackageReference Include="Azure.Identity" Version="1.21.0" />
-    <PackageReference Include="Microsoft.Extensions.AI.Abstractions" Version="10.8.3" />
-    <PackageReference Include="Microsoft.Extensions.AI.Evaluation" Version="10.8.0" />
-    <PackageReference Include="Microsoft.Extensions.AI.Evaluation.Reporting" Version="10.8.0" />
+    <PackageReference Include="Microsoft.Extensions.AI.Abstractions" Version="10.9.0" />
+    <PackageReference Include="Microsoft.Extensions.AI.Evaluation" Version="10.9.0" />
+    <PackageReference Include="Microsoft.Extensions.AI.Evaluation.Reporting" Version="10.9.0" />
     <PackageReference Include="Microsoft.Extensions.AI.Evaluation.Safety" Version="10.3.0-preview.1.26109.11" />
-    <PackageReference Include="Microsoft.Extensions.AI.OpenAI" Version="10.8.3" />
-    <PackageReference Include="Microsoft.Extensions.Configuration" Version="10.0.10" />
-    <PackageReference Include="Microsoft.Extensions.Configuration.UserSecrets" Version="10.0.10" />
-    <PackageReference Include="Microsoft.NET.Test.Sdk" Version="18.8.1" />
+    <PackageReference Include="Microsoft.Extensions.AI.OpenAI" Version="10.9.0" />
+    <PackageReference Include="Microsoft.Extensions.Configuration" Version="10.0.11" />
+    <PackageReference Include="Microsoft.Extensions.Configuration.UserSecrets" Version="10.0.11" />
+    <PackageReference Include="Microsoft.NET.Test.Sdk" Version="18.9.0" />
     <PackageReference Include="MSTest" Version="4.3.3" />
   </ItemGroup>
 
diff --git a/docs/ai/how-to/snippets/handle-invalid-tool-input/csharp/HandleInvalidToolInput.csproj b/docs/ai/how-to/snippets/handle-invalid-tool-input/csharp/HandleInvalidToolInput.csproj
index 9cc03596550af..a17b8ae9fe95b 100644
--- a/docs/ai/how-to/snippets/handle-invalid-tool-input/csharp/HandleInvalidToolInput.csproj
+++ b/docs/ai/how-to/snippets/handle-invalid-tool-input/csharp/HandleInvalidToolInput.csproj
@@ -8,10 +8,10 @@
   </PropertyGroup>
 
   <ItemGroup>
-    <PackageReference Include="Microsoft.Extensions.AI" Version="10.8.1" />
-    <PackageReference Include="Microsoft.Extensions.AI.OpenAI" Version="10.8.1" />
-    <PackageReference Include="Microsoft.Extensions.Configuration" Version="10.0.10" />
-    <PackageReference Include="Microsoft.Extensions.Configuration.UserSecrets" Version="10.0.10" />
+    <PackageReference Include="Microsoft.Extensions.AI" Version="10.9.0" />
+    <PackageReference Include="Microsoft.Extensions.AI.OpenAI" Version="10.9.0" />
+    <PackageReference Include="Microsoft.Extensions.Configuration" Version="10.0.11" />
+    <PackageReference Include="Microsoft.Extensions.Configuration.UserSecrets" Version="10.0.11" />
   </ItemGroup>
 
 </Project>
diff --git a/docs/ai/quickstarts/snippets/assistants/AIAssistants.csproj b/docs/ai/quickstarts/snippets/assistants/AIAssistants.csproj
index b2e4de73baa1a..5fa861af45d89 100644
--- a/docs/ai/quickstarts/snippets/assistants/AIAssistants.csproj
+++ b/docs/ai/quickstarts/snippets/assistants/AIAssistants.csproj
@@ -10,7 +10,7 @@
   <ItemGroup>
     <PackageReference Include="Azure.AI.OpenAI" Version="2.1.0" />
     <PackageReference Include="Azure.Identity" Version="1.21.0" />
-    <PackageReference Include="OpenAI" Version="2.12.0" />
+    <PackageReference Include="OpenAI" Version="2.13.0" />
   </ItemGroup>
 
 </Project>
diff --git a/docs/ai/quickstarts/snippets/mcp-server/SampleMcpServer.csproj b/docs/ai/quickstarts/snippets/mcp-server/SampleMcpServer.csproj
index 1084fdd5c4e62..5dd028f3c2256 100644
--- a/docs/ai/quickstarts/snippets/mcp-server/SampleMcpServer.csproj
+++ b/docs/ai/quickstarts/snippets/mcp-server/SampleMcpServer.csproj
@@ -33,8 +33,8 @@
   </ItemGroup>
 
   <ItemGroup>
-    <PackageReference Include="Microsoft.Extensions.Hosting" Version="10.0.10" />
-    <PackageReference Include="ModelContextProtocol" Version="2.1.0" />
+    <PackageReference Include="Microsoft.Extensions.Hosting" Version="10.0.11" />
+    <PackageReference Include="ModelContextProtocol" Version="2.2.0" />
   </ItemGroup>
 
 </Project>
diff --git a/docs/ai/snippets/microsoft-extensions-ai/ConsoleAI.CustomClientMiddle/ConsoleAI.CustomClientMiddle.csproj b/docs/ai/snippets/microsoft-extensions-ai/ConsoleAI.CustomClientMiddle/ConsoleAI.CustomClientMiddle.csproj
index f243b556a5664..f798208cff89d 100644
--- a/docs/ai/snippets/microsoft-extensions-ai/ConsoleAI.CustomClientMiddle/ConsoleAI.CustomClientMiddle.csproj
+++ b/docs/ai/snippets/microsoft-extensions-ai/ConsoleAI.CustomClientMiddle/ConsoleAI.CustomClientMiddle.csproj
@@ -8,8 +8,8 @@
   </PropertyGroup>
 
   <ItemGroup>
-    <PackageReference Include="OllamaSharp" Version="5.4.27" />
-    <PackageReference Include="System.Threading.RateLimiting" Version="10.0.10" />
+    <PackageReference Include="OllamaSharp" Version="5.4.30" />
+    <PackageReference Include="System.Threading.RateLimiting" Version="10.0.11" />
   </ItemGroup>
 
   <ItemGroup>
diff --git a/docs/ai/snippets/microsoft-extensions-ai/ConsoleAI.FunctionalityPipelines/ConsoleAI.FunctionalityPipelines.csproj b/docs/ai/snippets/microsoft-extensions-ai/ConsoleAI.FunctionalityPipelines/ConsoleAI.FunctionalityPipelines.csproj
index 2f33127f6a10a..54786603fdc2f 100644
--- a/docs/ai/snippets/microsoft-extensions-ai/ConsoleAI.FunctionalityPipelines/ConsoleAI.FunctionalityPipelines.csproj
+++ b/docs/ai/snippets/microsoft-extensions-ai/ConsoleAI.FunctionalityPipelines/ConsoleAI.FunctionalityPipelines.csproj
@@ -8,8 +8,8 @@
   </PropertyGroup>
 
   <ItemGroup>
-    <PackageReference Include="Microsoft.Extensions.Caching.Memory" Version="10.0.10" />
-    <PackageReference Include="OllamaSharp" Version="5.4.27" />
+    <PackageReference Include="Microsoft.Extensions.Caching.Memory" Version="10.0.11" />
+    <PackageReference Include="OllamaSharp" Version="5.4.30" />
     <PackageReference Include="OpenTelemetry.Exporter.Console" Version="1.17.0" />
   </ItemGroup>
 
diff --git a/docs/ai/snippets/prompt-engineering/multi-turn-chat.csproj b/docs/ai/snippets/prompt-engineering/multi-turn-chat.csproj
index 6a813ad952e16..c56e69ebabd11 100644
--- a/docs/ai/snippets/prompt-engineering/multi-turn-chat.csproj
+++ b/docs/ai/snippets/prompt-engineering/multi-turn-chat.csproj
@@ -10,7 +10,7 @@
 
   <ItemGroup>
     <PackageReference Include="Azure.AI.OpenAI" Version="2.8.0-beta.1" />
-    <PackageReference Include="Microsoft.Agents.AI.OpenAI" Version="1.17.0" />
+    <PackageReference Include="Microsoft.Agents.AI.OpenAI" Version="1.18.0" />
     <!--
     <PackageReference Include="Microsoft.Extensions.Configuration" Version="10.0.2" />
     <PackageReference Include="Microsoft.Extensions.Configuration.UserSecrets" Version="10.0.2" />
diff --git a/docs/ai/vector-stores/snippets/chat-with-data/openai/VectorDataAI.csproj b/docs/ai/vector-stores/snippets/chat-with-data/openai/VectorDataAI.csproj
index f555b7d1c423b..69be09d4afce2 100644
--- a/docs/ai/vector-stores/snippets/chat-with-data/openai/VectorDataAI.csproj
+++ b/docs/ai/vector-stores/snippets/chat-with-data/openai/VectorDataAI.csproj
@@ -9,10 +9,10 @@
   </PropertyGroup>
 
   <ItemGroup>
-    <PackageReference Include="Microsoft.Extensions.AI.OpenAI" Version="10.8.3" />
-    <PackageReference Include="Microsoft.Extensions.Configuration" Version="10.0.10" />
-    <PackageReference Include="Microsoft.Extensions.Configuration.UserSecrets" Version="10.0.10" />
-    <PackageReference Include="CommunityToolkit.VectorData.InMemory" Version="1.0.0" />
+    <PackageReference Include="Microsoft.Extensions.AI.OpenAI" Version="10.9.0" />
+    <PackageReference Include="Microsoft.Extensions.Configuration" Version="10.0.11" />
+    <PackageReference Include="Microsoft.Extensions.Configuration.UserSecrets" Version="10.0.11" />
+    <PackageReference Include="CommunityToolkit.VectorData.InMemory" Version="1.0.1" />
   </ItemGroup>
 
 </Project>
diff --git a/docs/architecture/modern-web-apps-azure/media/image5-8.png b/docs/architecture/modern-web-apps-azure/media/image5-8.png
index 8f01b369b564e..6723c1be30d93 100644
Binary files a/docs/architecture/modern-web-apps-azure/media/image5-8.png and b/docs/architecture/modern-web-apps-azure/media/image5-8.png differ
diff --git a/docs/azure/sdk/snippets/aspnetcore-guidance/MinApiSample/MinApiSample.csproj b/docs/azure/sdk/snippets/aspnetcore-guidance/MinApiSample/MinApiSample.csproj
index 362d4106b1f07..19c64cbe28d26 100644
--- a/docs/azure/sdk/snippets/aspnetcore-guidance/MinApiSample/MinApiSample.csproj
+++ b/docs/azure/sdk/snippets/aspnetcore-guidance/MinApiSample/MinApiSample.csproj
@@ -7,11 +7,11 @@
   </PropertyGroup>
 
   <ItemGroup>
-    <PackageReference Include="Microsoft.AspNetCore.OpenApi" Version="10.0.10" />
+    <PackageReference Include="Microsoft.AspNetCore.OpenApi" Version="10.0.11" />
 	  <PackageReference Include="Azure.Messaging.ServiceBus" Version="7.20.2" />
 	  <PackageReference Include="Azure.Security.KeyVault.Secrets" Version="4.11.0" />
 	  <PackageReference Include="Azure.Storage.Blobs" Version="12.29.1" />
-	  <PackageReference Include="Microsoft.Extensions.Azure" Version="1.14.0" />
+	  <PackageReference Include="Microsoft.Extensions.Azure" Version="1.14.1" />
   </ItemGroup>
 
 </Project>
diff --git a/docs/azure/sdk/snippets/logging/LoggingSampleApp.csproj b/docs/azure/sdk/snippets/logging/LoggingSampleApp.csproj
index a41dc1c4c32bb..a8f7c20a9afb0 100644
--- a/docs/azure/sdk/snippets/logging/LoggingSampleApp.csproj
+++ b/docs/azure/sdk/snippets/logging/LoggingSampleApp.csproj
@@ -7,10 +7,10 @@
   </PropertyGroup>
 
   <ItemGroup>
-    <PackageReference Include="Azure.Extensions.AspNetCore.DataProtection.Blobs" Version="1.5.3" />
-    <PackageReference Include="Azure.Extensions.AspNetCore.DataProtection.Keys" Version="1.6.3" />
+    <PackageReference Include="Azure.Extensions.AspNetCore.DataProtection.Blobs" Version="1.5.4" />
+    <PackageReference Include="Azure.Extensions.AspNetCore.DataProtection.Keys" Version="1.6.4" />
     <PackageReference Include="Azure.Identity" Version="1.21.0" />
-    <PackageReference Include="Microsoft.Extensions.Azure" Version="1.14.0" />
+    <PackageReference Include="Microsoft.Extensions.Azure" Version="1.14.1" />
   </ItemGroup>
 
 </Project>
diff --git a/docs/core/diagnostics/ambient-metadata/snippets/buildmetadata-msbuild-azure/buildmetadata-msbuild-azure.csproj b/docs/core/diagnostics/ambient-metadata/snippets/buildmetadata-msbuild-azure/buildmetadata-msbuild-azure.csproj
index cc602d1338e92..3647d7f0a3547 100644
--- a/docs/core/diagnostics/ambient-metadata/snippets/buildmetadata-msbuild-azure/buildmetadata-msbuild-azure.csproj
+++ b/docs/core/diagnostics/ambient-metadata/snippets/buildmetadata-msbuild-azure/buildmetadata-msbuild-azure.csproj
@@ -13,8 +13,8 @@
   </PropertyGroup>
 
   <ItemGroup>
-    <PackageReference Include="Microsoft.Extensions.Hosting" Version="10.0.10" />
-    <PackageReference Include="Microsoft.Extensions.AmbientMetadata.Build" Version="10.8.0" />
+    <PackageReference Include="Microsoft.Extensions.Hosting" Version="10.0.11" />
+    <PackageReference Include="Microsoft.Extensions.AmbientMetadata.Build" Version="10.9.0" />
   </ItemGroup>
 
 </Project>
diff --git a/docs/core/diagnostics/snippets/resource-monitoring/resource-monitoring.csproj b/docs/core/diagnostics/snippets/resource-monitoring/resource-monitoring.csproj
index cf6f7812068b1..1807958cb0fe7 100644
--- a/docs/core/diagnostics/snippets/resource-monitoring/resource-monitoring.csproj
+++ b/docs/core/diagnostics/snippets/resource-monitoring/resource-monitoring.csproj
@@ -8,10 +8,10 @@
   </PropertyGroup>
 
   <ItemGroup>
-    <PackageReference Include="Microsoft.Extensions.Logging.Console" Version="10.0.10" />
-    <PackageReference Include="Microsoft.Extensions.DependencyInjection" Version="10.0.10" />
-    <PackageReference Include="Microsoft.Extensions.Diagnostics.ResourceMonitoring" Version="10.8.0" />
-    <PackageReference Include="Microsoft.Extensions.Hosting" Version="10.0.10" />
+    <PackageReference Include="Microsoft.Extensions.Logging.Console" Version="10.0.11" />
+    <PackageReference Include="Microsoft.Extensions.DependencyInjection" Version="10.0.11" />
+    <PackageReference Include="Microsoft.Extensions.Diagnostics.ResourceMonitoring" Version="10.9.0" />
+    <PackageReference Include="Microsoft.Extensions.Hosting" Version="10.0.11" />
     <PackageReference Include="Spectre.Console" Version="0.57.2" />
   </ItemGroup>
 
diff --git a/docs/core/enrichment/snippets/enrichment/Enrichment.csproj b/docs/core/enrichment/snippets/enrichment/Enrichment.csproj
index c70733ef6ea9c..d8281734d4269 100644
--- a/docs/core/enrichment/snippets/enrichment/Enrichment.csproj
+++ b/docs/core/enrichment/snippets/enrichment/Enrichment.csproj
@@ -8,10 +8,10 @@
   </PropertyGroup>
 
   <ItemGroup>
-    <PackageReference Include="Microsoft.Extensions.Hosting" Version="10.0.10" />
-    <PackageReference Include="Microsoft.Extensions.Logging" Version="10.0.10" />
-    <PackageReference Include="Microsoft.Extensions.Logging.Console" Version="10.0.10" />
-    <PackageReference Include="Microsoft.Extensions.Telemetry" Version="10.8.0" />
+    <PackageReference Include="Microsoft.Extensions.Hosting" Version="10.0.11" />
+    <PackageReference Include="Microsoft.Extensions.Logging" Version="10.0.11" />
+    <PackageReference Include="Microsoft.Extensions.Logging.Console" Version="10.0.11" />
+    <PackageReference Include="Microsoft.Extensions.Telemetry" Version="10.9.0" />
   </ItemGroup>
 
 </Project>
diff --git a/docs/core/extensions/dependency-injection/snippets/basics/di-basics.csproj b/docs/core/extensions/dependency-injection/snippets/basics/di-basics.csproj
index 90a078641a92f..804c950f6220c 100644
--- a/docs/core/extensions/dependency-injection/snippets/basics/di-basics.csproj
+++ b/docs/core/extensions/dependency-injection/snippets/basics/di-basics.csproj
@@ -8,7 +8,7 @@
   </PropertyGroup>
 
   <ItemGroup>
-    <PackageReference Include="Microsoft.Extensions.DependencyInjection" Version="10.0.10" />
+    <PackageReference Include="Microsoft.Extensions.DependencyInjection" Version="10.0.11" />
   </ItemGroup>
 
 </Project>
diff --git a/docs/core/extensions/dependency-injection/snippets/console/console-di.csproj b/docs/core/extensions/dependency-injection/snippets/console/console-di.csproj
index 5e326936e111a..ee874bc639c74 100644
--- a/docs/core/extensions/dependency-injection/snippets/console/console-di.csproj
+++ b/docs/core/extensions/dependency-injection/snippets/console/console-di.csproj
@@ -9,8 +9,8 @@
   </PropertyGroup>
 
   <ItemGroup>
-    <PackageReference Include="Microsoft.Extensions.Configuration.Binder" Version="10.0.10" />
-    <PackageReference Include="Microsoft.Extensions.Hosting" Version="10.0.10" />
+    <PackageReference Include="Microsoft.Extensions.Configuration.Binder" Version="10.0.11" />
+    <PackageReference Include="Microsoft.Extensions.Hosting" Version="10.0.11" />
   </ItemGroup>
 
 </Project>
diff --git a/docs/core/extensions/snippets/async-state/csharp/AspNetCoreIntegration/AspNetCoreIntegration.csproj b/docs/core/extensions/snippets/async-state/csharp/AspNetCoreIntegration/AspNetCoreIntegration.csproj
index 9638bdf09798a..1a62c4db19894 100644
--- a/docs/core/extensions/snippets/async-state/csharp/AspNetCoreIntegration/AspNetCoreIntegration.csproj
+++ b/docs/core/extensions/snippets/async-state/csharp/AspNetCoreIntegration/AspNetCoreIntegration.csproj
@@ -6,7 +6,7 @@
   </PropertyGroup>
 
   <ItemGroup>
-    <PackageReference Include="Microsoft.Extensions.AsyncState" Version="10.8.0" />
+    <PackageReference Include="Microsoft.Extensions.AsyncState" Version="10.9.0" />
   </ItemGroup>
 
 </Project>
diff --git a/docs/core/extensions/snippets/configuration/binding-scenarios/DictionaryBinding/DictionaryBinding.csproj b/docs/core/extensions/snippets/configuration/binding-scenarios/DictionaryBinding/DictionaryBinding.csproj
index 58b4b914be8a5..6966fba4701d7 100644
--- a/docs/core/extensions/snippets/configuration/binding-scenarios/DictionaryBinding/DictionaryBinding.csproj
+++ b/docs/core/extensions/snippets/configuration/binding-scenarios/DictionaryBinding/DictionaryBinding.csproj
@@ -8,8 +8,8 @@
   </PropertyGroup>
 
   <ItemGroup>
-    <PackageReference Include="Microsoft.Extensions.Configuration" Version="10.0.10" />
-    <PackageReference Include="Microsoft.Extensions.Configuration.Binder" Version="10.0.10" />
+    <PackageReference Include="Microsoft.Extensions.Configuration" Version="10.0.11" />
+    <PackageReference Include="Microsoft.Extensions.Configuration.Binder" Version="10.0.11" />
   </ItemGroup>
 
 </Project>
diff --git a/docs/core/extensions/snippets/http/latency/latency.csproj b/docs/core/extensions/snippets/http/latency/latency.csproj
index 033ee0e7dd9bf..833f826449940 100644
--- a/docs/core/extensions/snippets/http/latency/latency.csproj
+++ b/docs/core/extensions/snippets/http/latency/latency.csproj
@@ -18,7 +18,7 @@
   </ItemGroup>
 
   <ItemGroup>
-    <PackageReference Include="Microsoft.Extensions.Http.Diagnostics" Version="10.8.0" />
+    <PackageReference Include="Microsoft.Extensions.Http.Diagnostics" Version="10.9.0" />
   </ItemGroup>
 
 </Project>
diff --git a/docs/core/extensions/sslstream-best-practices.md b/docs/core/extensions/sslstream-best-practices.md
index c05b588040c68..6e56b7ab76637 100644
--- a/docs/core/extensions/sslstream-best-practices.md
+++ b/docs/core/extensions/sslstream-best-practices.md
@@ -3,7 +3,8 @@ title: TLS/SSL best practices
 description: Learn the best practices when using SslStream in .NET.
 author: rzikm
 ms.author: radekzikmund
-ms.date: 03/13/2023
+ms.date: 08/26/2026
+ai-usage: ai-assisted
 ---
 
 # TLS/SSL best practices
@@ -25,19 +26,52 @@ Deferring the decision to the OS automatically uses the most recent version of T
 > [!NOTE]
 > <xref:System.Net.Security.CipherSuitesPolicy> is not supported on Windows and attempts to instantiate it will cause <xref:System.NotSupportedException> to be thrown.
 
-## Specify a server certificate
+## Specify a local certificate
 
-When authenticating as a server, <xref:System.Net.Security.SslStream> requires an <xref:System.Security.Cryptography.X509Certificates.X509Certificate2> instance. It is recommended to always use an <xref:System.Security.Cryptography.X509Certificates.X509Certificate2> instance which also contains the private key.
+When authenticating as a server, <xref:System.Net.Security.SslStream> always requires a certificate. When authenticating as a client, you also provide a certificate if the server requests one for mutual TLS (mTLS). In both roles, the certificate must be an <xref:System.Security.Cryptography.X509Certificates.X509Certificate2> instance that contains the private key.
 
-There are multiple ways that a server certificate can be passed to <xref:System.Net.Security.SslStream>:
+Recent .NET versions handle the server and client sides symmetrically, so the following guidance applies whether the application authenticates as a server, a client, or both.
 
-- Directly as a parameter to <xref:System.Net.Security.SslStream.AuthenticateAsServerAsync*?displayProperty=nameWithType> or via <xref:System.Net.Security.SslServerAuthenticationOptions.ServerCertificate?displayProperty=nameWithType> property
-- From a selection callback in <xref:System.Net.Security.SslServerAuthenticationOptions.ServerCertificateSelectionCallback?displayProperty=nameWithType> property
-- By passing a <xref:System.Net.Security.SslStreamCertificateContext> in the <xref:System.Net.Security.SslServerAuthenticationOptions.ServerCertificateContext?displayProperty=nameWithType> property
+You can provide the certificate to <xref:System.Net.Security.SslStream> in several ways.
 
-The recommended approach is to use the <xref:System.Net.Security.SslServerAuthenticationOptions.ServerCertificateContext?displayProperty=nameWithType> property. When the certificate is obtained by one of the other two ways, a <xref:System.Net.Security.SslStreamCertificateContext> instance is created internally by the <xref:System.Net.Security.SslStream> implementation. Creating a <xref:System.Net.Security.SslStreamCertificateContext> involves building an <xref:System.Security.Cryptography.X509Certificates.X509Chain> which is a CPU intensive operation. It is more efficient to create a <xref:System.Net.Security.SslStreamCertificateContext> once and reuse it for multiple <xref:System.Net.Security.SslStream> instances.
+When you authenticate as a server:
 
-Reusing <xref:System.Net.Security.SslStreamCertificateContext> instances also enables additional features such us [TLS session resumption](https://datatracker.ietf.org/doc/html/rfc5077) on Linux servers.
+- Set the <xref:System.Net.Security.SslServerAuthenticationOptions.ServerCertificate?displayProperty=nameWithType> property, or pass the certificate to <xref:System.Net.Security.SslStream.AuthenticateAsServerAsync*?displayProperty=nameWithType>.
+- Return the certificate from the <xref:System.Net.Security.SslServerAuthenticationOptions.ServerCertificateSelectionCallback?displayProperty=nameWithType> callback.
+- Set a <xref:System.Net.Security.SslStreamCertificateContext> on the <xref:System.Net.Security.SslServerAuthenticationOptions.ServerCertificateContext?displayProperty=nameWithType> property.
+
+When you authenticate as a client:
+
+- Add the certificate to the <xref:System.Net.Security.SslClientAuthenticationOptions.ClientCertificates?displayProperty=nameWithType> collection, or pass a collection that contains it to <xref:System.Net.Security.SslStream.AuthenticateAsClientAsync*?displayProperty=nameWithType>.
+- Return the certificate from the <xref:System.Net.Security.SslClientAuthenticationOptions.LocalCertificateSelectionCallback?displayProperty=nameWithType> callback.
+- Set a <xref:System.Net.Security.SslStreamCertificateContext> on the <xref:System.Net.Security.SslClientAuthenticationOptions.ClientCertificateContext?displayProperty=nameWithType> property.
+
+> [!NOTE]
+> The <xref:System.Net.Security.SslClientAuthenticationOptions.ClientCertificateContext> property is available starting in .NET 8.
+
+For better performance, use the certificate context property (<xref:System.Net.Security.SslServerAuthenticationOptions.ServerCertificateContext> or <xref:System.Net.Security.SslClientAuthenticationOptions.ClientCertificateContext>). When you provide the certificate in one of the other ways, <xref:System.Net.Security.SslStream> creates a <xref:System.Net.Security.SslStreamCertificateContext> internally. Creating the context builds an <xref:System.Security.Cryptography.X509Certificates.X509Chain>, which is a CPU-intensive operation, so it's more efficient to create the context once and reuse it across multiple <xref:System.Net.Security.SslStream> instances.
+
+Reusing a <xref:System.Net.Security.SslStreamCertificateContext> instance also enables extra features such as [TLS session resumption](https://datatracker.ietf.org/doc/html/rfc5077) on Linux servers.
+
+### Send intermediate certificates to the peer
+
+When an intermediate certificate authority issues the local certificate, the peer might not be able to build the full certificate chain unless the handshake includes the intermediate certificates. To send these intermediates, create a <xref:System.Net.Security.SslStreamCertificateContext> with the <xref:System.Net.Security.SslStreamCertificateContext.Create*> method and pass the intermediate certificates in the `additionalCertificates` parameter:
+
+```csharp
+X509Certificate2 leafCertificate = GetLeafCertificate();
+X509Certificate2Collection intermediates = GetIntermediateCertificates();
+
+SslStreamCertificateContext certificateContext =
+    SslStreamCertificateContext.Create(leafCertificate, intermediates);
+
+// When you authenticate as a server.
+serverOptions.ServerCertificateContext = certificateContext;
+
+// When you authenticate as a client for mutual TLS.
+clientOptions.ClientCertificateContext = certificateContext;
+```
+
+The context works the same way for both roles. On the client side, the certificate context is the recommended way to send intermediates, because the alternative—adding the intermediates to the machine or user certificate store—affects every application on the system.
 
 ## Custom `X509Certificate` validation
 
diff --git a/docs/core/extensions/sslstream-troubleshooting.md b/docs/core/extensions/sslstream-troubleshooting.md
index 7ea96387312a9..af81aeff48554 100644
--- a/docs/core/extensions/sslstream-troubleshooting.md
+++ b/docs/core/extensions/sslstream-troubleshooting.md
@@ -3,7 +3,8 @@ title: Troubleshoot SslStream authentication issues
 description: Learn how to troubleshoot and investigate issues when performing authentication with SslStream in .NET.
 author: rzikm
 ms.author: radekzikmund
-ms.date: 03/13/2023
+ms.date: 08/24/2026
+ai-usage: ai-assisted
 ---
 
 # Troubleshoot `SslStream` authentication issues
@@ -28,6 +29,22 @@ Unfortunately, for client application the only solution is to add the certificat
 
 On Windows, you may encounter the `(0x8009030E): No credentials are available in the security package` error message when attempting to use certificates with ephemeral keys. This behavior is due to a bug in the underlying OS API (Schannel). More relevant info and workarounds can be found on the associated [GitHub issue](https://github.com/dotnet/runtime/issues/23749).
 
+## Handshake message exceeds the Schannel limit
+
+On Windows, you might hit a handshake failure when a fragmented TLS handshake message exceeds the size limit that Schannel enforces. In this case, `SslStream` surfaces an <xref:System.Security.Authentication.AuthenticationException> whose inner <xref:System.ComponentModel.Win32Exception> reports error `0x80090326` (`SEC_E_ILLEGAL_MESSAGE`) and the message `The message received was unexpected or badly formatted`. You're most likely to produce large handshake messages when you use large certificate chains or when a peer sends a long list of acceptable certificate issuers during mutual TLS authentication.
+
+Because this error isn't specific to message size, confirm the cause before you change any Schannel configuration. Use a packet-capture tool to inspect the handshake messages and their sizes.
+
+If the capture confirms that a handshake message exceeds the limit, ask an administrator to create one of the following `DWORD` values under `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Messaging`:
+
+| Value | Applies to | Default |
+| --- | --- | --- |
+| `MessageLimitClient` | Messages that a TLS client accepts. | `0x8000` bytes |
+| `MessageLimitServer` | Messages that a TLS server accepts when it doesn't use client authentication. | `0x4000` bytes |
+| `MessageLimitServerClientAuth` | Messages that a TLS server accepts when it uses client authentication. | `0x8000` bytes |
+
+Set the smallest value that accepts the expected handshake message. Schannel supports values up to `0x10000` bytes. Don't change these settings unless you've confirmed the cause, because they affect the entire machine and larger limits increase memory use for each security context. For more information and registry-editing precautions, see [Messaging - fragment parsing](/windows-server/security/tls/tls-registry-settings#messaging--fragment-parsing).
+
 ## Client and server do not possess a common algorithm
 
 When inspecting the `ClientHello` and `ServerHello` messages, you may find out that there is no cipher suite offered by both client and server or even that some ciphers are not offered even if explicitly configured via <xref:System.Net.Security.CipherSuitesPolicy> (available on Linux only). The underlying TLS library may disable TLS versions and cipher suites which are considered insecure.
diff --git a/docs/core/testing/microsoft-testing-platform-ai.md b/docs/core/testing/microsoft-testing-platform-ai.md
new file mode 100644
index 0000000000000..91feccf7581b5
--- /dev/null
+++ b/docs/core/testing/microsoft-testing-platform-ai.md
@@ -0,0 +1,77 @@
+---
+title: Microsoft.Testing.Platform (MTP) AI integrations
+description: Learn how MTP extensions access AI chat clients and configure the Azure AI Foundry provider.
+author: Evangelink
+ms.author: amauryleve
+ms.date: 08/26/2026
+ai-usage: ai-assisted
+---
+
+# AI integrations
+
+The experimental [Microsoft.Testing.Platform.AI](https://www.nuget.org/packages/Microsoft.Testing.Platform.AI) package defines provider-neutral AI abstractions for test frameworks and MTP extensions. The package integrates with `Microsoft.Extensions.AI`, so an extension can request an <xref:Microsoft.Extensions.AI.IChatClient> without depending on a specific model provider.
+
+> [!IMPORTANT]
+> The AI APIs use the `TPEXP` diagnostic ID and can change in a future release. The packages supply infrastructure to extensions; they don't add AI behavior to a test suite by themselves.
+
+## Choose the packages
+
+Add the abstractions package when you author an extension that consumes a chat client. Add a provider package to the test application that hosts the extension:
+
+```dotnetcli
+dotnet add package Microsoft.Testing.Platform.AI
+dotnet add package Microsoft.Testing.Extensions.AzureFoundry
+```
+
+`Microsoft.Testing.Extensions.AzureFoundry` is the Microsoft-provided reference provider. It creates an Azure OpenAI chat client through Azure AI Foundry.
+
+## Configure Azure AI Foundry
+
+Set the following environment variables:
+
+| Variable | Required | Description |
+|---|---|---|
+| `AZURE_OPENAI_ENDPOINT` | Yes | The Azure OpenAI resource endpoint, such as `https://my-resource.openai.azure.com`. |
+| `AZURE_OPENAI_DEPLOYMENT_NAME` | Yes | The model deployment name. |
+| `AZURE_OPENAI_API_KEY` | Conditional | The resource API key. Set this value unless you register a `TokenCredential` in code. |
+
+To keep credentials out of source control, supply these values through your local environment or a protected CI secret store.
+
+## Register the provider
+
+Disable the generated MTP entry point and register the provider in your custom `Main` method. For API-key authentication, call:
+
+```csharp
+#pragma warning disable TPEXP
+builder.AddAzureOpenAIChatClientProvider();
+#pragma warning restore TPEXP
+```
+
+For Microsoft Entra ID or managed identity, reference the `Azure.Identity` package and pass a credential:
+
+```csharp
+using Azure.Identity;
+
+#pragma warning disable TPEXP
+builder.AddAzureOpenAIChatClientProvider(new DefaultAzureCredential());
+#pragma warning restore TPEXP
+```
+
+When `AZURE_OPENAI_API_KEY` is set, the provider uses the API key before the supplied credential. Credential resolution and authentication occur when the first chat request runs, so configuration errors might not appear during provider registration.
+
+## Consume a chat client
+
+Implement `IChatClientProvider` to integrate another AI provider. An MTP extension can retrieve the registered chat client from its `IServiceProvider`:
+
+```csharp
+IChatClient? client =
+    await serviceProvider.GetChatClientAsync(cancellationToken);
+```
+
+The call returns `null` when no available provider is registered. Before an extension sends test data to a model, document what data it sends and apply the privacy, security, and retention requirements for that data.
+
+## See also
+
+- [MTP features](microsoft-testing-platform-features.md)
+- [Build extensions for MTP](microsoft-testing-platform-architecture-extensions.md)
+- [Microsoft.Extensions.AI libraries](/dotnet/ai/microsoft-extensions-ai)
diff --git a/docs/core/testing/microsoft-testing-platform-architecture-capabilities.md b/docs/core/testing/microsoft-testing-platform-architecture-capabilities.md
index 0140788ba4e6b..46b245395fb44 100644
--- a/docs/core/testing/microsoft-testing-platform-architecture-capabilities.md
+++ b/docs/core/testing/microsoft-testing-platform-architecture-capabilities.md
@@ -3,7 +3,8 @@ title: Microsoft.Testing.Platform (MTP) capabilities overview
 description: Learn about MTP capabilities concept.
 author: MarcoRossignoli
 ms.author: mrossignoli
-ms.date: 07/11/2024
+ms.date: 08/26/2026
+ai-usage: ai-assisted
 ---
 
 # Microsoft.Testing.Platform (MTP) capabilities
@@ -76,7 +77,7 @@ If the testing framework implements this interface, at runtime, the following ca
 The hypothetical code fragment inside the extension could be something like:
 
 ```csharp
-IServiceProvider provider = null; // TODO: Get IServiceProvider.
+IServiceProvider serviceProvider = null; // TODO: Get IServiceProvider.
 var capabilities = serviceProvider.GetRequiredService<ITestFrameworkCapabilities>();
 
 // Utilize the `GetCapability` API to search for the specific capability to query.
@@ -104,7 +105,7 @@ The preceding example illustrates how the capability infrastructure enables a po
 
 It's evident that not all details can be communicated through an interface. Considering the previous example, what should the extension expect if the `CanProvidePerTestCpuConsumption` is supported? What kind of custom information is expected to be transmitted via the [IMessageBus](./microsoft-testing-platform-architecture-services.md#the-imessagebus-service) by the testing framework? The solution is **documentation of the capability**. It's the responsibility of the capability *owner* to design, ship, and document it as clearly as possible to assist implementors who want to effectively *collaborate* with the extension that requires the specific capability.
 
-For instance, the TRX report extension enables the testing framework to implement the necessary capability to accurately generate a TRX report. The extension to register is included in the <https://www.nuget.org/packages/Microsoft.Testing.Extensions.TrxReport> NuGet package, but the capability to implement is found in the *contract only*<https://www.nuget.org/packages/Microsoft.Testing.Extensions.TrxReport.Abstractions> NuGet package.
+For instance, the TRX report extension enables the testing framework to implement the necessary capability to accurately generate a TRX report. The extension to register is included in the <https://www.nuget.org/packages/Microsoft.Testing.Extensions.TrxReport> NuGet package, but the capability to implement is found in the [contract-only package](https://www.nuget.org/packages/Microsoft.Testing.Extensions.TrxReport.Abstractions).
 
 In conclusion, let's summarize the primary aspects of the capability system:
 
@@ -119,7 +120,7 @@ The platform exposes a specialized interface named `ITestFrameworkCapability` th
 
 ### `IBannerMessageOwnerCapability`
 
-An optional [test framework capability](#framework-capabilities) that allows the test framework to provide the banner message to the platform. If the message is `null` or if the capability is n't present, the platform will use its default banner message.
+An optional [test framework capability](#framework-capabilities) allows the test framework to provide the banner message to the platform. If the message is `null` or the capability isn't present, the platform uses its default banner message.
 
 This capability implementation allows you to abstract away the various conditions that the test framework may need to consider when deciding whether or not the banner message should be displayed.
 
diff --git a/docs/core/testing/microsoft-testing-platform-architecture-extensions.md b/docs/core/testing/microsoft-testing-platform-architecture-extensions.md
index 98ed287d3863b..c7ec6e6f3d8c3 100644
--- a/docs/core/testing/microsoft-testing-platform-architecture-extensions.md
+++ b/docs/core/testing/microsoft-testing-platform-architecture-extensions.md
@@ -3,7 +3,7 @@ title: Build extensions for Microsoft.Testing.Platform (MTP)
 description: Learn how to create in-process and out-of-process extensions for Microsoft.Testing.Platform (MTP).
 author: MarcoRossignoli
 ms.author: mrossignoli
-ms.date: 07/17/2026
+ms.date: 08/26/2026
 ai-usage: ai-assisted
 ---
 
@@ -312,6 +312,9 @@ The `IDataConsumer` inherits from [IExtension](./microsoft-testing-platform-arch
 
 `ConsumeAsync`: This method is triggered whenever data of a type to which the current consumer is subscribed is published to the [`IMessageBus`](./microsoft-testing-platform-architecture-services.md#the-imessagebus-service). It receives the `IDataProducer` to provide details about the data payload's producer, as well as the `IData` payload itself. As you can see, `IData` is a generic placeholder interface that contains general informative data. The ability to publish different types of `IData` implies that the consumer needs to *switch* on the type itself to cast it to the correct type and access the specific information.
 
+> [!IMPORTANT]
+> The message bus doesn't invoke an `IDataConsumer` for data from an `IDataProducer` whose `IExtension.Uid` matches the consumer's `IExtension.Uid`. If an extension both publishes and subscribes to message bus data, assign distinct UIDs to its producer and consumer registrations. To process data that the extension produces itself, call the processing logic directly instead of routing the data through the message bus.
+
 A sample implementation of a consumer that wants to elaborate the [`TestNodeUpdateMessage`](./microsoft-testing-platform-architecture-test-framework.md#the-testnodeupdatemessage-data) produced by a [testing framework](./microsoft-testing-platform-architecture-test-framework.md#test-framework-extension) could be:
 
 ```csharp
@@ -447,7 +450,7 @@ await messageBus.PublishAsync(
 > `TestNodeFileArtifact` is obsolete and was removed in MTP 2.0.0. To attach test-level files, use `FileArtifactProperty` on the `TestNode`. For more information, see [Migrate from Microsoft.Testing.Platform (MTP) v1 to v2](microsoft-testing-platform-migration-from-v1-to-v2.md#removed-obsolete-types).
 
 > [!NOTE]
-> MTP 2.4.0 (unreleased as of July 2026) adds an experimental `kind` constructor overload and `Kind` property to `FileArtifact` and `SessionFileArtifact` (requires the `TPEXP` diagnostic to be suppressed). `Kind` is a producer-asserted, reverse-DNS identifier of the artifact *format* (for example, `microsoft.testing.trx`, `microsoft.testing.junit`, `microsoft.testing.ctrf`, or `microsoft.testing.html`) that post-processing can use to group artifacts of the same format for consolidation. Leave it `null` or omit it when the producer doesn't declare a known kind. At this time, `Kind` is only a metadata contract; don't assume broad merge orchestration beyond that.
+> MTP 2.4.0 (unreleased as of August 2026) adds an experimental `kind` constructor overload and `Kind` property to `FileArtifact` and `SessionFileArtifact` (requires the `TPEXP` diagnostic to be suppressed). `Kind` is a producer-asserted, reverse-DNS identifier of the artifact *format* (for example, `microsoft.testing.trx`, `microsoft.testing.junit`, `microsoft.testing.ctrf`, or `microsoft.testing.html`) that post-processing uses to group artifacts of the same format. Leave it `null` or omit it when the producer doesn't declare a known kind.
 >
 > ```csharp
 > #pragma warning disable TPEXP // Experimental API.
@@ -460,6 +463,12 @@ await messageBus.PublishAsync(
 > #pragma warning restore TPEXP
 > ```
 
+### The `IArtifactPostProcessor` extensions
+
+Starting with MTP 2.4.0, the experimental `IArtifactPostProcessor` extension point processes artifacts after a `dotnet test` invocation runs multiple test modules or after a retry runs multiple attempts. The `ArtifactPostProcessingMode` value identifies whether the processor handles `TestModules` or `RetryAttempts`.
+
+The built-in TRX, JUnit, CTRF, and HTML report extensions use this extension point to consolidate related report artifacts in a `merged` directory. HTML consolidation creates a merged summary and preserves the original per-process reports. To learn how report consolidation affects test output, see [Report consolidation](microsoft-testing-platform-test-reports.md#report-consolidation).
+
 ### The `ITestHostEnvironmentVariableProvider` extensions
 
 The `ITestHostEnvironmentVariableProvider` is an *out-of-process* extension that enables you to establish custom environment variables for the test host. Utilizing this extension point ensures that the testing platform will initiate a new host with the appropriate environment variables, as detailed in the [architecture](./microsoft-testing-platform-architecture.md) section.
@@ -692,6 +701,17 @@ public static void AddSelfRegisteredExtensions(this global::Microsoft.Testing.Pl
 
 If the call is missing, double-check that the props file is packaged under `buildMultiTargeting/` (not `build/`) inside the `.nupkg`, that `DisplayName` and `TypeFullName` metadata are present, and that the consumer hasn't set `<GenerateTestingPlatformEntryPoint>false</GenerateTestingPlatformEntryPoint>`.
 
+## Load extensions dynamically
+
+Starting with MTP 2.4.0, pass `--enable-dynamic-extensions` to load extensions declared by `*.testingplatformextensions.json` manifest files next to the test application. MTP doesn't scan for arbitrary assemblies, and dynamic loading stays disabled unless each run explicitly enables it.
+
+Each manifest entry identifies an assembly and a `TestingPlatformBuilderHook` type to invoke. MTP reports every loaded extension in terminal output and fails the run if a manifest, assembly, type, or hook is invalid. Set an entry's `enabled` property to `false` to disable it without deleting the manifest.
+
+> [!WARNING]
+> Dynamically loaded extensions run with full trust inside the test process. Use manifests and assemblies only from directories and sources you trust.
+
+For the complete manifest contract, see the [extension manifest JSON schema](https://github.com/microsoft/testfx/blob/main/docs/testingplatformextensions.schema.json) and [dynamic extension loading design](https://github.com/microsoft/testfx/blob/main/docs/RFCs/023-Dynamic-Extension-Loading.md).
+
 ## Extensions execution order
 
 The testing platform consists of a [testing framework](./microsoft-testing-platform-architecture-test-framework.md#test-framework-extension) and any number of extensions that can operate [*in-process*](./microsoft-testing-platform-architecture.md#in-process-vs-out-of-process-extensions) or [*out-of-process*](./microsoft-testing-platform-architecture.md#in-process-vs-out-of-process-extensions). This document outlines the **sequence of calls** to all potential extensibility points to provide clarity on when a feature is anticipated to be invoked:
diff --git a/docs/core/testing/microsoft-testing-platform-architecture-services.md b/docs/core/testing/microsoft-testing-platform-architecture-services.md
index cd6814f0d6972..82db9a3c0d089 100644
--- a/docs/core/testing/microsoft-testing-platform-architecture-services.md
+++ b/docs/core/testing/microsoft-testing-platform-architecture-services.md
@@ -3,7 +3,8 @@ title: Microsoft.Testing.Platform services overview
 description: Learn about the available Microsoft.Testing.Platform (MTP) services.
 author: MarcoRossignoli
 ms.author: mrossignoli
-ms.date: 07/11/2024
+ms.date: 08/26/2026
+ai-usage: ai-assisted
 ---
 
 # Microsoft.Testing.Platform services
@@ -66,10 +67,11 @@ In the preceding code, both the `capabilitiesFactory` and the `adapterFactory` s
 
 The `IConfiguration` interface can be retrieved using the [`IServiceProvider`](#microsofttestingplatform-services) and provides access to the configuration settings for the testing framework and any extension points. By default, these configurations are loaded from:
 
-* Environment variables
-* A JSON file named `[assemblyName].testingplatformconfig.json` located near the entry point assembly.
+* Command-line options, exposed under the `commandLineOptions:` section.
+* Environment variables.
+* A JSON file named *[appname].testconfig.json* located next to the test application executable.
 
-**The order of precedence is maintained, which means that if a configuration is found in the environment variables, the JSON file will not be processed.**
+Command-line options take precedence over environment variables, which take precedence over values from *[appname].testconfig.json*. MTP loads every source and selects the first source that supplies each key. For `commandLineOptions:` values, MTP selects a source for the complete option so indexed arguments don't combine across sources. For details about configuration-file discovery and precedence, see [MTP configuration settings](./microsoft-testing-platform-config.md).
 
 The interface is a straightforward key-value pair of strings:
 
@@ -80,6 +82,8 @@ public interface IConfiguration
 }
 ```
 
+Starting with MTP 2.4.0, the configuration service also implements the `IConfigurationRoot` interface. Use `GetSection` to retrieve an `IConfigurationSection`, and use `GetChildren` to enumerate immediate child sections. A section exposes its `Key`, full `Path`, optional scalar `Value`, and `HasValue` state. Providers must implement `IHierarchicalConfigurationProvider` before their keys appear through enumeration, but you can retrieve a known path from any provider.
+
 ### JSON configuration file
 
 The JSON file follows a hierarchical structure. To access child properties, you need to use the `:` separator. For example, consider a configuration for a potential testing framework like:
@@ -172,6 +176,12 @@ The `ICommandLineOptions` can be obtained through certain APIs, such as the [ICo
 
 `ICommandLineOptions.TryGetOptionArgumentList(string optionName, out string[]? arguments)`: This method enables you to check whether a specific option has been set and, if so, retrieve the corresponding value or values (if the arity is more than one). Similar to the previous case, the `optionName` should be provided without the `--` prefix.
 
+## The `IArtifactNamingService` service
+
+Starting with MTP 2.4.0, `IArtifactNamingService` gives extensions the same cross-platform file-name templating that MTP report extensions use. Retrieve it with `serviceProvider.GetArtifactNamingService()`, then call `ResolveFileName` with a template.
+
+The service expands `{pname}`, `{pid}`, `{asm}`, `{tfm}`, `{arch}`, and `{time}`. It preserves directory segments and sanitizes the leaf file name for the current operating system. Unknown placeholders remain unchanged. For placeholder descriptions, see [Report file names](microsoft-testing-platform-test-reports.md#report-file-names).
+
 ## The `ILoggerFactory` service
 
 The testing platform comes with an integrated logging system that generates a log file. You can view the logging options by running the `--help` command.
@@ -347,8 +357,9 @@ The API consists of:
 public interface IOutputDevice
 {
     Task DisplayAsync(
-        IOutputDeviceDataProducer producer, 
-        IOutputDeviceData data);
+        IOutputDeviceDataProducer producer,
+        IOutputDeviceData data,
+        CancellationToken cancellationToken);
 }
 
 public interface IOutputDeviceDataProducer : IExtension
@@ -394,18 +405,19 @@ IServiceProvider provider = null; // Get the service provider...
 var outputDevice = provider.GetOutputDevice();
 
 await outputDevice.DisplayAsync(
-    this, 
+    this,
     new FormattedTextOutputDeviceData($"TestingFramework version '{Version}' running tests with parallelism of {_dopValue}")
     {
         ForegroundColor = new SystemConsoleColor
         {
             ConsoleColor = ConsoleColor.Green
         }
-    });
+    },
+    CancellationToken.None);
 ```
 
 Beyond the standard use of colored text, the main advantage of `IOutputDevice` and `IOutputDeviceData` is that the *output device* is entirely independent and unknown to the user. This allows for the development of complex user interfaces. For example, it's entirely feasible to implement a *real-time* web application that displays the progress of tests.
 
 ## The `IPlatformInformation` service
 
-Provides information about the platform such as: name, version, commit hash and build date.
+The experimental `IPlatformInformation` service provides the platform `Name`, optional `Version`, optional `CommitHash`, and optional `BuildDate`.
diff --git a/docs/core/testing/microsoft-testing-platform-cli-options.md b/docs/core/testing/microsoft-testing-platform-cli-options.md
index 6d01498c010e6..f10dbcdf8a015 100644
--- a/docs/core/testing/microsoft-testing-platform-cli-options.md
+++ b/docs/core/testing/microsoft-testing-platform-cli-options.md
@@ -3,7 +3,7 @@ title: Microsoft.Testing.Platform (MTP) CLI options reference
 description: Find platform and extension command-line options for MTP in one place.
 author: Evangelink
 ms.author: amauryleve
-ms.date: 07/09/2026
+ms.date: 08/26/2026
 ai-usage: ai-assisted
 ---
 
@@ -86,6 +86,13 @@ This article gives a central entry point for MTP command-line options.
 
   Defines the verbosity level when the `--diagnostic` switch is used. The available values are `Trace`, `Debug`, `Information`, `Warning`, `Error`, or `Critical`.
 
+- **`--enable-dynamic-extensions`**
+
+  Enables loading extensions declared by `*.testingplatformextensions.json` manifest files next to the test application. Dynamic extensions are disabled by default. For security requirements and the manifest schema, see [Load extensions dynamically](./microsoft-testing-platform-architecture-extensions.md#load-extensions-dynamically).
+
+  > [!NOTE]
+  > This option is available in MTP starting with version 2.4.0.
+
 - **`--exit-on-process-exit`**
 
   Exit the test process if dependent process exits. PID must be provided.
@@ -142,6 +149,20 @@ This article gives a central entry point for MTP command-line options.
 
   The directory where the test results are going to be placed. If the specified directory doesn't exist, it's created. The default is `TestResults` in the directory that contains the test application.
 
+- **`--server`**
+
+  Starts the test application in JSON-RPC server mode for editor, IDE, or tool integration. Omit the value or use `jsonrpc`. For a supported source-only client, see [MTP server mode](./microsoft-testing-platform-server-mode.md).
+
+  > [!IMPORTANT]
+  > The `dotnettestcli` value and its transport arguments are internal to the .NET SDK integration. Don't pass them manually.
+
+- **`--show-slowest-tests`**
+
+  Shows the requested number of slowest tests in the terminal summary. When a run contains multiple test modules, MTP reports the slowest tests for each module.
+
+  > [!NOTE]
+  > This option is available in MTP starting with version 2.4.0.
+
 - **`--timeout`**
 
   A global test execution timeout. Takes one argument as string in the format `<value>[h|m|s]` where `<value>` is float.
diff --git a/docs/core/testing/microsoft-testing-platform-config.md b/docs/core/testing/microsoft-testing-platform-config.md
index a83e147ffb9cb..e0248bef36aa9 100644
--- a/docs/core/testing/microsoft-testing-platform-config.md
+++ b/docs/core/testing/microsoft-testing-platform-config.md
@@ -3,7 +3,7 @@ title: Microsoft.Testing.Platform (MTP) config options
 description: Learn how to configure MTP using testconfig.json configuration settings and environment variables.
 author: Evangelink
 ms.author: amauryleve
-ms.date: 06/16/2026
+ms.date: 08/26/2026
 ai-usage: ai-assisted
 ---
 
@@ -215,6 +215,12 @@ When set to any non-empty value, suppresses all ANSI color output. MTP honors th
 
 When set to `1` or `true`, suppresses the startup banner, the copyright message, and the telemetry banner. This is the standard .NET CLI environment variable and is honored by MTP. See also `TESTINGPLATFORM_NOBANNER`.
 
+### `TESTINGPLATFORM_PIPE_DIRECTORY` environment variable
+
+Starting with MTP 2.4.0, this variable overrides the directory where MTP creates Unix domain-socket files for named-pipe communication. Use it when a sandbox or container doesn't allow socket creation in the default temporary directory. MTP creates and checks the directory, and fails with an error when the directory isn't writable or the resulting socket path is too long.
+
+The variable has no effect on Windows, where named pipes don't use file-system paths. It also doesn't relocate a pipe that another process, such as the .NET SDK, creates.
+
 ### `TESTINGPLATFORM_WAIT_ATTACH_DEBUGGER` environment variable
 
 When set to `1`, the test process pauses at startup and waits for a debugger to attach before proceeding. Equivalent to the `--debug` command-line option. Not supported on browser platforms.
diff --git a/docs/core/testing/microsoft-testing-platform-features.md b/docs/core/testing/microsoft-testing-platform-features.md
index 8aeab51c02d70..0dd297e6ef6c8 100644
--- a/docs/core/testing/microsoft-testing-platform-features.md
+++ b/docs/core/testing/microsoft-testing-platform-features.md
@@ -3,7 +3,7 @@ title: Microsoft.Testing.Platform features
 description: Learn about the various Microsoft.Testing.Platform features, both built-in and available as extensions.
 author: nohwnd
 ms.author: jajares
-ms.date: 07/03/2026
+ms.date: 08/26/2026
 ai-usage: ai-assisted
 ---
 
@@ -31,16 +31,19 @@ Use the following path based on your goal:
 
 - Need to customize terminal output: [Terminal output](./microsoft-testing-platform-terminal-output.md) (built-in)
 - Need TRX or Azure DevOps reports: [Test reports](./microsoft-testing-platform-test-reports.md) (extension)
-- Need GitHub Actions-native output (log groups, annotations, and job summary): [GitHub Actions report](./microsoft-testing-platform-test-reports.md#github-actions-reports) (extension, experimental)
+- Need GitHub Actions-native output (log groups, annotations, and job summary): [GitHub Actions report](./microsoft-testing-platform-test-reports.md#github-actions-reports) (extension)
 - Need coverage data: [Code coverage](./microsoft-testing-platform-code-coverage.md) (extension)
 - Need crash or hang diagnostics: [Crash and hang dumps](./microsoft-testing-platform-crash-hang-dumps.md) (extension)
 - Need to record the screen during a run: [Diagnostics](./microsoft-testing-platform-diagnostics.md) (extension, experimental)
 - Need to deploy and launch a packaged-app test host: [Test host deployment](./microsoft-testing-platform-test-host-deployment.md) (extension, experimental)
 - Need to route platform logs through `Microsoft.Extensions.Logging`: [Microsoft.Extensions integration](./microsoft-testing-platform-extensions-integration.md) (extension, experimental)
+- Need to build editor or IDE integration: [Server mode](./microsoft-testing-platform-server-mode.md) (built-in)
+- Need to load extensions that aren't compile-time references: [Dynamic extension loading](./microsoft-testing-platform-architecture-extensions.md#load-extensions-dynamically) (built-in, opt-in)
 - Need to retry failed tests: [Retry](./microsoft-testing-platform-retry.md#retry) (extension)
 - Need hot reload support: [Hot Reload](./microsoft-testing-platform-hot-reload.md) (extension)
 - Need Microsoft Fakes support: [Microsoft Fakes](./microsoft-testing-platform-fakes.md) (extension)
 - Need OpenTelemetry traces and metrics: [OpenTelemetry](./microsoft-testing-platform-open-telemetry.md) (extension)
+- Need to supply AI chat clients to a test framework or extension: [AI integrations](./microsoft-testing-platform-ai.md) (extension, experimental)
 - Telemetry data collection and opt-out: [Telemetry](./microsoft-testing-platform-telemetry.md) (extension)
 
 ## Built-in features
@@ -51,6 +54,14 @@ These features are part of the core platform and don't require additional NuGet
 
 Status and progress reporting to the terminal: output modes, ANSI support, and progress indicators.
 
+**[Server mode](./microsoft-testing-platform-server-mode.md)**
+
+Drive test discovery and execution from an editor, IDE, or other tool through JSON-RPC.
+
+**[Dynamic extension loading](./microsoft-testing-platform-architecture-extensions.md#load-extensions-dynamically)**
+
+Load explicitly declared extension assemblies from JSON manifests when a run opts in.
+
 ## Extension features
 
 These features require installing NuGet packages.
@@ -71,6 +82,10 @@ Collect process dump files when the test host crashes or hangs.
 
 Emit traces and metrics through OpenTelemetry during test runs.
 
+**[AI integrations](./microsoft-testing-platform-ai.md)** (experimental)
+
+Supply provider-neutral AI chat clients to test frameworks and extensions, including through Azure AI Foundry.
+
 **[Retry](./microsoft-testing-platform-retry.md)**
 
 Retry failed tests with configurable policies.
diff --git a/docs/core/testing/microsoft-testing-platform-intro.md b/docs/core/testing/microsoft-testing-platform-intro.md
index 8f723de2fd7b2..38e4508c74742 100644
--- a/docs/core/testing/microsoft-testing-platform-intro.md
+++ b/docs/core/testing/microsoft-testing-platform-intro.md
@@ -3,7 +3,7 @@ title: Microsoft.Testing.Platform overview - .NET test runner
 description: Learn about Microsoft.Testing.Platform (MTP), a lightweight and portable .NET test runner and VSTest alternative for running unit tests in CI pipelines, CLI, and IDEs.
 author: Evangelink
 ms.author: amauryleve
-ms.date: 08/06/2026
+ms.date: 08/26/2026
 ai-usage: ai-assisted
 ---
 
@@ -30,6 +30,7 @@ Use the following path, based on what you need next:
 - Migrate an existing VSTest setup: [Migrate from VSTest to MTP](./migrating-vstest-microsoft-testing-platform.md)
 - Add diagnostics, coverage, and reporting: [MTP features](./microsoft-testing-platform-features.md)
 - Build your own extension: [MTP architecture](./microsoft-testing-platform-architecture.md), [Extension points](./microsoft-testing-platform-architecture-extensions.md), and [Services](./microsoft-testing-platform-architecture-services.md)
+- Build editor or IDE integration: [MTP server mode](./microsoft-testing-platform-server-mode.md)
 
 ## MTP pillars
 
diff --git a/docs/core/testing/microsoft-testing-platform-open-telemetry.md b/docs/core/testing/microsoft-testing-platform-open-telemetry.md
index 97781093d81a9..266a26e130910 100644
--- a/docs/core/testing/microsoft-testing-platform-open-telemetry.md
+++ b/docs/core/testing/microsoft-testing-platform-open-telemetry.md
@@ -3,7 +3,7 @@ title: Microsoft.Testing.Platform (MTP) OpenTelemetry
 description: Learn how to use the OpenTelemetry extension to emit traces and metrics from MTP.
 author: Evangelink
 ms.author: amauryleve
-ms.date: 06/16/2026
+ms.date: 08/26/2026
 ai-usage: ai-assisted
 ---
 
@@ -17,7 +17,7 @@ This extension integrates [OpenTelemetry](https://opentelemetry.io/) with Micros
 > This extension is available in MTP starting with version 2.1.0.
 
 > [!IMPORTANT]
-> This extension is currently experimental. All public APIs are gated behind the `TPEXP` diagnostic ID.
+> Starting with MTP 2.4.0, the OpenTelemetry extension follows the MTP release version and its public entry points are no longer experimental.
 
 ## Registration
 
@@ -40,6 +40,14 @@ using var app = await builder.BuildAsync();
 return await app.RunAsync();
 ```
 
+To configure instrumentation, resource attributes, and an OTLP exporter from standard `OTEL_*` environment variables, call:
+
+```csharp
+builder.AddOpenTelemetryProviderFromEnvironment();
+```
+
+The method adds instrumentation only when you configure an exporter or pass a configuration callback, so you can leave the registration in the application when some environments don't export telemetry.
+
 ## API
 
 ### `AddOpenTelemetryProvider`
@@ -53,9 +61,48 @@ Registers the OpenTelemetry provider on `ITestApplicationBuilder`. Accepts two o
 
 Call on `TracerProviderBuilder` or `MeterProviderBuilder` to subscribe to the built-in `Microsoft.Testing.Platform` activity source and meter.
 
+### `AddTestingPlatformResource`
+
+Call on `ResourceBuilder` to add test assembly, host, operating system, and runtime attributes. The detector also identifies CI provider, pipeline, branch, and commit information for GitHub Actions, Azure Pipelines, GitLab CI, and Jenkins.
+
+### `AddOpenTelemetryProviderFromEnvironment`
+
+Registers tracing, metrics, resource detection, and an OTLP exporter from standard OpenTelemetry environment variables. `OTEL_SDK_DISABLED=true` disables the integration. Configure `OTEL_TRACES_EXPORTER`, `OTEL_METRICS_EXPORTER`, or `OTEL_EXPORTER_OTLP_ENDPOINT` to activate export.
+
 ## Activity source and meter
 
 The extension emits telemetry under:
 
 - Activity source: `Microsoft.Testing.Platform`
 - Meter: `Microsoft.Testing.Platform`
+
+## Semantic conventions
+
+MTP emits standard OpenTelemetry testing and code attributes where a convention exists, including `test.case.name`, `test.case.result.status`, `test.suite.name`, `code.function.name`, `code.file.path`, `code.line.number`, `code.stacktrace`, and `error.type`. Failed tests set the span status to `Error` and add an `exception` event.
+
+MTP extends the conventions with additional result states (`skipped`, `error`, `timeout`, `cancelled`, and `unknown`) and test attributes for concepts that OpenTelemetry doesn't define. To preserve existing dashboards, legacy attribute and instrument names remain enabled by default.
+
+When the launching process supplies `TRACEPARENT` and `TRACESTATE`, MTP places the test run under that trace instead of starting an unrelated root trace.
+
+## Emitted metrics
+
+| Instrument | Type | Unit | Description |
+|---|---|---|---|
+| `test.case.duration` | Histogram | `s` | Test duration, grouped by result status and suite. |
+| `test.case.result.count` | Counter | `{test}` | Completed tests, grouped by result status and suite. |
+| `test.case.active` | UpDownCounter | `{test}` | Tests that are currently running. |
+| `test.run.duration` | Histogram | `s` | Run duration, grouped by result status and exit code. |
+| `test.case.retry.count` | Counter | `{test}` | Tests scheduled for another attempt by the retry extension. |
+
+## Environment configuration
+
+| Environment variable | Default | Description |
+|---|---|---|
+| `TRACEPARENT`, `TRACESTATE` | Unset | W3C trace context for the parent run. |
+| `TESTINGPLATFORM_OTEL_CAPTURE_TEST_OUTPUT` | `1` | Attaches captured standard output and error to test spans. Set to `0` when output might contain secrets. |
+| `TESTINGPLATFORM_OTEL_ATTRIBUTE_VALUE_LENGTH_LIMIT` | `8192` | Sets the maximum characters retained for a string attribute. |
+| `TESTINGPLATFORM_OTEL_EMIT_LEGACY_ATTRIBUTES` | `1` | Emits legacy attribute and instrument names alongside semantic-convention names. |
+| `OTEL_SDK_DISABLED` | Unset | Set to `true` to disable the OpenTelemetry SDK. |
+| `OTEL_SERVICE_NAME` | Unset | Overrides the service name. |
+| `OTEL_EXPORTER_OTLP_ENDPOINT` | Unset | Sets the OTLP endpoint. |
+| `OTEL_TRACES_EXPORTER`, `OTEL_METRICS_EXPORTER` | Unset | Selects trace and metric exporters. |
diff --git a/docs/core/testing/microsoft-testing-platform-server-mode.md b/docs/core/testing/microsoft-testing-platform-server-mode.md
new file mode 100644
index 0000000000000..a6c7bb88680da
--- /dev/null
+++ b/docs/core/testing/microsoft-testing-platform-server-mode.md
@@ -0,0 +1,50 @@
+---
+title: Microsoft.Testing.Platform (MTP) server mode
+description: Learn how tools and IDEs drive MTP test applications through JSON-RPC server mode.
+author: Evangelink
+ms.author: amauryleve
+ms.date: 08/26/2026
+ai-usage: ai-assisted
+---
+
+# Server mode
+
+MTP server mode lets an editor, IDE, or other test tool launch a test application and drive discovery and execution through JSON-RPC. Use server mode when you build tooling around MTP. For normal command-line and CI runs, run the test application directly or use `dotnet test`.
+
+Start the public JSON-RPC server with `--server` or `--server jsonrpc`.
+
+> [!IMPORTANT]
+> The .NET SDK uses a separate internal binary protocol through `--server dotnettestcli`. Don't pass that value yourself. `dotnet test` configures the transport and protocol arguments.
+
+## Use the source-only client
+
+Starting with MTP 2.4.0, the [Microsoft.Testing.Platform.ServerMode.Client.Sources](https://www.nuget.org/packages/Microsoft.Testing.Platform.ServerMode.Client.Sources) package supplies a canonical client for the JSON-RPC protocol. The package injects C# source into your project instead of adding a runtime assembly.
+
+The source-only design provides:
+
+- No runtime DLL or additional deployment dependency.
+- Native AOT-compatible, reflection-free serialization.
+- Protocol types and serialization code from the same repository as the MTP server.
+
+The injected `MtpServerClient` and `IMtpServerClient` types can initialize a connection, discover tests, run tests, request server exit, and report test-node updates. The types remain `internal` to your assembly.
+
+## Meet client requirements
+
+Use C# 12 or later. The package sets `LangVersion` to `12.0` when your project doesn't specify a language version. It also supplies internal compatibility types for .NET Framework 4.6.2 and `netstandard2.0`.
+
+Remove any hand-written copy of the MTP client before you add the package to avoid duplicate internal types.
+
+## Choose connection behavior
+
+Set `MtpServerClientOptions.IsStateful` to tell the server whether the client preserves state across requests:
+
+- Leave the value `false` for a single discovery or execution request followed by exit.
+- Set the value to `true` for an editor or IDE session that sends multiple requests over the same connection.
+
+The client sends this setting through the experimental `capabilities.testing.isStateful` protocol capability.
+
+## See also
+
+- [Run and debug tests with MTP](microsoft-testing-platform-run-and-debug.md)
+- [Build a test framework for MTP](microsoft-testing-platform-architecture-test-framework.md)
+- [MTP JSON-RPC protocol](https://github.com/microsoft/testfx/blob/main/docs/mstest-runner-protocol/001-protocol-intro.md)
diff --git a/docs/core/testing/microsoft-testing-platform-telemetry.md b/docs/core/testing/microsoft-testing-platform-telemetry.md
index e4ea91187bc0a..056d67161bec1 100644
--- a/docs/core/testing/microsoft-testing-platform-telemetry.md
+++ b/docs/core/testing/microsoft-testing-platform-telemetry.md
@@ -3,7 +3,7 @@ title: Microsoft.Testing.Platform (MTP) telemetry
 description: Learn about the telemetry data collected by MTP and how to disable it.
 author: nohwnd
 ms.author: jajares
-ms.date: 02/25/2026
+ms.date: 08/26/2026
 ai-usage: ai-assisted
 ---
 
@@ -74,7 +74,7 @@ The telemetry feature collects the following data points:
 | All | If Hot reload is enabled. |
 | All | If the application crashed. |
 | All | If the application is running as NativeAOT. |
-| All | If the repository is our own repository. Based on the `telemetry:isDevelopmentRepository` setting in _testingplatformconfig.json_. |
+| All | Whether the repository is the MTP development repository, based on the `platformOptions:telemetry:isDevelopmentRepository` setting in *[appname].testconfig.json*. |
 | All | Name of the test framework you're using, as a hashed value. |
 | All | Name of your executable (which is usually the same as the name of the project), as a hashed value. |
 | All | Operating system, version and architecture. |
diff --git a/docs/core/testing/microsoft-testing-platform-terminal-output.md b/docs/core/testing/microsoft-testing-platform-terminal-output.md
index 8171110826548..c47670f8cbe17 100644
--- a/docs/core/testing/microsoft-testing-platform-terminal-output.md
+++ b/docs/core/testing/microsoft-testing-platform-terminal-output.md
@@ -3,7 +3,7 @@ title: Microsoft.Testing.Platform (MTP) terminal output
 description: Learn about the built-in terminal test reporter in MTP, including output modes, ANSI support, and progress indicators.
 author: evangelink
 ms.author: amauryleve
-ms.date: 08/06/2026
+ms.date: 08/26/2026
 ai-usage: ai-assisted
 ---
 
@@ -61,6 +61,7 @@ If your code must write directly to the console and you need that output to rema
 | `--show-stdout` | 2.2.1 | Determines when to show captured standard output of a test. Valid values are `All`, `Failed`, and `None`. Default is `All`. |
 | `--show-stderr` | 2.2.1 | Determines when to show captured error output of a test. Valid values are `All`, `Failed`, and `None`. Default is `All`. |
 | `--show-flaky-tests` | 2.4.0 | Controls the `flaky:` summary and the **Flaky tests** list for tests that pass after a retry. Use `on` or `off`; the default is `on`. Applies to MSTest `[Retry]` and the [retry extension](microsoft-testing-platform-retry.md). |
+| `--show-slowest-tests` | 2.4.0 | Shows the requested number of slowest tests in the summary. For a multi-module run, MTP reports the slowest tests for each module. |
 
 > [!NOTE]
 > A dash (—) in the **MTP version** column marks core options that aren't tied to a specific version because they've been available since the platform's initial releases.
diff --git a/docs/core/testing/microsoft-testing-platform-test-reports.md b/docs/core/testing/microsoft-testing-platform-test-reports.md
index eb3a9ff1345ce..3c5aa9b8f4a5d 100644
--- a/docs/core/testing/microsoft-testing-platform-test-reports.md
+++ b/docs/core/testing/microsoft-testing-platform-test-reports.md
@@ -3,7 +3,7 @@ title: Microsoft.Testing.Platform (MTP) test reports
 description: Learn about the MTP extensions that create test report files (TRX, HTML, JUnit, CTRF, Azure DevOps, GitHub Actions).
 author: evangelink
 ms.author: amauryleve
-ms.date: 08/06/2026
+ms.date: 08/26/2026
 ai-usage: ai-assisted
 ---
 
@@ -34,6 +34,14 @@ For example, `--report-trx-filename "{asm}_{tfm}_{arch}.trx"` reproduces the def
 > [!NOTE]
 > Placeholder names are case-sensitive and use lowercase. Placeholder support for report file names is available in MTP starting with version 2.3.0.
 
+## Report consolidation
+
+Starting with MTP 2.4.0, MTP automatically post-processes report artifacts after a `dotnet test` invocation runs multiple test modules or after retry support runs multiple attempts. The feature is experimental in MTP 2.4.0.
+
+The TRX, JUnit, CTRF, and HTML extensions group compatible artifacts by report kind and write a consolidated report under the test results directory's `merged` subdirectory. CTRF consolidation combines module results and collapses retry attempts into the final test result with retry history. HTML consolidation creates a merged summary and preserves the original per-process reports.
+
+For custom report extensions, the experimental `IArtifactPostProcessor` API exposes separate `TestModules` and `RetryAttempts` processing modes. For more information, see [The `IArtifactPostProcessor` extensions](microsoft-testing-platform-architecture-extensions.md#the-iartifactpostprocessor-extensions).
+
 ## Visual Studio test reports (TRX)
 
 The Visual Studio test result file (or TRX) is the default format for publishing test results. This extension requires the [Microsoft.Testing.Extensions.TrxReport](https://nuget.org/packages/Microsoft.Testing.Extensions.TrxReport) NuGet package.
@@ -151,6 +159,8 @@ builder.TestHost.AddAzureDevOpsProvider();
 |---|---|---|
 | `--report-azdo` | 1.9.0 | Enables the Azure DevOps report generator. Errors and warnings are written to the output in a format that Azure DevOps understands. |
 | `--report-azdo-severity` | 1.9.0 | Severity to use for reported events. Valid values are `error` (default) and `warning`. |
+| `--report-azdo-groups` | 2.4.0 | Enables or disables per-assembly log groups. When enabled, each test assembly's output appears in a collapsible section of the Azure Pipelines log. Valid values are `on` and `off`. MTP 2.4.0 preview builds default to `on`; the stable MTP 2.4.0 release defaults to `off`. Requires `--report-azdo`. |
+| `--report-azdo-annotations` | 2.4.0 | Enables or disables annotations for failed and skipped tests. Valid values are `on` (default) and `off`. Requires `--report-azdo`. |
 | `--report-azdo-flaky-history` | 2.3.0 | Queries Azure DevOps test result history for the past N days (1-90) and annotates reported failures with flakiness context. Requires `--report-azdo`. |
 | `--report-azdo-demote-known-flaky` | 2.3.0 | Demotes failures that are flaky enough in the Azure DevOps history window (default threshold is 25%) from errors to warnings. Requires `--report-azdo` and `--report-azdo-flaky-history`. |
 | `--report-azdo-quarantine-file` | 2.3.0 | Path to a text file that lists quarantined test fully qualified names or glob patterns. Matching failures are reported as warnings. Requires `--report-azdo`. |
@@ -163,19 +173,29 @@ builder.TestHost.AddAzureDevOpsProvider();
 | `--publish-azdo-test-results` | 2.3.0 | Publishes test results live to the Azure DevOps **Tests** tab. |
 | `--publish-azdo-run-name` | 2.3.0 | Sets a custom Azure DevOps test run name for live test-result publishing. Requires `--publish-azdo-test-results`. |
 
+> [!WARNING]
+> Don't enable groups when multiple test assemblies run in parallel. Azure DevOps `##[group]` and `##[endgroup]` formatting commands are sequential and anonymous. Concurrent assembly output can interleave, cause incorrect group nesting, and put lines under the wrong assembly. If you use an MTP 2.4.0 preview build, pass `--report-azdo-groups off` to disable groups. The stable MTP 2.4.0 release disables groups by default. Pass `--report-azdo-groups on` only for a single assembly or serialized assembly execution.
+
 > [!NOTE]
-> The **MTP version** column lists the MTP release in which each option first became available in a stable build. The Azure DevOps extension itself became stable in MTP 1.9.0 with `--report-azdo` and `--report-azdo-severity`; the remaining options were added in MTP 2.3.0.
+> The **MTP version** column lists the first MTP version that contains each option. The Azure DevOps extension itself became stable in MTP 1.9.0 with `--report-azdo` and `--report-azdo-severity`; the remaining options were added in MTP 2.3.0 or 2.4.0.
 
 The extension automatically detects that it is running in continuous integration (CI) environment by checking the `TF_BUILD` environment variable.
 
+Starting with MTP 2.4.0, Azure DevOps Markdown summaries aggregate results across every test module in a `dotnet test` invocation. When you also enable code coverage, the summary includes covered and total counts, percentages, threshold results, and an indicator when coverage data is partial.
+
 ## GitHub Actions reports
 
 The GitHub Actions report emits GitHub Actions-native workflow commands so test runs produce a first-class experience on the runner: per-assembly log groups, failed and skipped test annotations (surfaced in the workflow **Annotations** tab and, when the source location resolves, on the pull request's **Files changed** diff), a Markdown job summary appended to the file referenced by `GITHUB_STEP_SUMMARY`, and slow-test notices.
 
+This extension requires the [Microsoft.Testing.Extensions.GitHubActionsReport](https://www.nuget.org/packages/Microsoft.Testing.Extensions.GitHubActionsReport) NuGet package.
+
 The extension activates only when the run is on GitHub Actions (the `GITHUB_ACTIONS` environment variable is `true`) and the `--report-gh` switch is set; otherwise it does nothing. When active, each feature is enabled by default and can be turned off individually with its `--report-gh-*` option.
 
+> [!IMPORTANT]
+> The `--report-gh` option belongs to `Microsoft.Testing.Extensions.GitHubActionsReport`. The [GitHubActionsTestLogger](https://www.nuget.org/packages/GitHubActionsTestLogger) package provides a different option, `--report-github`. The options aren't aliases and work only when the test project registers the package that owns the option.
+
 > [!NOTE]
-> Available in MTP starting with version 2.3.0. This extension is experimental, and its options and output format might change in a future version.
+> The extension is available starting with MTP 2.3.0. Starting with MTP 2.4.0, its public entry points are no longer experimental.
 
 ### Manual registration
 
@@ -191,6 +211,9 @@ builder.AddGitHubActionsProvider();
 | `--report-gh` | 2.3.0 | Enables the GitHub Actions report generator so test runs emit workflow commands. Requires the run to be on GitHub Actions. |
 | `--report-gh-groups` | 2.3.0 | Enables or disables per-assembly log groups. Valid values are `on` (default) and `off`. Requires `--report-gh`. |
 | `--report-gh-annotations` | 2.3.0 | Enables or disables annotations for failed and skipped tests. Valid values are `on` (default) and `off`. Requires `--report-gh`. |
-| `--report-gh-step-summary` | 2.3.0 | Enables or disables writing a Markdown job summary to the file referenced by `GITHUB_STEP_SUMMARY`. Valid values are `on` (default) and `off`. Requires `--report-gh`. |
+| `--report-gh-step-summary` | 2.3.0 | Controls whether the extension writes a Markdown job summary to the file referenced by `GITHUB_STEP_SUMMARY`. Valid values are `on` (default), `off`, and, starting with MTP 2.4.0, `on-failure`. Requires `--report-gh`. |
+| `--report-gh-step-summary-sections` | 2.4.0 | Selects summary content. Valid values are `test-results`, `slow-tests`, `coverage`, and `all` (default). Requires `--report-gh` and a summary mode other than `off`. |
 | `--report-gh-slow-test-notices` | 2.3.0 | Enables or disables slow-test notices. Valid values are `on` (default) and `off`. Requires `--report-gh`. |
 | `--report-gh-slow-test-threshold` | 2.3.0 | The duration a test can run before a slow-test notice is emitted. Accepts a bare number of seconds or a value with a unit suffix such as `90s`, `2m`, or `1.5h`. The default is `60s`. Requires `--report-gh`. |
+
+Starting with MTP 2.4.0, GitHub Actions Markdown summaries aggregate results across every test module in a `dotnet test` invocation. When you also enable code coverage, select `coverage` or `all` to include covered and total counts, percentages, threshold results, and an indicator when coverage data is partial.
diff --git a/docs/core/testing/migrating-vstest-microsoft-testing-platform.md b/docs/core/testing/migrating-vstest-microsoft-testing-platform.md
index 6ec31331068e1..11ec53c1026c5 100644
--- a/docs/core/testing/migrating-vstest-microsoft-testing-platform.md
+++ b/docs/core/testing/migrating-vstest-microsoft-testing-platform.md
@@ -3,7 +3,8 @@ title: Migration guide from VSTest to Microsoft.Testing.Platform (MTP)
 description: Step-by-step guide to migrate from VSTest to Microsoft.Testing.Platform (MTP), including argument mapping, project configuration, and CI pipeline updates.
 author: Youssef1313
 ms.author: ygerges
-ms.date: 09/15/2025
+ms.date: 08/26/2026
+ai-usage: ai-assisted
 ---
 
 # Migrate from VSTest to Microsoft.Testing.Platform (MTP)
@@ -89,6 +90,54 @@ The build-related arguments are irrelevant to the test platform and as such don'
 - `-r|--runtime <RUNTIME_IDENTIFIER>`
 - `-v|--verbosity <LEVEL>`
 
+Although `--arch` remains a build-related option, it replaces the architecture that VSTest selects through `RunConfiguration.TargetPlatform`. Pass `--arch` to `dotnet test` itself, before any `--` separator.
+
+For example, migrate this VSTest project command:
+
+```dotnetcli
+dotnet test MyTests.csproj -c Debug -- RunConfiguration.TargetPlatform=x86 /Parallel
+```
+
+For .NET 10 SDK and later versions, use this MTP command:
+
+```dotnetcli
+dotnet test --project MyTests.csproj -c Debug --arch x86
+```
+
+Replace `x86` with `x64` to target x64. MTP runs test modules in parallel by default, so `/Parallel` doesn't need a replacement. To limit module-level parallelism, use `--max-parallel-test-modules <NUMBER>`.
+
+> [!IMPORTANT]
+> You can't combine `--solution` with `--arch`, `--os`, or `--runtime`. These options set `RuntimeIdentifier` as a global MSBuild property, and solution builds don't support a global `RuntimeIdentifier`. To test a solution across architectures, invoke each test project separately or set `RuntimeIdentifier` in the individual test projects.
+
+For example, replace these four solution-level VSTest commands:
+
+```dotnetcli
+dotnet test MySolution.sln -c Debug -- RunConfiguration.TargetPlatform=x86 /Parallel
+dotnet test MySolution.sln -c Release -- RunConfiguration.TargetPlatform=x86 /Parallel
+dotnet test MySolution.sln -c Debug -- RunConfiguration.TargetPlatform=x64 /Parallel
+dotnet test MySolution.sln -c Release -- RunConfiguration.TargetPlatform=x64 /Parallel
+```
+
+For .NET 10 SDK and later versions, use a project-level matrix:
+
+```powershell
+$testProjects = @("tests/A.Tests/A.Tests.csproj", "tests/B.Tests/B.Tests.csproj")
+$testRunFailed = $false
+foreach ($configuration in "Debug", "Release") {
+    foreach ($architecture in "x86", "x64") {
+        foreach ($testProject in $testProjects) {
+            dotnet test --project $testProject -c $configuration --arch $architecture
+            if ($LASTEXITCODE -ne 0) {
+                $testRunFailed = $true
+            }
+        }
+    }
+}
+if ($testRunFailed) {
+    throw "One or more test runs failed."
+}
+```
+
 The test-related arguments are VSTest specific and so need to be transformed to match the new platform. The following table shows the mapping between the VSTest arguments and the new platform:
 
 | VSTest argument | New platform argument |
@@ -108,6 +157,8 @@ The test-related arguments are VSTest specific and so need to be transformed to
 | `--results-directory <RESULTS_DIR>` | `--results-directory <RESULTS_DIR>` |
 | `-s\|--settings <SETTINGS_FILE>` | Depends upon the selected test framework |
 | `-t\|--list-tests` | `--list-tests` |
+| `-- RunConfiguration.TargetPlatform=<ARCHITECTURE>` | `--arch <ARCHITECTURE>` for a project invocation |
+| `/Parallel` | No option required. MTP runs test modules in parallel by default. |
 | `-- <RunSettings arguments>` | `--test-parameter` (provided by [VSTestBridge](microsoft-testing-platform-extensions-vstest-bridge.md)) |
 
 #### `--collect`
@@ -178,6 +229,27 @@ dotnet test --report-trx
 > As explained earlier, when using MTP with the VSTest-based `dotnet test`, extra `--` is needed before the arguments intended to be passed to the platform.
 > So, this becomes `dotnet test -- --report-trx`.
 
+GitHub Actions reporter options are package-specific and aren't interchangeable:
+
+| Reporter package | MTP option |
+|---|---|
+| [Microsoft.Testing.Extensions.GitHubActionsReport](microsoft-testing-platform-test-reports.md#github-actions-reports) | `--report-gh` |
+| [GitHubActionsTestLogger](https://www.nuget.org/packages/GitHubActionsTestLogger) | `--report-github` |
+
+The test application recognizes an option only when the package that owns it is installed and registered. For example, if you migrate `--logger GitHubActions` and keep the `GitHubActionsTestLogger` package, replace the VSTest command:
+
+```dotnetcli
+dotnet test --logger GitHubActions
+```
+
+With .NET 10 SDK and later versions, use:
+
+```dotnetcli
+dotnet test --report-github
+```
+
+For .NET 9 SDK and earlier versions, use `dotnet test -- --report-github` instead.
+
 #### `--settings`
 
 VSTest's `--settings` is used to specify a RunSettings file for the test run. RunSettings isn't supported by the core MTP and was replaced by a more modern [`testconfig.json`](./microsoft-testing-platform-config.md) configuration file. However, MSTest and NUnit still support the old RunSettings when running MTP and `--settings` is still supported.
diff --git a/docs/core/testing/mstest-analyzers/mstest0082.md b/docs/core/testing/mstest-analyzers/mstest0082.md
new file mode 100644
index 0000000000000..188e61fbc2b19
--- /dev/null
+++ b/docs/core/testing/mstest-analyzers/mstest0082.md
@@ -0,0 +1,89 @@
+---
+title: "MSTEST0082: A test class inherits a lifecycle or test method from a different MSTest version"
+description: "Learn about code analysis rule MSTEST0082: A test class inherits a lifecycle or test method from a different MSTest version"
+ms.date: 08/26/2026
+f1_keywords:
+- MSTEST0082
+- InheritedMemberFromDifferentMSTestVersionAnalyzer
+helpviewer_keywords:
+- InheritedMemberFromDifferentMSTestVersionAnalyzer
+- MSTEST0082
+author: evangelink
+ms.author: amauryleve
+ai-usage: ai-assisted
+dev_langs:
+- CSharp
+---
+# MSTEST0082: A test class inherits a lifecycle or test method from a different MSTest version
+
+| Property                            | Value                                              |
+|-------------------------------------|----------------------------------------------------|
+| **Rule ID**                         | MSTEST0082                                         |
+| **Title**                           | A test class inherits a lifecycle or test method from a different MSTest version |
+| **Category**                        | Usage                                              |
+| **Fix is breaking or non-breaking** | Non-breaking                                       |
+| **Enabled by default**              | Yes                                                |
+| **Default severity**                | Warning                                            |
+| **Introduced in version**           | 4.4.0 (preview)                                    |
+| **Is there a code fix**             | No                                                 |
+
+> [!IMPORTANT]
+> This analyzer is planned for MSTest 4.4 and is available only in preview builds until MSTest 4.4.0 is released.
+
+## Cause
+
+A discoverable test class inherits a public test method or lifecycle method from an assembly that references a different major version of MSTest.
+
+## Rule description
+
+MSTest matches test and lifecycle attributes by exact runtime type identity. MSTest v3 defines these attributes in `Microsoft.VisualStudio.TestPlatform.TestFramework`, while MSTest v4 defines them in `MSTest.TestFramework`. If a base library and a derived test project use different major versions, the adapter silently ignores inherited attributes from the other framework assembly. As a result, inherited tests aren't discovered, and inherited initialization or cleanup methods don't run.
+
+For example, a shared test library built with MSTest v3 might declare:
+
+```csharp
+public abstract class SharedTests
+{
+    [TestMethod] public void InheritedTest() { }
+}
+```
+
+An MSTest v4 project that derives from the base class triggers the diagnostic:
+
+```csharp
+[TestClass]
+public sealed class ProductTests : SharedTests { } // Violation
+```
+
+The analyzer checks inherited test methods, test initialization and cleanup methods, and class initialization and cleanup methods that are configured to run for derived classes.
+
+## How to fix violations
+
+Reference the same MSTest major version from the base library and the derived test project. Recompile the assembly that declares the base class and, for a custom attribute derived from an MSTest attribute, recompile the assembly that declares the custom attribute.
+
+## When to suppress warnings
+
+Don't suppress warnings from this rule. A violation means that MSTest silently skips inherited tests or lifecycle methods.
+
+## Suppress a warning
+
+If you just want to suppress a single violation, add preprocessor directives to your source file to disable and then re-enable the rule.
+
+```csharp
+#pragma warning disable MSTEST0082
+// The code that's violating the rule is on this line.
+#pragma warning restore MSTEST0082
+```
+
+To disable the rule for a file, folder, or project, set its severity to `none` in the [configuration file](../../../fundamentals/code-analysis/configuration-files.md).
+
+```ini
+[*.{cs,vb}]
+dotnet_diagnostic.MSTEST0082.severity = none
+```
+
+For more information, see [How to suppress code analysis warnings](../../../fundamentals/code-analysis/suppress-warnings.md).
+
+## See also
+
+- [Migrate from MSTest v3 to v4](../unit-testing-mstest-migration-v3-v4.md)
+- [Test lifecycle](../unit-testing-mstest-writing-tests-lifecycle.md)
diff --git a/docs/core/testing/mstest-analyzers/mstest0083.md b/docs/core/testing/mstest-analyzers/mstest0083.md
new file mode 100644
index 0000000000000..f184e1a012ebe
--- /dev/null
+++ b/docs/core/testing/mstest-analyzers/mstest0083.md
@@ -0,0 +1,91 @@
+---
+title: "MSTEST0083: Use '[ExecutableCondition]' instead of 'File.Exists' checks before 'Process.Start'"
+description: "Learn about code analysis rule MSTEST0083: Use '[ExecutableCondition]' instead of 'File.Exists' checks before 'Process.Start'"
+ms.date: 08/26/2026
+f1_keywords:
+- MSTEST0083
+- UseExecutableConditionAttributeInsteadOfProcessCheckAnalyzer
+helpviewer_keywords:
+- UseExecutableConditionAttributeInsteadOfProcessCheckAnalyzer
+- MSTEST0083
+author: evangelink
+ms.author: amauryleve
+ai-usage: ai-assisted
+dev_langs:
+- CSharp
+---
+# MSTEST0083: Use '\[ExecutableCondition]' instead of 'File.Exists' checks before 'Process.Start'
+
+| Property                            | Value                                              |
+|-------------------------------------|----------------------------------------------------|
+| **Rule ID**                         | MSTEST0083                                         |
+| **Title**                           | Use '\[ExecutableCondition]' instead of 'File.Exists' checks before 'Process.Start' |
+| **Category**                        | Usage                                              |
+| **Fix is breaking or non-breaking** | Non-breaking                                       |
+| **Enabled by default**              | Yes                                                |
+| **Default severity**                | Info                                               |
+| **Introduced in version**           | 4.4.0 (preview)                                    |
+| **Is there a code fix**             | Yes, for C# only                                   |
+
+> [!IMPORTANT]
+> This analyzer is planned for MSTest 4.4 and is available only in preview builds until MSTest 4.4.0 is released.
+
+## Cause
+
+A test method first checks whether an executable exists and returns or calls `Assert.Inconclusive` when it doesn't, then calls `Process.Start` with the same executable path.
+
+## Rule description
+
+Use `[ExecutableCondition]` to declare that a test requires an executable. The attribute reports the test as skipped when MSTest can't resolve the executable. An early return incorrectly reports the test as passed, and an imperative check hides the requirement from discovery and reporting tools.
+
+```csharp
+[TestMethod]
+public void RunsTool()
+{
+    if (!File.Exists("tool.exe")) return; // Violation
+    Process.Start("tool.exe");
+}
+```
+
+The analyzer recognizes a first-statement guard without a meaningful `else` branch when both `File.Exists` and the later `Process.Start` use the same constant executable path.
+
+## How to fix violations
+
+Replace the guard with `[ExecutableCondition]`.
+
+```csharp
+[TestMethod]
+[ExecutableCondition("tool.exe")]
+public void RunsTool() => Process.Start("tool.exe");
+```
+
+A C# code fix replaces the guard with the attribute. Visual Basic reports the diagnostic but doesn't provide an automatic fix.
+
+## When to suppress warnings
+
+Suppress the rule when the file check validates data rather than an executable prerequisite, or when the test needs behavior that `ExecutableConditionAttribute` can't express.
+
+## Suppress a warning
+
+If you just want to suppress a single violation, add preprocessor directives to your source file to disable and then re-enable the rule.
+
+```csharp
+#pragma warning disable MSTEST0083
+// The code that's violating the rule is on this line.
+#pragma warning restore MSTEST0083
+```
+
+To disable the rule for a file, folder, or project, set its severity to `none` in the [configuration file](../../../fundamentals/code-analysis/configuration-files.md).
+
+```ini
+[*.{cs,vb}]
+dotnet_diagnostic.MSTEST0083.severity = none
+```
+
+For more information, see [How to suppress code analysis warnings](../../../fundamentals/code-analysis/suppress-warnings.md).
+
+## See also
+
+- [ExecutableConditionAttribute](../unit-testing-mstest-writing-tests-controlling-execution.md#executableconditionattribute)
+- [MSTEST0061: Use OSCondition attribute instead of runtime check](mstest0061.md)
+- [MSTEST0079: Use ArchitectureCondition attribute instead of runtime checks](mstest0079.md)
diff --git a/docs/core/testing/mstest-analyzers/overview.md b/docs/core/testing/mstest-analyzers/overview.md
index ade647d04055b..486ca0559e82a 100644
--- a/docs/core/testing/mstest-analyzers/overview.md
+++ b/docs/core/testing/mstest-analyzers/overview.md
@@ -3,7 +3,7 @@ title: MSTest code analysis
 description: Learn about the MSTest code analysis.
 author: evangelink
 ms.author: amauryleve
-ms.date: 08/06/2026
+ms.date: 08/26/2026
 ai-usage: ai-assisted
 ---
 
@@ -118,6 +118,7 @@ Rules that help ensure your test classes and methods are properly structured and
 - [MSTEST0072](mstest0072.md) - `[AssemblyFixtureProvider]` isn't supported with ahead-of-time compilation
 - [MSTEST0078](mstest0078.md) - `[DependsOn]` arguments should be valid
 - [MSTEST0081](mstest0081.md) - `[TestFilterProvider]` should reference a valid test filter type
+- [MSTEST0082](mstest0082.md) - A test class inherits a lifecycle or test method from a different MSTest version
 
 Related documentation: [Write tests with MSTest](../unit-testing-mstest-writing-tests.md)
 
@@ -241,6 +242,8 @@ Rules for configuring test execution, parallelization, and other test settings:
 - [MSTEST0079](mstest0079.md) - Use ArchitectureCondition attribute instead of runtime checks
 - [MSTEST0080](mstest0080.md) - Use CICondition attribute instead of environment checks
 - [MSTEST0081](mstest0081.md) - `[TestFilterProvider]` should reference a valid test filter type
+- [MSTEST0082](mstest0082.md) - A test class inherits a lifecycle or test method from a different MSTest version
+- [MSTEST0083](mstest0083.md) - Use `[ExecutableCondition]` instead of `File.Exists` checks before `Process.Start`
 
 Related documentation: [Configure MSTest](../unit-testing-mstest-configure.md), [Running tests](../unit-testing-mstest-running-tests.md)
 
@@ -329,6 +332,8 @@ Related documentation: [Configure MSTest](../unit-testing-mstest-configure.md),
 | [MSTEST0079](mstest0079.md) | Usage | Use ArchitectureCondition attribute instead of runtime checks | Info |
 | [MSTEST0080](mstest0080.md) | Usage | Use CICondition attribute instead of environment checks | Info |
 | [MSTEST0081](mstest0081.md) | Usage | `[TestFilterProvider]` should reference a valid test filter type | Warning |
+| [MSTEST0082](mstest0082.md) | Usage | A test class inherits a lifecycle or test method from a different MSTest version | Warning |
+| [MSTEST0083](mstest0083.md) | Usage | Use `[ExecutableCondition]` instead of `File.Exists` checks before `Process.Start` | Info |
 
 \* Escalated to Error in `Recommended` and `All` modes.
 
diff --git a/docs/core/testing/mstest-analyzers/usage-rules.md b/docs/core/testing/mstest-analyzers/usage-rules.md
index 04154cef03af1..e3a24d0dbc481 100644
--- a/docs/core/testing/mstest-analyzers/usage-rules.md
+++ b/docs/core/testing/mstest-analyzers/usage-rules.md
@@ -3,7 +3,7 @@ title: MSTest Usage rules (code analysis)
 description: Learn about MSTest code analysis usage rules.
 author: evangelink
 ms.author: amauryleve
-ms.date: 08/06/2026
+ms.date: 08/26/2026
 ai-usage: ai-assisted
 ---
 
@@ -77,6 +77,8 @@ Usage rules support proper usage of MSTest attributes, methods, and patterns. Th
 | [MSTEST0079](mstest0079.md) | Use ArchitectureCondition attribute instead of runtime checks. | Info | Yes |
 | [MSTEST0080](mstest0080.md) | Use CICondition attribute instead of environment checks. | Info | Yes |
 | [MSTEST0081](mstest0081.md) | `[TestFilterProvider]` should reference a valid test filter type. | Warning | No |
+| [MSTEST0082](mstest0082.md) | A test class inherits a lifecycle or test method from a different MSTest version. | Warning | No |
+| [MSTEST0083](mstest0083.md) | Use `[ExecutableCondition]` instead of `File.Exists` checks before `Process.Start`. | Info | Yes |
 
 \* Escalated to Error in `Recommended` and `All` modes.
 
@@ -91,6 +93,7 @@ Ensure your test classes, methods, and fixtures follow MSTest requirements:
 - **[MSTEST0030](mstest0030.md)**: Methods with [TestMethod] must be in a [TestClass].
 - **[MSTEST0063](mstest0063.md)**: Test class constructor validation.
 - **[MSTEST0069](mstest0069.md)**: Apply [TestClass] directly so source-generated discovery finds the class.
+- **[MSTEST0082](mstest0082.md)**: Keep base and derived test classes on the same MSTest major version.
 
 ### Lifecycle methods
 
@@ -105,6 +108,7 @@ Validate initialization and cleanup methods:
 - **[MSTEST0034](mstest0034.md)**: Set ClassCleanupBehavior.EndOfClass.
 - **[MSTEST0050](mstest0050.md)**: Global test fixture validation.
 - **[MSTEST0072](mstest0072.md)**: Don't use shared assembly fixture providers with ahead-of-time compilation.
+- **[MSTEST0082](mstest0082.md)**: Recompile inherited lifecycle methods against the test project's MSTest version.
 
 ### Data-driven testing
 
@@ -181,6 +185,8 @@ Rules for tests that run in parallel:
 - **[MSTEST0079](mstest0079.md)**: Use `ArchitectureCondition` instead of runtime architecture checks.
 - **[MSTEST0080](mstest0080.md)**: Use `CICondition` instead of environment checks.
 - **[MSTEST0081](mstest0081.md)**: Validate test filter provider registrations.
+- **[MSTEST0082](mstest0082.md)**: Detect inherited tests and lifecycle methods compiled against another MSTest major version.
+- **[MSTEST0083](mstest0083.md)**: Use `ExecutableCondition` instead of an imperative executable check.
 
 ## Related documentation
 
diff --git a/docs/core/testing/snippets/order-unit-tests/csharp/MSTest.Project/MSTest.Project.csproj b/docs/core/testing/snippets/order-unit-tests/csharp/MSTest.Project/MSTest.Project.csproj
index de67a89c56f7e..0c41737a1e24d 100644
--- a/docs/core/testing/snippets/order-unit-tests/csharp/MSTest.Project/MSTest.Project.csproj
+++ b/docs/core/testing/snippets/order-unit-tests/csharp/MSTest.Project/MSTest.Project.csproj
@@ -8,7 +8,7 @@
   </PropertyGroup>
 
   <ItemGroup>
-    <PackageReference Include="Microsoft.NET.Test.Sdk" Version="18.8.1" />
+    <PackageReference Include="Microsoft.NET.Test.Sdk" Version="18.9.0" />
     <PackageReference Include="MSTest.TestAdapter" Version="4.3.3" />
     <PackageReference Include="MSTest.TestFramework" Version="4.3.3" />
     <PackageReference Include="coverlet.collector" Version="10.0.1">
diff --git a/docs/core/testing/snippets/order-unit-tests/csharp/NUnit.TestProject/NUnit.Project.csproj b/docs/core/testing/snippets/order-unit-tests/csharp/NUnit.TestProject/NUnit.Project.csproj
index 52c129fc5ff8a..372f386f510f0 100644
--- a/docs/core/testing/snippets/order-unit-tests/csharp/NUnit.TestProject/NUnit.Project.csproj
+++ b/docs/core/testing/snippets/order-unit-tests/csharp/NUnit.TestProject/NUnit.Project.csproj
@@ -10,7 +10,7 @@
   <ItemGroup>
     <PackageReference Include="NUnit" Version="4.6.1" />
     <PackageReference Include="NUnit3TestAdapter" Version="6.2.0" />
-    <PackageReference Include="Microsoft.NET.Test.Sdk" Version="18.8.1" />
+    <PackageReference Include="Microsoft.NET.Test.Sdk" Version="18.9.0" />
     <PackageReference Include="NUnit.Analyzers" Version="4.14.0">
         <PrivateAssets>all</PrivateAssets>
         <IncludeAssets>runtime; build; native; contentfiles; analyzers</IncludeAssets>
diff --git a/docs/core/testing/snippets/order-unit-tests/csharp/XUnit.TestProject/XUnit.Project.csproj b/docs/core/testing/snippets/order-unit-tests/csharp/XUnit.TestProject/XUnit.Project.csproj
index 767ca5e1f7b41..ac785d6263b1b 100644
--- a/docs/core/testing/snippets/order-unit-tests/csharp/XUnit.TestProject/XUnit.Project.csproj
+++ b/docs/core/testing/snippets/order-unit-tests/csharp/XUnit.TestProject/XUnit.Project.csproj
@@ -8,9 +8,9 @@
   </PropertyGroup>
 
   <ItemGroup>
-    <PackageReference Include="Microsoft.NET.Test.Sdk" Version="18.8.1" />
+    <PackageReference Include="Microsoft.NET.Test.Sdk" Version="18.9.0" />
     <PackageReference Include="xunit" Version="2.9.3" />
-    <PackageReference Include="xunit.runner.visualstudio" Version="3.1.5">
+    <PackageReference Include="xunit.runner.visualstudio" Version="4.0.0">
       <PrivateAssets>all</PrivateAssets>
       <IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
     </PackageReference>
diff --git a/docs/core/testing/unit-testing-mstest-sdk.md b/docs/core/testing/unit-testing-mstest-sdk.md
index 4de82c2381838..6c232f7fb31f2 100644
--- a/docs/core/testing/unit-testing-mstest-sdk.md
+++ b/docs/core/testing/unit-testing-mstest-sdk.md
@@ -3,7 +3,7 @@ title: MSTest SDK configuration
 author: MarcoRossignoli
 description: Learn how to configure MSTest.Sdk profiles, extensions, and advanced features.
 ms.author: mrossignoli
-ms.date: 08/06/2026
+ms.date: 08/26/2026
 ai-usage: ai-assisted
 ---
 
@@ -46,7 +46,7 @@ You can set the profile using the property `TestingExtensionsProfile` with one o
   * [Code Coverage](./microsoft-testing-platform-code-coverage.md#microsoft-code-coverage)
   * [Trx Report](./microsoft-testing-platform-test-reports.md#visual-studio-test-reports-trx)
 
-* `AllMicrosoft` - Enable all extensions shipped by Microsoft (including extensions with a restrictive license).
+* `AllMicrosoft` - Enables the Microsoft extensions selected for broad out-of-the-box use, including extensions with a restrictive license. Experimental and API-only extensions can still require explicit opt-in.
 
   Enables the following extensions:
 
@@ -55,6 +55,8 @@ You can set the profile using the property `TestingExtensionsProfile` with one o
   * [Fakes](./microsoft-testing-platform-fakes.md) (MSTest.Sdk 3.7.0+)
   * [Hang Dump](./microsoft-testing-platform-crash-hang-dumps.md#hang-dump)
   * [Hot Reload](./microsoft-testing-platform-hot-reload.md#hot-reload)
+  * [HTML Report](./microsoft-testing-platform-test-reports.md#html-reports)
+  * [GitHub Actions Report](./microsoft-testing-platform-test-reports.md#github-actions-reports) (MSTest.Sdk 4.3.0+)
   * [Retry](./microsoft-testing-platform-retry.md#retry)
   * [Trx Report](./microsoft-testing-platform-test-reports.md#visual-studio-test-reports-trx)
   * [AzureDevOpsReport](./microsoft-testing-platform-test-reports.md#azure-devops-reports)
@@ -79,12 +81,15 @@ Here's a full example, using the `None` profile:
 | [Fakes](https://www.nuget.org/packages/Microsoft.Testing.Extensions.Fakes)                        |       |                    | :heavy_check_mark:¹ |
 | [Hang Dump](https://www.nuget.org/packages/Microsoft.Testing.Extensions.HangDump)                 |       |                    | :heavy_check_mark:  |
 | [Hot Reload](https://www.nuget.org/packages/Microsoft.Testing.Extensions.HotReload)               |       |                    | :heavy_check_mark:  |
+| [HTML Report](https://www.nuget.org/packages/Microsoft.Testing.Extensions.HtmlReport)             |       |                    | :heavy_check_mark:  |
+| [GitHub Actions Report](https://www.nuget.org/packages/Microsoft.Testing.Extensions.GitHubActionsReport) |       |              | :heavy_check_mark:³ |
 | [Retry](https://www.nuget.org/packages/Microsoft.Testing.Extensions.Retry)                        |       |                    | :heavy_check_mark:  |
 | [Trx](https://www.nuget.org/packages/Microsoft.Testing.Extensions.TrxReport)                      |       | :heavy_check_mark: | :heavy_check_mark:  |
 | [AzureDevOpsReport](./microsoft-testing-platform-test-reports.md#azure-devops-reports) |       |                    | :heavy_check_mark:²  |
 
 ¹ MSTest.Sdk 3.7.0+
 ² MSTest.Sdk 3.11.0+
+³ MSTest.Sdk 4.3.0+
 
 ### Enable or disable extensions
 
@@ -105,7 +110,13 @@ For example, to enable the crash dump extension (NuGet package [Microsoft.Testin
 
 For a list of all available extensions, see [MTP features](./microsoft-testing-platform-features.md).
 
-Starting with MSTest.Sdk 4.3, enable the experimental JUnit report extension with `<EnableMicrosoftTestingExtensionsJUnitReport>true</EnableMicrosoftTestingExtensionsJUnitReport>`, then pass `--report-junit` when you run the test application. The extension is available only with Microsoft.Testing.Platform and isn't included in the `Default` or `AllMicrosoft` profiles.
+Some MTP extensions remain opt-in and aren't included in the `Default` or `AllMicrosoft` profiles:
+
+- Starting with MSTest.Sdk 4.3, set `<EnableMicrosoftTestingExtensionsJUnitReport>true</EnableMicrosoftTestingExtensionsJUnitReport>`, then pass `--report-junit`.
+- Starting with the MSTest.Sdk 4.4 preview, set `<EnableMicrosoftTestingExtensionsCtrfReport>true</EnableMicrosoftTestingExtensionsCtrfReport>`, then pass `--report-ctrf`.
+- To reference the OpenTelemetry extension, set `<EnableMicrosoftTestingExtensionsOpenTelemetry>true</EnableMicrosoftTestingExtensionsOpenTelemetry>`. Because the extension requires API configuration, register it in your custom entry point as described in [OpenTelemetry](microsoft-testing-platform-open-telemetry.md).
+
+These extensions are available only with MTP.
 
 > [!WARNING]
 > It's important to review the licensing terms for each extension as they might vary.
diff --git a/docs/csharp/roslyn-sdk/tutorials/snippets/how-to-write-csharp-analyzer-code-fix/MakeConst/MakeConst.CodeFixes/MakeConst.CodeFixes.csproj b/docs/csharp/roslyn-sdk/tutorials/snippets/how-to-write-csharp-analyzer-code-fix/MakeConst/MakeConst.CodeFixes/MakeConst.CodeFixes.csproj
index a48924612fd42..4ad3dd306d3be 100644
--- a/docs/csharp/roslyn-sdk/tutorials/snippets/how-to-write-csharp-analyzer-code-fix/MakeConst/MakeConst.CodeFixes/MakeConst.CodeFixes.csproj
+++ b/docs/csharp/roslyn-sdk/tutorials/snippets/how-to-write-csharp-analyzer-code-fix/MakeConst/MakeConst.CodeFixes/MakeConst.CodeFixes.csproj
@@ -7,8 +7,8 @@
   </PropertyGroup>
 
   <ItemGroup>
-    <PackageReference Include="Microsoft.CodeAnalysis.CSharp" Version="5.6.0" />
-    <PackageReference Include="Microsoft.CodeAnalysis.CSharp.Workspaces" Version="5.6.0" />
+    <PackageReference Include="Microsoft.CodeAnalysis.CSharp" Version="5.9.0" />
+    <PackageReference Include="Microsoft.CodeAnalysis.CSharp.Workspaces" Version="5.9.0" />
   </ItemGroup>
 
   <ItemGroup>
diff --git a/docs/csharp/roslyn-sdk/tutorials/snippets/how-to-write-csharp-analyzer-code-fix/MakeConst/MakeConst.Test/MakeConst.Test.csproj b/docs/csharp/roslyn-sdk/tutorials/snippets/how-to-write-csharp-analyzer-code-fix/MakeConst/MakeConst.Test/MakeConst.Test.csproj
index 930e832c01091..dd920bf8a436b 100644
--- a/docs/csharp/roslyn-sdk/tutorials/snippets/how-to-write-csharp-analyzer-code-fix/MakeConst/MakeConst.Test/MakeConst.Test.csproj
+++ b/docs/csharp/roslyn-sdk/tutorials/snippets/how-to-write-csharp-analyzer-code-fix/MakeConst/MakeConst.Test/MakeConst.Test.csproj
@@ -11,7 +11,7 @@
     <PackageReference Include="Microsoft.NET.Test.Sdk" Version="17.13.0" />
     <PackageReference Include="MSTest.TestAdapter" Version="4.3.3" />
     <PackageReference Include="MSTest.TestFramework" Version="4.3.3" />
-    <PackageReference Include="Microsoft.CodeAnalysis" Version="5.6.0" />
+    <PackageReference Include="Microsoft.CodeAnalysis" Version="5.9.0" />
     <PackageReference Include="Microsoft.CodeAnalysis.CSharp.Analyzer.Testing.MSTest" Version="1.1.2" />
     <PackageReference Include="Microsoft.CodeAnalysis.CSharp.CodeFix.Testing.MSTest" Version="1.1.2" />
     <PackageReference Include="Microsoft.CodeAnalysis.CSharp.CodeRefactoring.Testing.MSTest" Version="1.1.2" />
diff --git a/docs/csharp/roslyn-sdk/tutorials/snippets/how-to-write-csharp-analyzer-code-fix/MakeConst/MakeConst/MakeConst.csproj b/docs/csharp/roslyn-sdk/tutorials/snippets/how-to-write-csharp-analyzer-code-fix/MakeConst/MakeConst/MakeConst.csproj
index 12bc57d45d344..0ceff617a9adf 100644
--- a/docs/csharp/roslyn-sdk/tutorials/snippets/how-to-write-csharp-analyzer-code-fix/MakeConst/MakeConst/MakeConst.csproj
+++ b/docs/csharp/roslyn-sdk/tutorials/snippets/how-to-write-csharp-analyzer-code-fix/MakeConst/MakeConst/MakeConst.csproj
@@ -9,8 +9,8 @@
   </PropertyGroup>
 
   <ItemGroup>
-    <PackageReference Include="Microsoft.CodeAnalysis.Analyzers" Version="5.6.0" />
-    <PackageReference Include="Microsoft.CodeAnalysis.CSharp" Version="5.6.0" />
+    <PackageReference Include="Microsoft.CodeAnalysis.Analyzers" Version="5.9.0" />
+    <PackageReference Include="Microsoft.CodeAnalysis.CSharp" Version="5.9.0" />
   </ItemGroup>
 
   <ItemGroup>
diff --git a/docs/navigate/devops-testing/toc.yml b/docs/navigate/devops-testing/toc.yml
index eb7b83755c05d..a1f3ae47b9ba7 100644
--- a/docs/navigate/devops-testing/toc.yml
+++ b/docs/navigate/devops-testing/toc.yml
@@ -266,6 +266,10 @@ items:
                         href: ../../core/testing/mstest-analyzers/mstest0080.md
                       - name: MSTEST0081
                         href: ../../core/testing/mstest-analyzers/mstest0081.md
+                      - name: MSTEST0082
+                        href: ../../core/testing/mstest-analyzers/mstest0082.md
+                      - name: MSTEST0083
+                        href: ../../core/testing/mstest-analyzers/mstest0083.md
               - name: Migration
                 items:
                   - name: Migrate from MSTest v1 to v3
@@ -350,6 +354,9 @@ items:
                   - name: OpenTelemetry
                     href: ../../core/testing/microsoft-testing-platform-open-telemetry.md
                     displayName: MTP,OpenTelemetry,traces,metrics
+                  - name: AI integrations
+                    href: ../../core/testing/microsoft-testing-platform-ai.md
+                    displayName: MTP,AI,Azure AI Foundry,Azure OpenAI,IChatClient
                   - name: Retry
                     href: ../../core/testing/microsoft-testing-platform-retry.md
                     displayName: MTP,retry,flaky tests
@@ -392,6 +399,9 @@ items:
                   - name: Services
                     href: ../../core/testing/microsoft-testing-platform-architecture-services.md
                     displayName: MTP,services,IServiceProvider
+                  - name: Server mode
+                    href: ../../core/testing/microsoft-testing-platform-server-mode.md
+                    displayName: MTP,server mode,JSON-RPC,IDE integration,test client
           - name: VSTest
             href: https://github.com/microsoft/vstest
       - name: Testing with 'dotnet test'
diff --git a/docs/orleans/host/snippets/aspire/Client/Client.csproj b/docs/orleans/host/snippets/aspire/Client/Client.csproj
index 2be5e5bc85dc5..9c0308f6c49c6 100644
--- a/docs/orleans/host/snippets/aspire/Client/Client.csproj
+++ b/docs/orleans/host/snippets/aspire/Client/Client.csproj
@@ -8,12 +8,12 @@
   <ItemGroup>
     <PackageReference Include="Microsoft.Orleans.Client" Version="10.2.2" />
     <PackageReference Include="Microsoft.Orleans.Clustering.Redis" Version="10.2.2" />
-    <PackageReference Include="Aspire.StackExchange.Redis" Version="13.4.6" />
+    <PackageReference Include="Aspire.StackExchange.Redis" Version="13.5.0" />
   </ItemGroup>
   <!-- </client_packages> -->
 
   <ItemGroup>
-    <PackageReference Include="Microsoft.Extensions.Hosting" Version="10.0.8" />
+    <PackageReference Include="Microsoft.Extensions.Hosting" Version="10.0.11" />
   </ItemGroup>
 
   <ItemGroup>
diff --git a/docs/orleans/host/snippets/aspire/ServiceDefaults/ServiceDefaults.csproj b/docs/orleans/host/snippets/aspire/ServiceDefaults/ServiceDefaults.csproj
index 3a46347aefe7c..a229877443b73 100644
--- a/docs/orleans/host/snippets/aspire/ServiceDefaults/ServiceDefaults.csproj
+++ b/docs/orleans/host/snippets/aspire/ServiceDefaults/ServiceDefaults.csproj
@@ -11,7 +11,7 @@
     <PackageReference Include="OpenTelemetry.Instrumentation.AspNetCore" Version="1.17.0" />
     <PackageReference Include="OpenTelemetry.Instrumentation.Http" Version="1.17.0" />
     <PackageReference Include="OpenTelemetry.Instrumentation.Runtime" Version="1.17.0" />
-    <PackageReference Include="Aspire.StackExchange.Redis" Version="13.4.6" />
+    <PackageReference Include="Aspire.StackExchange.Redis" Version="13.5.0" />
   </ItemGroup>
 
 </Project>
diff --git a/docs/orleans/host/snippets/aspire/Silo/Silo.csproj b/docs/orleans/host/snippets/aspire/Silo/Silo.csproj
index a9d1304b3565a..37512d869aa1d 100644
--- a/docs/orleans/host/snippets/aspire/Silo/Silo.csproj
+++ b/docs/orleans/host/snippets/aspire/Silo/Silo.csproj
@@ -8,14 +8,14 @@
   <ItemGroup>
     <PackageReference Include="Microsoft.Orleans.Server" Version="10.2.2" />
     <PackageReference Include="Microsoft.Orleans.Clustering.Redis" Version="10.2.2" />
-    <PackageReference Include="Aspire.StackExchange.Redis" Version="13.4.6" />
+    <PackageReference Include="Aspire.StackExchange.Redis" Version="13.5.0" />
   </ItemGroup>
   <!-- </silo_packages> -->
 
   <ItemGroup>
-    <PackageReference Include="Aspire.Azure.Data.Tables" Version="13.4.6" />
+    <PackageReference Include="Aspire.Azure.Data.Tables" Version="13.5.0" />
     <PackageReference Include="Microsoft.Orleans.Persistence.Redis" Version="10.2.2" />
-    <PackageReference Include="Microsoft.Extensions.Hosting" Version="10.0.8" />
+    <PackageReference Include="Microsoft.Extensions.Hosting" Version="10.0.11" />
   </ItemGroup>
 
   <ItemGroup>