Switch DTS Bicep templates from Dedicated to Consumption SKU

[Copilot]

All sample Bicep deployments currently use the Dedicated SKU for Azure Durable Task Scheduler, which is slow to provision and expensive for evaluation/quickstart scenarios.

Changes

DTS module templates (dts.bicep - 7 files)

• Conditional SKU object: omit capacity property for Consumption, include it for Dedicated
• Made skuCapacity parameter optional (default: 0)

sku: skuName == 'Dedicated' ? {
  name: skuName
  capacity: skuCapacity
} : {
  name: skuName
}

Main deployment templates (main.bicep - 7 files)

• Changed dtsSkuName default from 'Dedicated' to 'Consumption'

Affected samples

• samples/infra/
• samples/scenarios/AutoscalingInACA/
• All durable-functions samples (HelloCities, PdfSummarizer, OrderProcessor, AiAgentTravelPlanOrchestrator)
• Python pdf-summarizer

Backward Compatibility

Dedicated SKU remains available by overriding parameters:

dtsSkuName: 'Dedicated'
dtsCapacity: 3

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• aka.ms
  • Triggering command: /usr/local/bin/bicep bicep build dts.bicep (dns block)
  • Triggering command: /usr/local/bin/bicep bicep build dts.bicep --stdout (dns block)
• azcliprod.blob.core.windows.net
  • Triggering command: /usr/bin/../../opt/az/bin/python3 /usr/bin/../../opt/az/bin/python3 -Im azure.cli bicep build --file dts.bicep (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Samples deploy Durable Task Scheduler with Dedicated SKU; switch Bicep to Consumption</issue_title>
<issue_description>The samples in this repo currently deploy Azure Durable Task Scheduler (DTS) using the Dedicated SKU.

Dedicated is expensive and slow to deploy, which makes the samples painful for quickstarts and developer evaluation.

Expected behavior
All sample deployments should default to the Consumption SKU instead, because it is the appropriate choice for samples/quickstarts and is cheaper + faster to provision.

What to change
Update the Bicep templates that deploy Microsoft.DurableTask/schedulers to:

• Set the DTS SKU name to Consumption
• Do not set sku.capacity when using Consumption (capacity applies to Dedicated; Consumption has no capacity).

Per the resource schema, sku.name supports 'Consumption' | 'Dedicated', and sku.capacity is a scale/capacity setting that should not be used for Consumption. </issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Samples deploy Durable Task Scheduler with Dedicated SKU; switch Bicep to Consumption #138

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.