tweaks

Signed-off-by: Hannah Hunter <[email protected]>

Author: hhunter-ms

articles/azure-functions/durable/TOC.yml

@@ -130,14 +130,10 @@
             href: ./durable-task-scheduler/develop-with-durable-task-scheduler.md
   - name: Durable Task SDKs
     items:
-    - name: Scheduler API
-      href: ./durable-task-scheduler/durable-task-scheduler.md #placeholder
     - name: How-to guides
       items:
       - name: Autoscaling with the Durable Task SDKs in Azure Container Apps
         href: ./durable-task-scheduler/durable-task-scheduler-auto-scaling-aca.md
-      - name: Run app on Azure Container Apps
-        href: ./durable-task-scheduler/durable-task-scheduler.md #placeholder
   - name: Billing
     href: ./durable-task-scheduler/durable-task-scheduler-dedicated-sku.md
   - name: Troubleshoot

articles/azure-functions/durable/durable-task-scheduler/durable-task-scheduler-auto-scaling-aca.md

@@ -30,7 +30,7 @@ You can set the autoscaler configuration via the Azure portal, a Bicep template,
 | maxConcurrentWorkItemsCount | The maximum concurrent work items dispatched as an event to your compute, such as telling your compute to run an orchestration. | 1 |
 | taskhubName | The name of the task hub connected to the scheduler. | taskhub-ID |
 | workItemType | The work item type that is being dispatched. Options include Orchestration, Activity, or Entity. | Orchestration |
-| Managed identity | The user assigned or system assigned managed identity linked to the scheduler and task hub resource. Ensure the **Authenticate with a Managed Identity** checkbox is selected. | user@microsoft.com |
+| Managed identity | The user assigned managed identity linked to the scheduler and task hub resource. Ensure the **Authenticate with a Managed Identity** checkbox is selected. | someone@microsoft.com |
 
 # [Bicep](#tab/bicep)
 
