Skills azure-resource-manager-durabletask-dotnet
📦
azure-resource-manager-durabletask-dotnet
Content revision r2 Safe ⚙️ External commands🌐 Network access🔑 Env variables
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.
Supports: Claude Codex Code(CC)
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "azure-resource-manager-durabletask-dotnet" from https://skillstore.io/skills/sickn33-azure-resource-manager-durabletask-dotnet.md and its manifest at https://skillstore.io/api/skills/sickn33-azure-resource-manager-durabletask-dotnet/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "azure-resource-manager-durabletask-dotnet". Choose a scheduler SKU for a development workload with variable traffic.
Expected outcome:
- Recommendation: Consumption SKU for variable development traffic.
- Reason: It avoids fixed capacity management and scales automatically.
- Validation: Confirm regional availability, quotas, and current Azure pricing before deployment.
Using "azure-resource-manager-durabletask-dotnet". Outline a safe plan to create a Dedicated scheduler and one task hub.
Expected outcome:
- Plan: Authenticate, select the subscription and resource group, then create the scheduler with an idempotent operation.
- Dependencies: Azure.ResourceManager.DurableTask and Azure.Identity.
- Checks: Verify RBAC, location support, naming, IP allowlist, and operation completion.
Using "azure-resource-manager-durabletask-dotnet". Explain how to investigate an ARM conflict during an update.
Expected outcome:
- Diagnosis: The scheduler name may already exist, or another operation may still be updating it.
- Next actions: Fetch the current resource, compare desired settings, and use idempotent update logic.
Security Audit
Safev5 • 7/23/2026 Open versioned report
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.
1
Files scanned
387
Lines analyzed
0
Review items
0
False positives ignored
Risk Factors
⚙️ External commands (50)
SKILL.md:19-22 SKILL.md:22-29 SKILL.md:29-36 SKILL.md:36-40 SKILL.md:40-53 SKILL.md:53-57 SKILL.md:57-64 SKILL.md:64-70 SKILL.md:70-102 SKILL.md:102-106 SKILL.md:106-121 SKILL.md:121-125 SKILL.md:125-140 SKILL.md:140-144 SKILL.md:144-160 SKILL.md:160-164 SKILL.md:164-176 SKILL.md:176-180 SKILL.md:180-201 SKILL.md:201-205 SKILL.md:205-212 SKILL.md:212-216 SKILL.md:216-233 SKILL.md:233-239 SKILL.md:239-240 SKILL.md:240-241 SKILL.md:241-242 SKILL.md:242-243 SKILL.md:243-244 SKILL.md:244-245 SKILL.md:245 SKILL.md:246-247 SKILL.md:247-248 SKILL.md:248-249 SKILL.md:249-250 SKILL.md:250-251 SKILL.md:251-257 SKILL.md:257-258 SKILL.md:258-262 SKILL.md:262 SKILL.md:264-276 SKILL.md:276-280 SKILL.md:280-281 SKILL.md:281-282 SKILL.md:282-283 SKILL.md:283-284 SKILL.md:284-290 SKILL.md:290-310 SKILL.md:310-314 SKILL.md:314-363
🌐 Network access (4)
🔑 Env variables (3)
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-azure-resource-manager-durabletask-dotnet/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-azure-resource-manager-durabletask-dotnet?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-azure-resource-manager-durabletask-dotnet?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-azure-resource-manager-durabletask-dotnet/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-azure-resource-manager-durabletask-dotnet.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). azure-resource-manager-durabletask-dotnet security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-azure-resource-manager-durabletask-dotnet/audits/5BibTeX citation
@techreport{sickn33-sickn33-azure-resource-manager-durabletask-dotnet-2026,
author = {sickn33},
title = {azure-resource-manager-durabletask-dotnet security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-azure-resource-manager-durabletask-dotnet/audits/5},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "azure-resource-manager-durabletask-dotnet security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/sickn33-azure-resource-manager-durabletask-dotnet/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-azure-resource-manager-durabletask-dotnet:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: High 55
Architecture
85
Maintainability
87
Content
68
Community
83
Spec Compliance
What You Can Build
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.
Try These Prompts
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.
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.
Avoid
- 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.
Frequently Asked Questions
Does this skill execute Azure changes?
No. It provides guidance and examples. Running generated code with authorized Azure credentials can create, update, or delete resources.
Can it start Durable Task orchestrations?
No. Use the Azure Managed Durable Task client and worker packages for data plane orchestration operations.
Which authentication approach does it recommend?
It recommends DefaultAzureCredential, which supports local development and managed Azure identities without hardcoded credentials.
How should I choose a scheduler SKU?
Use Dedicated for predictable capacity needs. Consider Consumption for variable workloads, after checking availability, quotas, and pricing.
What should I verify before deleting a scheduler?
Confirm the subscription, resource group, scheduler name, environment, and dependent task hubs. Ensure recovery or recreation procedures are available.
Are the documented package versions guaranteed to be current?
No. Verify package versions, API support, regional availability, and release notes before implementing the examples.