🛡️ Azure Cosmos DB Account MongoDB API version is below 4.2🟢

• Contextual name: 🛡️ Account MongoDB API version is below 4.2🟢
• ID: /ce/ca/azure/cosmos-db/mongodb-api-version-below-4-2
• Tags:
  • 🟢 Policy with categories
  • 🟢 Policy with type
  • 🟢 Production policy
• Policy Type: BEST_PRACTICE
• Policy Categories: COST, RELIABILITY

Stats

not available

Logic

• 🧠 prod.logic.yaml🟢
  • 📗 Azure Cosmos DB Account
  • 🔌 Azure Cosmos DB Account - object.extracts.yaml
  • 🧪 test-data.json

Description

Open File

Description

Ensure that Azure Cosmos DB accounts using the MongoDB API run server version 4.2 or a later Azure-supported version. The setting determines the account's MongoDB API storage format; it does not evaluate self-managed MongoDB servers or client drivers.

Rationale

Azure reports lower query and storage costs for the MongoDB API 4.2 storage format. Migrating an eligible workload can therefore reduce the cost of storing data and executing queries. This policy identifies a configuration opportunity; it does not calculate workload-specific savings.

Impact

The migration creates a new account and moves data; it is not a routine in-place configuration update. Applications that depend on version-specific behavior can fail or behave differently after cutover. Plan compatibility testing, data validation, downtime, rollback, and the temporary cost of running source and target accounts.

Audit

This policy evaluates the Kind and API Server Version properties of each Azure Cosmos DB Account.

• INCOMPLIANT: the account uses the MongoDB API and its server version is 3.2,

... see more

Remediation

Open File

Remediation

Treat this finding as a planned migration, not an in-place account update. The appropriate migration method depends on the application, data volume, availability requirements, and target account configuration.

Plan and execute the migration

1. Confirm the account uses MongoDB API version 3.2, 3.6, or 4.0 and identify the applications, drivers, queries, indexes, integrations, and data dependencies that use it.
2. Define an approved target version and create a separate Azure Cosmos DB account with equivalent network, backup, availability, encryption, monitoring, and access controls.
3. Migrate representative data and validate application behavior, data integrity, performance, and cost in a non-production environment.
4. Prepare a production cutover plan with an approved maintenance window, communications, monitoring, and a tested rollback procedure.
5. Migrate production data and cut over application traffic only after validation succeeds. Retain the source account until the rollback window closes.

... see more

policy.yaml

Open File

Linked Framework Sections

Section	Sub Sections	Internal Rules	Policies	Flags	Compliance
💼 Cloudaware Framework → 💼 Infrastructure Modernization			19		no data
💼 Cloudaware Framework → 💼 Resource Optimization			37		no data