Secure, optimize, and deploy Azure Cosmos DB solutions
At a glance
-
Level
-
Skill
-
Product
-
Role
-
Subject
This learning path builds the skills to operate Azure Cosmos DB for NoSQL in production. It starts with the security surface: authenticating with Microsoft Entra ID instead of account keys, separating control-plane from data-plane permissions, restricting network access, and masking sensitive values in query results.
From there you protect the data and keep it available. You choose between periodic and continuous backup, recover from a mistake with a point-in-time restore, and design a multi-region topology, including the four failover mechanisms and the rules that decide which one you can run during an outage.
The middle of the path is performance. You design an indexing policy for the queries an application actually runs, then measure what those queries cost and reduce it, reading server-side metrics and index utilization rather than guessing. Monitoring follows: interpreting response codes and the four distinct causes of a 429, tracking latency against a service-level objective, and alerting on the signals that predict a problem.
The path closes at fleet scale, where you manage throughput and analytics across many Azure Cosmos DB accounts from one place instead of account by account.
Prerequisites
- Completion of the Design and develop Azure Cosmos DB database solutions learning path, or equivalent experience building applications on Azure Cosmos DB for NoSQL
- Basic knowledge of Azure identities, role assignments, and virtual networking
- Basic familiarity with the Azure CLI, Azure Monitor, and the Azure portal
Achievement Code
Would you like to request an achievement code?
Modules in this learning path
Secure an Azure Cosmos DB account by configuring Microsoft Entra and key-based authentication, role-based access control across the control and data planes, network isolation, and dynamic data masking.
Choose between periodic and continuous backup for an Azure Cosmos DB account, enable continuous backup, recover data to a point in time, and describe vaulted backup for long-term retention.
Add regions to an Azure Cosmos DB account, route reads and writes to the closest region from the SDK, resolve conflicts between write regions, and choose the failover behavior that matches your recovery objectives.
Fit an Azure Cosmos DB for NoSQL indexing policy to its workload, add the composite, spatial, and computed-property indexes that specific query shapes need, and use global secondary indexes to turn cross-partition queries into single-partition ones.
Diagnose an expensive Azure Cosmos DB for NoSQL query from the metrics it returns, distinguish a scan from a fan-out, and apply the remediation the evidence points to instead of raising throughput.
Diagnose an Azure Cosmos DB for NoSQL incident from the evidence the service already produces, and put alerts in place so the next one announces itself before your users do.
Run a multitenant Azure Cosmos DB estate as one unit. Group accounts into a fleet, share throughput with a pool instead of provisioning every tenant for its peak, and answer estate-wide usage and cost questions from a single dataset.