# Manage Azure Durable Task Resources with .NET

Provisioning Durable Task Scheduler resources through Azure Resource Manager requires precise SDK patterns. This skill provides focused .NET guidance for schedulers, task hubs, retention, updates, and cleanup.

## Install

```bash
npx skillstore add sickn33/azure-resource-manager-durabletask-dotnet
```

## Metadata

- Status: approved
- Slug: sickn33-azure-resource-manager-durabletask-dotnet
- Skillstore revision: r2
- Version status: missing
- Tree hash: d92cbffe87244782b5ba72f0752ef48128f93b983d4f07cb675a208e394e365c
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/azure-resource-manager-durabletask-dotnet
- Ref: f9e2c34b4f19c7f3e6b0a1e93227b5f77cc12526
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, env\_access
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/sickn33-azure-resource-manager-durabletask-dotnet
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-azure-resource-manager-durabletask-dotnet/manifest

## Capabilities

- Explains package installation and ARM client authentication with DefaultAzureCredential.
- Shows how to create Dedicated and Consumption schedulers with idempotent operations.
- Demonstrates task hub creation and retention policy management.
- Covers listing, retrieving, updating, and deleting scheduler resources.
- Provides patterns for long-running operations and common ARM API failures.
- Distinguishes management plane resources from data plane orchestration packages.

## Use Cases

- Provision a scheduler: Create a Durable Task Scheduler and task hub with suitable location, SKU, capacity, and network settings.
- Build management tooling: Add typed C\# workflows for listing, retrieving, updating, and deleting Durable Task resources.
- Standardize resource operations: Define reliable deployment and cleanup procedures with idempotent calls, completion waits, and ARM error handling.

## Prompt Templates

### Set up authentication

```
Show how to install the required .NET packages and authenticate an ArmClient with DefaultAzureCredential. Use placeholders for subscription and resource group values.
```

### Create a scheduler

```
Create a C# example for a [Dedicated or Consumption] Durable Task Scheduler in [region]. Include a task hub and explain each required setting.
```

### Manage the lifecycle

```
Design an idempotent C# workflow that finds, updates, lists, and safely deletes a scheduler named [name]. Handle long-running operations and common ARM errors.
```

### Design production provisioning

```
Review these workload requirements: [requirements]. Recommend SKU, capacity, IP allowlist, retention, error handling, validation, and cleanup steps for a production-ready management workflow.
```

## Limitations

- It does not start orchestrations, query instances, or run Durable Task workers.
- Examples require valid Azure subscriptions, resource groups, RBAC permissions, and environment-specific settings.
- It does not deploy, execute, or validate generated workflows automatically.
- Package versions and Azure API behavior may change after the documented release.

## Best Practices

- Use DefaultAzureCredential and grant only the Azure roles required for each management operation.
- Use idempotent operations and wait explicitly when later steps depend on completion.
- Validate names, regions, quotas, allowlists, and deletion targets before changing live resources.

## Anti Patterns

- Do not hardcode Azure credentials, subscription identifiers, or production resource names.
- Do not use the management SDK for orchestration and worker data plane operations.
- Do not delete schedulers before confirming dependent task hubs and the intended environment.

## Security Audit

- Audited at: 2026-07-23T22:18:40.645\+00:00
- Summary: All 63 static findings are false positives caused by Markdown syntax, private example CIDRs, official reference links, and placeholder Azure variables. SKILL.md contains documentation and C\# examples, with no executable script, automatic network request, or real secret. No prompt injection, exfiltration intent, or other semantic security issue was found.

## Stats

- Views: 81
- Downloads: 10
- Favorites: 0
- Popularity score: 0