Add Durable Task Scheduler skill

[greenie-msft]

Adds a new reference skill for the Durable Task Scheduler enabling Copilot to guide users through building reliable, fault-tolerant workflows on Azure.

The skill covers:

Framework selection (Durable Functions vs. Durable Task SDKs)
Local development with the DTS emulator
Workflow patterns: chaining, fan-out/fan-in, async HTTP, monitor, human interaction, and saga
Orchestration determinism rules and replay-safe logging
Azure deployment with Bicep and managed identity configuration
Error handling and retry policies

[Copilot]

Pull request overview

Adds a new Azure Prepare reference document for Durable Task Scheduler (DTS) to help guide users in building durable, fault-tolerant workflow orchestrations on Azure.

Changes:

• Introduces a new durable-task-scheduler.md reference covering DTS fundamentals, local emulator setup, workflow patterns, and determinism rules.
• Includes example snippets for .NET and Python (starter, patterns, logging, retry).
• Adds Azure provisioning guidance including CLI, Bicep, and managed identity role assignment.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

[Copilot]

Pull request overview

Copilot reviewed 5 out of 5 changed files in this pull request and generated 4 comments.

Comments suppressed due to low confidence (3)

plugin/skills/azure-deploy/references/recipes/azd/durable-task-scheduler-deploy.md:19

• Callout formatting here (> **💡 TIP**:) is inconsistent with other AZD recipe docs in this repo (e.g., > 💡 **Note:**, > 💡 **Tip:**, > ⚠️ **Important:**). Consider switching to the same callout style for consistency and easier scanning.

> **💡 TIP**: Start with `consumption` for development and variable workloads. Switch to `dedicated` when you need consistent, high-throughput performance.

plugin/skills/azure-deploy/references/recipes/azd/durable-task-scheduler-deploy.md:109

• The RBAC scope example uses <sub-id>/myRG style placeholders, which differs from placeholder conventions used in other Azure CLI snippets in this repo (e.g., SUB, RG, PRINCIPAL_ID). Standardizing the placeholders (and using a consistent style throughout this doc) will make the instructions easier to apply.

# Grant access to scheduler
az role assignment create \
    --assignee $PRINCIPAL_ID \
    --role "Durable Task Data Contributor" \
    --scope /subscriptions/<sub-id>/resourceGroups/myRG/providers/Microsoft.DurableTask/schedulers/my-scheduler

plugin/skills/azure-prepare/references/services/durable-task-scheduler.md:24

• Callout formatting (> **💡 TIP**: / > **⚠️ NOTE**:) is inconsistent with the common style used across the repo’s references (> 💡 **Tip:**, > ⚠️ **Important:**, etc.). Consider normalizing these callouts for consistency and to avoid multiple variants of the same pattern.

> **💡 TIP**: Use Durable Functions for serverless with built-in triggers. Use Durable Task SDKs for hosting flexibility.

[Copilot]

Pull request overview

Copilot reviewed 5 out of 5 changed files in this pull request and generated no new comments.

[Copilot]

Pull request overview

Copilot reviewed 11 out of 11 changed files in this pull request and generated 5 comments.

[Copilot]

Pull request overview

Copilot reviewed 19 out of 19 changed files in this pull request and generated 4 comments.

[paulyuk]

Touches a number of files but I think we need to because this is a new scenario for orchestration that can be used with all the host app compute services. The changes are correct and look safe.

[Copilot]

Pull request overview

Copilot reviewed 19 out of 19 changed files in this pull request and generated 2 comments.

Comments suppressed due to low confidence (1)

plugin/skills/azure-prepare/references/services/durable-task-scheduler/bicep.md:95

• The connection string example orders fields differently than other DTS docs in this PR and the durable-task-scheduler Bicep module output. Since these strings are meant to be copy/paste templates, align the field order across docs (and ideally match the module output) to avoid confusion when troubleshooting.

{
  name: 'DURABLE_TASK_SCHEDULER_CONNECTION_STRING'
  value: 'Endpoint=${scheduler.properties.endpoint};TaskHub=${taskHub.name};Authentication=ManagedIdentity;ClientID=${uamiClientId}'
}