Align large payload doc with updated samples

Author: torosent

articles/azure-functions/durable/durable-task-scheduler/durable-task-scheduler-large-payloads.md

@@ -4,7 +4,9 @@ description: Learn how to use large payload support in Durable Functions and the
 ms.topic: conceptual
 ms.date: 03/14/2026
 ms.author: torosent
+ms.service: azure-functions
 ms.subservice: durable-task-scheduler
+ms.devlang: csharp
 zone_pivot_groups: azure-durable-approach
 ---
 
@@ -39,6 +41,8 @@ When you enable large payload support, the runtime follows the same high level f
 1. It sends a blob reference through Durable Task Scheduler instead of the full payload.
 1. The runtime automatically resolves the reference before your orchestrator or activity code reads the value.
 
+The current .NET samples use deterministic, low-compressibility 1.5 MiB payloads. That keeps the stored blob size representative, even though the runtime writes blobs with gzip content encoding.
+
 Large payload support changes how payloads move through the runtime. It doesn't change the recommendation to keep durable state as small as practical.
 
 ## Choose the right pattern
@@ -168,6 +172,10 @@ For an end-to-end .NET example, see the [Durable Task SDK large payload sample](
 
 Large payload support with Durable Task Scheduler is available only for the .NET Durable Task SDK.
 
+# [PowerShell](#tab/powershell)
+
+Large payload support with Durable Task Scheduler is available only for the .NET Durable Task SDK.
+
 # [Python](#tab/python)
 
 Large payload support with Durable Task Scheduler is available only for the .NET Durable Task SDK.
@@ -180,6 +188,85 @@ Large payload support with Durable Task Scheduler is available only for the .NET
 
 ::: zone-end
 
+## Environment variable configuration
+
+::: zone pivot="durable-functions"
+
+Use these local settings or app settings with the current Durable Functions samples.
+
+# [C#](#tab/csharp)
+
+| Setting | Description | Sample default |
+| --- | --- | --- |
+| `FUNCTIONS_WORKER_RUNTIME` | Azure Functions isolated worker runtime | `dotnet-isolated` |
+| `AzureWebJobsStorage` | Storage for Functions host state and payload blobs | `UseDevelopmentStorage=true` locally |
+| `DTS_CONNECTION_STRING` | Durable Task Scheduler connection string | `Endpoint=http://localhost:8080;Authentication=None` |
+| `TASKHUB_NAME` | Target task hub | `default` |
+| `PAYLOAD_SIZE_BYTES` | Payload size used by the starter or generated by each activity | `1572864` |
+| `ACTIVITY_COUNT` | Number of parallel activities in the fan-out/fan-in sample only | `3` |
+
+The `ACTIVITY_COUNT` setting is used only by the `LargePayloadFanOutFanIn` sample. The `LargePayload` round-trip sample doesn't read it.
+
+# [JavaScript](#tab/javascript)
+
+Large payload support with Durable Task Scheduler is available only for .NET isolated C# Durable Functions apps.
+
+# [Python](#tab/python)
+
+Large payload support with Durable Task Scheduler is available only for .NET isolated C# Durable Functions apps.
+
+# [PowerShell](#tab/powershell)
+
+Large payload support with Durable Task Scheduler is available only for .NET isolated C# Durable Functions apps.
+
+# [Java](#tab/java)
+
+Large payload support with Durable Task Scheduler is available only for .NET isolated C# Durable Functions apps.
+
+---
+
+::: zone-end
+
+::: zone pivot="durable-task-sdks"
+
+Use these environment variables with the current .NET Durable Task SDK sample.
+
+# [C#](#tab/csharp)
+
+| Variable | Description | Sample default |
+| --- | --- | --- |
+| `DURABLE_TASK_SCHEDULER_CONNECTION_STRING` | Durable Task Scheduler connection string | `Endpoint=http://localhost:8080;TaskHub=default;Authentication=None` |
+| `PAYLOAD_STORAGE_CONNECTION_STRING` | Blob storage connection string for externalized payloads | `UseDevelopmentStorage=true` |
+| `PAYLOAD_STORAGE_ACCOUNT_URI` | Blob account URI for identity-based payload storage access | unset |
+| `PAYLOAD_CONTAINER_NAME` | Blob container for externalized payloads | `durabletask-payloads` |
+| `PAYLOAD_SIZE_BYTES` | Default payload size used by the run endpoint | `1572864` |
+| `EXTERNALIZE_THRESHOLD_BYTES` | Blob offload threshold | `900000` |
+| `PAYLOAD_STORAGE_MANAGED_IDENTITY_CLIENT_ID` | Optional user-assigned managed identity client ID for storage access | unset |
+| `AZURE_CLIENT_ID` | Alternate way to select a user-assigned managed identity | unset |
+| `ASPNETCORE_URLS` | Listen URLs for the sample's HTTP host | framework default |
+
+If `PAYLOAD_STORAGE_CONNECTION_STRING` isn't set and `PAYLOAD_STORAGE_ACCOUNT_URI` is provided, the sample uses `DefaultAzureCredential`. If you need a specific user-assigned identity, set `PAYLOAD_STORAGE_MANAGED_IDENTITY_CLIENT_ID` or `AZURE_CLIENT_ID`.
+
+# [JavaScript](#tab/javascript)
+
+This sample is shown for .NET, Java, and Python.
+
+# [PowerShell](#tab/powershell)
+
+This sample is shown for .NET, Java, and Python.
+
+# [Python](#tab/python)
+
+This sample is shown for .NET, Java, and Python.
+
+# [Java](#tab/java)
+
+This sample is shown for .NET, Java, and Python.
+
+---
+
+::: zone-end
+
 ## Azure permissions
 
 When you use Azure resources instead of local emulators, the app identity needs access to Durable Task Scheduler and Blob Storage:
@@ -210,6 +297,8 @@ The sample apps also validate the round trip:
 - The Durable Functions samples return a small summary object that confirms the input and output sizes.
 - The .NET Durable Task SDK sample prints whether the run creates new payload blobs.
 
+Because the runtime stores externalized payloads with gzip content encoding, Azure reports the compressed on-disk blob size. With the current low-compressibility sample payloads, those blob sizes should stay reasonably close to the logical payload size.
+
 ## Next steps
 
 > [!div class="nextstepaction"]