# Manage Azure Cosmos DB Resources with .NET

Provisioning Cosmos DB resources through Azure Resource Manager requires correct SDK types, credentials, and operation handling. This skill provides focused .NET patterns for common management tasks.

## Install

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

## Metadata

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

## Capabilities

- Identifies the NuGet packages required for Azure Cosmos DB management workflows.
- Shows Azure authentication with DefaultAzureCredential and an ARM subscription resource.
- Demonstrates account, SQL database, and SQL container provisioning with asynchronous ARM operations.
- Configures partition keys, indexing, time to live, manual throughput, and autoscale throughput.
- Explains resource hierarchy, key SDK types, and RequestFailedException handling.

## Use Cases

- Provision a Development Environment: Create a Cosmos DB account, SQL database, and container for a .NET development environment.
- Standardize Platform Provisioning: Draft repeatable ARM SDK workflows with consistent throughput, indexing, and resource naming.
- Review Cosmos DB Management Code: Check authentication, long-running operations, exception handling, and management plane boundaries.

## Prompt Templates

### Install the Management SDK

```
List the packages and setup steps for managing Azure Cosmos DB resources from a .NET project. Use DefaultAzureCredential.
```

### Create a Cosmos DB Resource Hierarchy

```
Design a .NET workflow that creates a Cosmos DB account, SQL database, and container in my existing resource group.
```

### Configure Container and Throughput

```
Propose container settings for partition key {path}, time to live {seconds}, and autoscale maximum {RU}. Explain each decision.
```

### Harden an ARM Provisioning Workflow

```
Review my Cosmos DB management workflow for least privilege, idempotency, error handling, secret exposure, and long-running operation behavior.
```

## Limitations

- Covers management plane resources, not document operations, queries, or stored procedure execution.
- Examples require an Azure subscription, an existing resource group, valid credentials, and sufficient RBAC permissions.
- Package versions and generated SDK types can change after the skill is published.
- The connection information example prints secrets and requires security changes before production use.

## Best Practices

- Use DefaultAzureCredential with least-privilege Azure RBAC assignments.
- Validate names, regions, partition keys, and throughput settings before provisioning.
- Keep account keys and connection strings out of logs, prompts, and terminal output.

## Anti Patterns

- Do not use the management SDK for document queries or item operations.
- Do not print master keys, connection strings, client secrets, or other credentials.
- Do not start dependent operations before required ARM operations complete.

## Security Audit

- Audited at: 2026-07-23T22:15:11.97\+00:00
- Summary: All command detections are Markdown fences or inline code, and the environment variable detections are placeholder setup examples. However, the skill demonstrates printing account keys and connection strings, which can expose secrets through logs or terminal history.

## Stats

- Views: 87
- Downloads: 8
- Favorites: 0
- Popularity score: 0