azure-resource-manager-cosmosdb-dotnet
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.
Stop for confirmation before installing.
Review the plan and obtain explicit user consent before changing files.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "azure-resource-manager-cosmosdb-dotnet" from https://skillstore.io/skills/sickn33-azure-resource-manager-cosmosdb-dotnet.md and its manifest at https://skillstore.io/api/skills/sickn33-azure-resource-manager-cosmosdb-dotnet/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.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-cosmosdb-dotnet". Plan a development account with one SQL database and one container using autoscale.
Expected outcome:
- Use DefaultAzureCredential with a subscription-scoped ARM client.
- Create the account in the selected resource group and wait for completion.
- Create the SQL database, then add a container with a validated partition key.
- Apply autoscale throughput after confirming the expected workload range.
Using "azure-resource-manager-cosmosdb-dotnet". Review my approach for retrieving connection information.
Expected outcome:
Retrieve credentials only when required and never print them. Prefer managed identity, restricted access, and direct storage in Azure Key Vault.
Using "azure-resource-manager-cosmosdb-dotnet". Explain when to use this SDK instead of Microsoft.Azure.Cosmos.
Expected outcome:
Use Azure.ResourceManager.CosmosDB for accounts, databases, containers, throughput, networking, and RBAC. Use Microsoft.Azure.Cosmos for documents, queries, and data operations.
Security Audit
High RiskAll 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.
Confirmed security concerns (1)
Risk Factors
⚙️ External commands (37)
🔑 Env variables (3)
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-cosmosdb-dotnet/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-azure-resource-manager-cosmosdb-dotnet?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-azure-resource-manager-cosmosdb-dotnet?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-azure-resource-manager-cosmosdb-dotnet/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-azure-resource-manager-cosmosdb-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-cosmosdb-dotnet security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-azure-resource-manager-cosmosdb-dotnet/audits/5BibTeX citation
@techreport{sickn33-sickn33-azure-resource-manager-cosmosdb-dotnet-2026,
author = {sickn33},
title = {azure-resource-manager-cosmosdb-dotnet security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-azure-resource-manager-cosmosdb-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-cosmosdb-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-cosmosdb-dotnet/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-azure-resource-manager-cosmosdb-dotnet:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
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.
Try These Prompts
List the packages and setup steps for managing Azure Cosmos DB resources from a .NET project. Use DefaultAzureCredential.
Design a .NET workflow that creates a Cosmos DB account, SQL database, and container in my existing resource group.
Propose container settings for partition key {path}, time to live {seconds}, and autoscale maximum {RU}. Explain each decision.Review my Cosmos DB management workflow for least privilege, idempotency, error handling, secret exposure, and long-running operation behavior.
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.
Avoid
- 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.