Provision and Manage Azure Cosmos DB Resources

This skill teaches an agent to use the Azure.ResourceManager.CosmosDB .NET SDK, the management-plane client for provisioning and managing Cosmos DB resources through Azure Resource Manager - as opposed to the Microsoft.Azure.Cosmos data-plane SDK, which does document CRUD and queries. Starting from an ArmClient, it walks a resource hierarchy (SubscriptionResource to ResourceGroupResource to CosmosDBAccountResource to CosmosDBSqlDatabaseResource to CosmosDBSqlContainerResource, plus Cassandra, Gremlin, MongoDB, and Table sub-resources) to create accounts, SQL databases, and SQL containers, configure manual or autoscale throughput, and retrieve account keys and connection strings.

Use it when provisioning or managing Cosmos DB infrastructure itself - creating accounts, databases, containers, partition and indexing configuration, throughput, failover, or retrieving keys and connection strings - as distinct from writing application code that reads and writes documents. For document-level CRUD, queries, or stored procedure execution, use the Microsoft.Azure.Cosmos data-plane SDK instead; this skill's SDK cannot do that. Its stated best practices: use CreateOrUpdateAsync for idempotent resource operations, navigate the hierarchy through Get* methods such as account.GetCosmosDBSqlDatabases(), always authenticate with DefaultAzureCredential rather than hardcoded keys, and catch RequestFailedException for ARM-level errors, for example treating a 409 status as "resource already exists" rather than a failure.

Inputs: AZURE_SUBSCRIPTION_ID (and, for service principal auth, AZURE_TENANT_ID, AZURE_CLIENT_ID, AZURE_CLIENT_SECRET), a DefaultAzureCredential, and per-resource creation payloads - CosmosDBAccountCreateOrUpdateContent (location, consistency policy, automatic failover), CosmosDBSqlDatabaseCreateOrUpdateContent, CosmosDBSqlContainerCreateOrUpdateContent (partition key paths and kind, indexing policy, TTL), and ThroughputSettingsUpdateData (manual Throughput or AutoscaleSettings.MaxThroughput). Outputs: long-running-operation results resolving to typed resources (CosmosDBAccountResource, CosmosDBSqlDatabaseResource, CosmosDBSqlContainerResource), account keys (PrimaryMasterKey) and connection strings, and RequestFailedExceptions carrying an ARM status and error code, for example 409 for an account that already exists.

Azure Resource Manager (via ArmClient), Azure Identity (DefaultAzureCredential), and Cosmos DB's multiple API surfaces at the resource level - SQL, Cassandra, Gremlin, MongoDB, and Table - each with their own resource types under the account. Reference material covers account management (CRUD, failover, keys, connection strings, networking), SQL resources (databases, containers, stored procedures, triggers, user-defined functions), and throughput, including migrating between manual and autoscale modes. WaitUntil.Completed blocks until a long-running operation finishes, while WaitUntil.Started allows manual polling or running operations in parallel.

dotnet add package Azure.ResourceManager.CosmosDB
dotnet add package Azure.Identity

.NET developers and platform engineers provisioning or managing Cosmos DB infrastructure as code - accounts, databases, containers, throughput, and access keys - who need the ARM management plane rather than the data-plane document SDK.