Add Durable Task Scheduler skill by greenie-msft · Pull Request #919 · microsoft/GitHub-Copilot-for-Azure

greenie-msft · 2026-02-13T18:14:35Z

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 · 2026-02-13T18:18:55Z

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

+# Start the emulator
+docker pull mcr.microsoft.com/dts/dts-emulator:latest
+docker run -d -p 8080:8080 -p 8082:8082 --name dts-emulator mcr.microsoft.com/dts/dts-emulator:latest


The emulator instructions use the :latest image tag, which makes the setup non-reproducible and can break as the image changes over time. Consider pinning to a specific emulator version tag (and optionally note how to discover newer versions) so local dev matches CI/troubleshooting guidance.

Suggested change

# Start the emulator

docker pull mcr.microsoft.com/dts/dts-emulator:latest

docker run -d -p 8080:8080 -p 8082:8082 --name dts-emulator mcr.microsoft.com/dts/dts-emulator:latest

# Start the emulator (update the tag as needed; see DTS emulator image tags in MCR for newer versions)

docker pull mcr.microsoft.com/dts/dts-emulator:1.0.0

docker run -d -p 8080:8080 -p 8082:8082 --name dts-emulator mcr.microsoft.com/dts/dts-emulator:1.0.0

Copilot · 2026-02-13T18:18:55Z

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

+  <PackageReference Include="Microsoft.Azure.Functions.Worker.Extensions.DurableTask" Version="1.*" />
+  <PackageReference Include="Microsoft.Azure.Functions.Worker.Extensions.DurableTask.AzureManaged" Version="*" />
+  <PackageReference Include="Azure.Identity" Version="1.*" />


PackageReference Version="*" can resolve to unexpected versions (including potentially breaking updates) and makes the guidance non-reproducible. Prefer an explicit version (or at least a bounded floating version like x.*) and/or add a note to check official docs for the current recommended version.

Suggested change

<PackageReference Include="Microsoft.Azure.Functions.Worker.Extensions.DurableTask" Version="1.*" />

<PackageReference Include="Microsoft.Azure.Functions.Worker.Extensions.DurableTask.AzureManaged" Version="*" />

<PackageReference Include="Azure.Identity" Version="1.*" />

<PackageReference Include="Microsoft.Azure.Functions.Worker.Extensions.DurableTask" Version="1.1.2" />

<PackageReference Include="Microsoft.Azure.Functions.Worker.Extensions.DurableTask.AzureManaged" Version="1.0.0" />

<PackageReference Include="Azure.Identity" Version="1.11.4" />

Copilot · 2026-02-13T18:18:55Z

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

+| Local Emulator | `Endpoint=http://localhost:8080;Authentication=None` |
+| Azure (Managed Identity) | `Endpoint=https://<scheduler>.durabletask.io;Authentication=ManagedIdentity` |
+
+> **⚠️ NOTE**: Durable Task Scheduler uses identity-based authentication only — no connection strings with keys.


The note says Durable Task Scheduler uses identity-based auth only, but the table includes Authentication=None for the local emulator and the rest of the doc uses an endpoint-style connection string setting. Suggest rewording to clarify this is about Azure-hosted schedulers (no shared keys), while the emulator can run without auth.

Suggested change

> **⚠️ NOTE**: Durable Task Scheduler uses identity-based authentication only — no connection strings with keys.

> **⚠️ NOTE**: Azure-hosted Durable Task Scheduler instances use identity-based authentication only (no shared-key connection strings). The local emulator can run without authentication (`Authentication=None`).

Copilot · 2026-02-13T18:18:56Z

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