@@ -58,34 +58,41 @@ scale: {
 
 | Field | Description | Example |
 | ----- | ----------- | ------- |
-| `minReplicas` | Minimum number of replicas allowed for the container revision at any given time. | `containerMinReplicas` |
-| `maxReplicas` | Maximum number of replicas allowed for the container revision at any given time. | `containerMaxReplicas` |
-| `endpoint` | The Durable Task Scheduler endpoint that the scaler connects to. | `dtsEndpoint` |
+| `minReplicas` | Minimum number of replicas allowed for the container revision at any given time. | `1` |
+| `maxReplicas` | Maximum number of replicas allowed for the container revision at any given time. | `10` |
+| `endpoint` | The Durable Task Scheduler endpoint that the scaler connects to. | `https://dts-ID.centralus.durabletask.io` |
 | `maxConcurrentWorkItemsCount` | The maximum concurrent work items dispatched as an event to your compute, such as telling your compute to run an orchestration. | `1` |
-| `taskhubName` | The name of the task hub connected to the scheduler. | `taskHubName` |
+| `taskhubName` | The name of the task hub connected to the scheduler. | `myTaskHubName` |
 | `workItemType` | The work item type that is being dispatched. Options include Orchestration, Activity, or Entity. | `Orchestration` |
-| `identity` | The user assigned or system assigned managed identity linked to the scheduler and task hub resource. | `scaleRuleIdentity` |
+| `identity` | The user assigned managed identity linked to the scheduler and task hub resource. | `[email protected]` |
 
 
 # [Azure CLI](#tab/cli)
 
 ```azurecli
-
+az containerapp create \
+  --resource-group <RESOURCE_GROUP> \
+  --name <APP_NAME> \
+  --environment <ENVIRONMENT_ID> \
+  --user-assigned <USER_ASSIGNED_IDENTITY_ID> \
+  --scale-rule-name dtsscaler-orchestration \
+  --scale-rule-type azure-durabletask-scheduler \
+  --scale-rule-metadata "endpoint=<DTS-ENDPOINT>" "maxConcurrentWorkItemsCount=1" "taskhubName=<TASKHUB-NAME> "workItemType=Orchestration" \
+  --scale-rule-identity <USER_ASSIGNED_IDENTITY_ID>
 ```
 
 | Field | Description | Example |
 | ----- | ----------- | ------- |
-| `minReplicas` | Minimum number of replicas allowed for the container revision at any given time. |  |
-| `maxReplicas` | Maximum number of replicas allowed for the container revision at any given time. |  |
-| `endpoint` | The Durable Task Scheduler endpoint that the scaler connects to. |  |
-| `maxConcurrentWorkItemsCount` | The maximum concurrent work items dispatched as an event to your compute, such as telling your compute to run an orchestration. |  |
-| `taskhubName` | The name of the task hub connected to the scheduler. |  |
-| `workItemType` | The work item type that is being dispatched. Options include Orchestration, Activity, or Entity. |  |
-| `identity` | The user assigned or system assigned managed identity linked to the scheduler and task hub resource. |  |
+| `minReplicas` | Minimum number of replicas allowed for the container revision at any given time. | `1` |
+| `maxReplicas` | Maximum number of replicas allowed for the container revision at any given time. | `10` |
+| `endpoint` | The Durable Task Scheduler endpoint that the scaler connects to. | `https://dts-ID.centralus.durabletask.io` |
+| `maxConcurrentWorkItemsCount` | The maximum concurrent work items dispatched as an event to your compute, such as telling your compute to run an orchestration. | `1` |
+| `taskhubName` | The name of the task hub connected to the scheduler. | `myTaskHubName` |
+| `workItemType` | The work item type that is being dispatched. Options include Orchestration, Activity, or Entity. | `Orchestration` |
+| `scale-rule-identity` | The user assigned managed identity linked to the scheduler and task hub resource. | `[email protected]` |
 
 ---
 
-
 ## Experiment with the sample
 
 The [Autoscaling in Azure Container Apps sample]() demonstrates how to implement autoscaling with the Azure Durable Task Scheduler using the .NET SDK in Azure Container Apps. The function chaining application pattern showcases an orchestration workflow that benefits from dynamically scaling worker instances based on load.
@@ -238,3 +245,5 @@ Verify the autoscaling is functioning correctly in the deployed solution.
 
 ## Next steps
 
+> [!div class="nextstepaction"]
+> [Learn more about the Durable Task Scheduler](./durable-task-scheduler.md)

articles/azure-functions/durable/durable-task-scheduler/quickstart-aca-azd-durable-task-sdk.md

@@ -21,7 +21,14 @@ zone_pivot_groups: df-languages
 
 ::: zone-end
 
-::: zone pivot="csharp,python,java"
+::: zone pivot="java"
+
+> [!IMPORTANT]
+> Currently, this quickstart sample isn't available for Java.
+
+::: zone-end
+
+::: zone pivot="csharp,python"
 
 In this quickstart, you learn how to:
 
@@ -57,16 +64,7 @@ Before you begin:
 
 ::: zone-end
 
-::: zone pivot="java"
-
-- Make sure you have [Java 8 or 11](https://www.java.com/en/download/).
-- Install [Docker](https://www.docker.com/products/docker-desktop/) for running the emulator.
-- Install [Azure Developer CLI](/azure/developer/azure-developer-cli/install-azd)
-- Clone the [Durable Task Scheduler GitHub repository](https://github.com/Azure-Samples/Durable-Task-Scheduler) to use the quickstart sample.
-
-::: zone-end
-
-::: zone pivot="csharp,python,java"
+::: zone pivot="csharp,python"
 
 ## Prepare the project
 
@@ -90,15 +88,7 @@ cd /samples/durable-task-sdks/python/function-chaining
 
 ::: zone-end
 
-::: zone pivot="java"
-
-```bash
-cd /samples/durable-task-sdks/java/function-chaining
-```
-
-::: zone-end
-
-::: zone pivot="csharp,python,java"
+::: zone pivot="csharp,python"
 
 ## Deploy using Azure Developer CLI
 
@@ -193,7 +183,7 @@ In the Azure portal, verify the orchestrations are running successfully.
 
 ::: zone-end
 
-::: zone pivot="csharp,python,java"
+::: zone pivot="csharp,python"
 
 ## Understanding the code
 
@@ -401,105 +391,6 @@ with DurableTaskSchedulerWorker(
 ```
 
 
-::: zone-end
-
-::: zone pivot="java"
-
-### Client
-
-The Client project:
-
-- Uses the same connection string logic as the worker
-- Implements a sequential orchestration scheduler that:
-  - Schedules 20 orchestration instances, one at a time
-  - Waits 5 seconds between scheduling each orchestration
-  - Tracks all orchestration instances in a list
-  - Waits for all orchestrations to complete before exiting
-- Uses standard logging to show progress and results
-
-```java
-// Create client using Azure-managed extensions
-DurableTaskClient client = DurableTaskSchedulerClientExtensions.createClientBuilder(connectionString).build();
-
-// Start a new instance of the registered "ActivityChaining" orchestration
-String instanceId = client.scheduleNewOrchestrationInstance(
-        "ActivityChaining",
-        new NewOrchestrationInstanceOptions().setInput("Hello, world!"));
-logger.info("Started new orchestration instance: {}", instanceId);
-
-// Block until the orchestration completes. Then print the final status, which includes the output.
-OrchestrationMetadata completedInstance = client.waitForInstanceCompletion(
-        instanceId,
-        Duration.ofSeconds(30),
-        true);
-logger.info("Orchestration completed: {}", completedInstance);
-logger.info("Output: {}", completedInstance.readOutputAs(String.class))
-```
-
-### Worker
-
-#### Orchestration Implementation
-
-The orchestration directly calls each activity in sequence using the standard `callActivity` method:
-
-```java
-DurableTaskGrpcWorker worker = DurableTaskSchedulerWorkerExtensions.createWorkerBuilder(connectionString)
-    .addOrchestration(new TaskOrchestrationFactory() {
-        @Override
-        public String getName() { return "ActivityChaining"; }
-
-        @Override
-        public TaskOrchestration create() {
-            return ctx -> {
-                String input = ctx.getInput(String.class);
-                String x = ctx.callActivity("Reverse", input, String.class).await();
-                String y = ctx.callActivity("Capitalize", x, String.class).await();
-                String z = ctx.callActivity("ReplaceWhitespace", y, String.class).await();
-                ctx.complete(z);
-            };
-        }
-    })
-    .addActivity(new TaskActivityFactory() {
-        @Override
-        public String getName() { return "Reverse"; }
-
-        @Override
-        public TaskActivity create() {
-            return ctx -> {
-                String input = ctx.getInput(String.class);
-                StringBuilder builder = new StringBuilder(input);
-                builder.reverse();
-                return builder.toString();
-            };
-        }
-    })
-    .addActivity(new TaskActivityFactory() {
-        @Override
-        public String getName() { return "Capitalize"; }
-
-        @Override
-        public TaskActivity create() {
-            return ctx -> ctx.getInput(String.class).toUpperCase();
-        }
-    })
-    .addActivity(new TaskActivityFactory() {
-        @Override
-        public String getName() { return "ReplaceWhitespace"; }
-
-        @Override
-        public TaskActivity create() {
-            return ctx -> {
-                String input = ctx.getInput(String.class);
-                return input.trim().replaceAll("\\s", "-");
-            };
-        }
-    })
-    .build();
-
-// Start the worker
-worker.start();
-```
-
 ::: zone-end
 
 ## Next steps