+{
+    [Function("HttpStart")]
+    public static async Task<HttpResponseData> HttpStart(
+        [HttpTrigger(AuthorizationLevel.Anonymous, "post")] HttpRequestData req,


Both minimal HTTP starter examples are configured as anonymous (AuthorizationLevel.Anonymous / AuthLevel.ANONYMOUS). Since this reference also covers Azure deployment guidance, add a clear note (or adjust the sample) to avoid encouraging anonymous endpoints in production (e.g., use Function auth or Entra ID).

Suggested change

[HttpTrigger(AuthorizationLevel.Anonymous, "post")] HttpRequestData req,

[HttpTrigger(AuthorizationLevel.Function, "post")] HttpRequestData req,

tmeschter · 2026-02-13T19:05:30Z

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

@@ -0,0 +1,466 @@
+# Durable Task Scheduler


This file needs to be referenced somewhere or else it will never be used by the language model. That is, there needs to be some chain of Markdown references that starts from plugin/skills/azure-prepare/SKILL.md and leads to this file.

tmeschter · 2026-02-13T19:07:31Z

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

+    asyncio.run(main())
+```
+
+## Azure Deployment


Consider putting deployment details under the azure-deploy skill.

Copilot

Pull request overview

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

Copilot · 2026-02-13T23:30:13Z

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

+
+```bicep
+@allowed(['consumption', 'dedicated'])
+@description('Use consumption for QuickStarts/variable workloads, dedicated for high-demand/predictable throughput')


The term "QuickStarts" appears to use non-standard capitalization. Consider using "quick starts" (lowercase, two words) or "quickstarts" (one word, lowercase) for consistency with common documentation style, unless "QuickStarts" is an official Azure terminology.

Copilot · 2026-02-13T23:30:13Z

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

+resource uami 'Microsoft.ManagedIdentity/userAssignedIdentities@2023-01-31' = {
+  name: '<uami-name>'
+  location: location
+}
+
+// 2. Assign the UAMI to the Function App
+// (include in functionApp resource properties)
+// identity: {
+//   type: 'UserAssigned'
+//   userAssignedIdentities: { '${uami.id}': {} }
+// }
+
+// 3. Assign Durable Task Data Contributor to the UAMI
+resource durableTaskUamiRoleAssignment 'Microsoft.Authorization/roleAssignments@2022-04-01' = {
+  name: guid(scheduler.id, uami.id, durableTaskDataContributorRoleId)
+  scope: scheduler
+  properties: {
+    roleDefinitionId: subscriptionResourceId('Microsoft.Authorization/roleDefinitions', durableTaskDataContributorRoleId)
+    principalId: uami.properties.principalId
+    principalType: 'ServicePrincipal'
+  }
+}
+


The Bicep example shows both Option A (System-Assigned MI) and Option B (User-Assigned MI) as active resources that would both deploy if copied. The resource durableTaskRoleAssignment at line 465 should likely be commented out when using Option B, or vice versa, to avoid deploying both options simultaneously. Consider either:

Making Option A a complete commented example, or

Adding a conditional parameter to deploy only one based on user choice

This would prevent users from accidentally deploying both managed identity configurations when they likely only need one.

Suggested change

resource uami 'Microsoft.ManagedIdentity/userAssignedIdentities@2023-01-31' = {

name: '<uami-name>'

location: location

}

// 2. Assign the UAMI to the Function App

// (include in functionApp resource properties)

// identity: {

// type: 'UserAssigned'

// userAssignedIdentities: { '${uami.id}': {} }

// }

// 3. Assign Durable Task Data Contributor to the UAMI

resource durableTaskUamiRoleAssignment 'Microsoft.Authorization/roleAssignments@2022-04-01' = {

name: guid(scheduler.id, uami.id, durableTaskDataContributorRoleId)

scope: scheduler

properties: {

roleDefinitionId: subscriptionResourceId('Microsoft.Authorization/roleDefinitions', durableTaskDataContributorRoleId)

principalId: uami.properties.principalId

principalType: 'ServicePrincipal'

}

}

// OPTION B: User-Assigned Managed Identity (UAMI)

// Uncomment this block and comment out the System-Assigned MI example above

// if you prefer to use a user-assigned managed identity.

//

// resource uami 'Microsoft.ManagedIdentity/userAssignedIdentities@2023-01-31' = {

// name: '<uami-name>'

// location: location

// }

//

// // 2. Assign the UAMI to the Function App

// // (include in functionApp resource properties)

// // identity: {

// // type: 'UserAssigned'

// // userAssignedIdentities: { '${uami.id}': {} }

// // }

//

// // 3. Assign Durable Task Data Contributor to the UAMI

// resource durableTaskUamiRoleAssignment 'Microsoft.Authorization/roleAssignments@2022-04-01' = {

// name: guid(scheduler.id, uami.id, durableTaskDataContributorRoleId)

// scope: scheduler

// properties: {

// roleDefinitionId: subscriptionResourceId('Microsoft.Authorization/roleDefinitions', durableTaskDataContributorRoleId)

// principalId: uami.properties.principalId

// principalType: 'ServicePrincipal'

// }

// }

Copilot · 2026-02-13T23:30:13Z

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

+
+| SKU | Best For |
+|-----|----------|
+| **Consumption** | QuickStarts, variable or bursty workloads, pay-per-use |


The term "QuickStarts" appears to use non-standard capitalization. Consider using "quick starts" (lowercase, two words) or "quickstarts" (one word, lowercase) for consistency with common documentation style, unless "QuickStarts" is an official Azure terminology.

Suggested change

| **Consumption** | QuickStarts, variable or bursty workloads, pay-per-use |

| **Consumption** | quickstarts, variable or bursty workloads, pay-per-use |

Add Durable Task Scheduler skill

a01ec18

Copilot AI review requested due to automatic review settings February 13, 2026 18:14

Copilot started reviewing on behalf of greenie-msft February 13, 2026 18:15 View session

Copilot AI reviewed Feb 13, 2026

View reviewed changes

tmeschter reviewed Feb 13, 2026

View reviewed changes

tmeschter requested changes Feb 13, 2026

View reviewed changes

greenie-msft added 2 commits February 13, 2026 14:52

Update DTS skill to include RBAC guidance and SKU guidance

fb4f0d3

Add DTS to architecture guidance table for workflow

d3c243a

Copilot AI review requested due to automatic review settings February 13, 2026 23:25

Copilot started reviewing on behalf of greenie-msft February 13, 2026 23:25 View session

Copilot AI reviewed Feb 13, 2026

View reviewed changes

kvenkatrajan added the pending-owner-action label Feb 18, 2026

This was referenced Feb 20, 2026

[repo-status] Weekly Repo Status — Feb 14–20, 2026 #984

Closed

[repo-status] Weekly Repo Status — Feb 14–20, 2026 #989

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Comments

Add Durable Task Scheduler skill#919

Add Durable Task Scheduler skill#919
greenie-msft wants to merge 3 commits intomicrosoft:mainfrom
greenie-msft:add-dts-skill

greenie-msft commented Feb 13, 2026

Uh oh!

Copilot AI left a comment

Uh oh!

Copilot AI Feb 13, 2026

Uh oh!

Copilot AI Feb 13, 2026

Uh oh!

Copilot AI Feb 13, 2026

Uh oh!

Copilot AI Feb 13, 2026

Uh oh!

tmeschter Feb 13, 2026

Uh oh!

tmeschter Feb 13, 2026

Uh oh!

Copilot AI left a comment

Uh oh!

Copilot AI Feb 13, 2026

Uh oh!

Copilot AI Feb 13, 2026

Uh oh!

Copilot AI Feb 13, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

	> ⚠️ NOTE: Durable Task Scheduler uses identity-based authentication only — no connection strings with keys.
	> ⚠️ NOTE: Azure-hosted Durable Task Scheduler instances use identity-based authentication only (no shared-key connection strings). The local emulator can run without authentication (`Authentication=None`).

	[HttpTrigger(AuthorizationLevel.Anonymous, "post")] HttpRequestData req,
	[HttpTrigger(AuthorizationLevel.Function, "post")] HttpRequestData req,

-resource uami 'Microsoft.ManagedIdentity/userAssignedIdentities@2023-01-31' = {
-  name: '<uami-name>'
-  location: location
-}
-// 2. Assign the UAMI to the Function App
-// (include in functionApp resource properties)
-// identity: {
-//   type: 'UserAssigned'
-//   userAssignedIdentities: { '${uami.id}': {} }
-// }
-// 3. Assign Durable Task Data Contributor to the UAMI
-resource durableTaskUamiRoleAssignment 'Microsoft.Authorization/roleAssignments@2022-04-01' = {
-  name: guid(scheduler.id, uami.id, durableTaskDataContributorRoleId)
-  scope: scheduler
-  properties: {
-    roleDefinitionId: subscriptionResourceId('Microsoft.Authorization/roleDefinitions', durableTaskDataContributorRoleId)
-    principalId: uami.properties.principalId
-    principalType: 'ServicePrincipal'
-  }
-}
+// OPTION B: User-Assigned Managed Identity (UAMI)
+// Uncomment this block and comment out the System-Assigned MI example above
+// if you prefer to use a user-assigned managed identity.
+//
+// resource uami 'Microsoft.ManagedIdentity/userAssignedIdentities@2023-01-31' = {
+//   name: '<uami-name>'
+//   location: location
+// }
+//
+// // 2. Assign the UAMI to the Function App
+// // (include in functionApp resource properties)
+// // identity: {
+// //   type: 'UserAssigned'
+// //   userAssignedIdentities: { '${uami.id}': {} }
+// // }
+//
+// // 3. Assign Durable Task Data Contributor to the UAMI
+// resource durableTaskUamiRoleAssignment 'Microsoft.Authorization/roleAssignments@2022-04-01' = {
+//   name: guid(scheduler.id, uami.id, durableTaskDataContributorRoleId)
+//   scope: scheduler
+//   properties: {
+//     roleDefinitionId: subscriptionResourceId('Microsoft.Authorization/roleDefinitions', durableTaskDataContributorRoleId)
+//     principalId: uami.properties.principalId
+//     principalType: 'ServicePrincipal'
+//   }
+// }

	\| Consumption \| QuickStarts, variable or bursty workloads, pay-per-use \|
	\| Consumption \| quickstarts, variable or bursty workloads, pay-per-use \|

Comments

Conversation

greenie-msft commented Feb 13, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

tmeschter Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

tmeschter Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants