@raishin/vanguard-frontier-agentic 3.19.0 → 3.20.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (459) hide show
  1. package/.claude-plugin/marketplace.json +2 -2
  2. package/.claude-plugin/plugin.json +8 -1
  3. package/.cursor-plugin/plugin.json +8 -1
  4. package/.github/plugin/marketplace.json +1 -1
  5. package/README.md +21 -21
  6. package/agents/AGENTS.md +4 -4
  7. package/agents/README.md +7 -7
  8. package/agents/alibaba/alibaba-tablestore-architect-agent/AGENT.md +54 -0
  9. package/agents/alibaba/alibaba-tablestore-architect-agent/harnesses/claude-code.agent.md +37 -0
  10. package/agents/alibaba/alibaba-tablestore-architect-agent/harnesses/codex.toml +11 -0
  11. package/agents/alibaba/alibaba-tablestore-architect-agent/harnesses/copilot.agent.md +43 -0
  12. package/agents/alibaba/alibaba-tablestore-architect-agent/harnesses/cursor.agent.md +38 -0
  13. package/agents/alibaba/alibaba-tablestore-architect-agent/harnesses/gemini.agent.md +39 -0
  14. package/agents/alibaba/alibaba-tablestore-architect-agent/harnesses/kiro-cli.agent.json +5 -0
  15. package/agents/alibaba/alibaba-tablestore-architect-agent/harnesses/kiro-ide.agent.md +37 -0
  16. package/agents/alibaba/alibaba-tablestore-architect-agent/metadata.json +39 -0
  17. package/agents/aws/aws-dynamodb-patterns-agent/AGENT.md +53 -0
  18. package/agents/aws/aws-dynamodb-patterns-agent/harnesses/claude-code.agent.md +36 -0
  19. package/agents/aws/aws-dynamodb-patterns-agent/harnesses/codex.toml +23 -0
  20. package/agents/aws/aws-dynamodb-patterns-agent/harnesses/copilot.agent.md +42 -0
  21. package/agents/aws/aws-dynamodb-patterns-agent/harnesses/cursor.agent.md +38 -0
  22. package/agents/aws/aws-dynamodb-patterns-agent/harnesses/gemini.agent.md +38 -0
  23. package/agents/aws/aws-dynamodb-patterns-agent/harnesses/kiro-cli.agent.json +5 -0
  24. package/agents/aws/aws-dynamodb-patterns-agent/harnesses/kiro-ide.agent.md +36 -0
  25. package/agents/aws/aws-dynamodb-patterns-agent/metadata.json +39 -0
  26. package/agents/azure/azure-cosmosdb-application-developer-agent/metadata.json +4 -0
  27. package/agents/azure/azure-cosmosdb-pattern-agent/AGENT.md +53 -0
  28. package/agents/azure/azure-cosmosdb-pattern-agent/harnesses/claude-code.agent.md +36 -0
  29. package/agents/azure/azure-cosmosdb-pattern-agent/harnesses/codex.toml +23 -0
  30. package/agents/azure/azure-cosmosdb-pattern-agent/harnesses/copilot.agent.md +42 -0
  31. package/agents/azure/azure-cosmosdb-pattern-agent/harnesses/cursor.agent.md +37 -0
  32. package/agents/azure/azure-cosmosdb-pattern-agent/harnesses/gemini.agent.md +38 -0
  33. package/agents/azure/azure-cosmosdb-pattern-agent/harnesses/kiro-cli.agent.json +5 -0
  34. package/agents/azure/azure-cosmosdb-pattern-agent/harnesses/kiro-ide.agent.md +36 -0
  35. package/agents/azure/azure-cosmosdb-pattern-agent/metadata.json +38 -0
  36. package/agents/gcp/gcp-bigtable-architect-agent/AGENT.md +54 -0
  37. package/agents/gcp/gcp-bigtable-architect-agent/harnesses/claude-code.agent.md +37 -0
  38. package/agents/gcp/gcp-bigtable-architect-agent/harnesses/codex.toml +11 -0
  39. package/agents/gcp/gcp-bigtable-architect-agent/harnesses/copilot.agent.md +43 -0
  40. package/agents/gcp/gcp-bigtable-architect-agent/harnesses/cursor.agent.md +38 -0
  41. package/agents/gcp/gcp-bigtable-architect-agent/harnesses/gemini.agent.md +39 -0
  42. package/agents/gcp/gcp-bigtable-architect-agent/harnesses/kiro-cli.agent.json +5 -0
  43. package/agents/gcp/gcp-bigtable-architect-agent/harnesses/kiro-ide.agent.md +37 -0
  44. package/agents/gcp/gcp-bigtable-architect-agent/metadata.json +39 -0
  45. package/agents/huawei/huawei-geminidb-architect-agent/AGENT.md +54 -0
  46. package/agents/huawei/huawei-geminidb-architect-agent/harnesses/claude-code.agent.md +37 -0
  47. package/agents/huawei/huawei-geminidb-architect-agent/harnesses/codex.toml +11 -0
  48. package/agents/huawei/huawei-geminidb-architect-agent/harnesses/copilot.agent.md +43 -0
  49. package/agents/huawei/huawei-geminidb-architect-agent/harnesses/cursor.agent.md +38 -0
  50. package/agents/huawei/huawei-geminidb-architect-agent/harnesses/gemini.agent.md +39 -0
  51. package/agents/huawei/huawei-geminidb-architect-agent/harnesses/kiro-cli.agent.json +5 -0
  52. package/agents/huawei/huawei-geminidb-architect-agent/harnesses/kiro-ide.agent.md +37 -0
  53. package/agents/huawei/huawei-geminidb-architect-agent/metadata.json +38 -0
  54. package/agents/oci/oci-nosql-database-architect-agent/AGENT.md +54 -0
  55. package/agents/oci/oci-nosql-database-architect-agent/harnesses/claude-code.agent.md +37 -0
  56. package/agents/oci/oci-nosql-database-architect-agent/harnesses/codex.toml +11 -0
  57. package/agents/oci/oci-nosql-database-architect-agent/harnesses/copilot.agent.md +43 -0
  58. package/agents/oci/oci-nosql-database-architect-agent/harnesses/cursor.agent.md +39 -0
  59. package/agents/oci/oci-nosql-database-architect-agent/harnesses/gemini.agent.md +39 -0
  60. package/agents/oci/oci-nosql-database-architect-agent/harnesses/kiro-cli.agent.json +5 -0
  61. package/agents/oci/oci-nosql-database-architect-agent/harnesses/kiro-ide.agent.md +37 -0
  62. package/agents/oci/oci-nosql-database-architect-agent/metadata.json +39 -0
  63. package/agents/oci/oci-nosql-pattern-agent/AGENT.md +53 -0
  64. package/agents/oci/oci-nosql-pattern-agent/harnesses/claude-code.agent.md +36 -0
  65. package/agents/oci/oci-nosql-pattern-agent/harnesses/codex.toml +23 -0
  66. package/agents/oci/oci-nosql-pattern-agent/harnesses/copilot.agent.md +42 -0
  67. package/agents/oci/oci-nosql-pattern-agent/harnesses/cursor.agent.md +38 -0
  68. package/agents/oci/oci-nosql-pattern-agent/harnesses/gemini.agent.md +38 -0
  69. package/agents/oci/oci-nosql-pattern-agent/harnesses/kiro-cli.agent.json +5 -0
  70. package/agents/oci/oci-nosql-pattern-agent/harnesses/kiro-ide.agent.md +36 -0
  71. package/agents/oci/oci-nosql-pattern-agent/metadata.json +38 -0
  72. package/catalog/agents.json +204 -1
  73. package/catalog/asset-integrity.json +601 -61
  74. package/catalog/install-roles.json +19 -1
  75. package/catalog/model-assignments.json +231 -0
  76. package/catalog/skill-manifest.json +1603 -56
  77. package/catalog/skills.json +314 -14
  78. package/package.json +7 -2
  79. package/plugins/vanguard-frontier-agentic/.codex-plugin/plugin.json +1 -1
  80. package/powers/vanguard-alibaba/POWER.md +1 -1
  81. package/powers/vanguard-aws/POWER.md +1 -1
  82. package/powers/vanguard-azure/POWER.md +1 -1
  83. package/powers/vanguard-gcp/POWER.md +1 -1
  84. package/powers/vanguard-huawei/POWER.md +1 -1
  85. package/powers/vanguard-oci/POWER.md +1 -1
  86. package/skills/alibaba/README.md +2 -1
  87. package/skills/alibaba/alibaba-maestro/SKILL.md +2 -1
  88. package/skills/alibaba/alibaba-tablestore-architect/SKILL.md +69 -0
  89. package/skills/alibaba/alibaba-tablestore-architect/metadata.json +28 -0
  90. package/skills/alibaba/alibaba-tablestore-architect/references/commands/audit/live.md +110 -0
  91. package/skills/alibaba/alibaba-tablestore-architect/references/commands/audit/offline.md +119 -0
  92. package/skills/alibaba/alibaba-tablestore-architect/references/commands/audit.md +22 -0
  93. package/skills/alibaba/alibaba-tablestore-architect/references/evidence-ledger.md +87 -0
  94. package/skills/alibaba/alibaba-tablestore-architect/references/operations.md +190 -0
  95. package/skills/alibaba/alibaba-tablestore-architect/references/tablestore-design-guide.md +159 -0
  96. package/skills/aws/aws-documentdb-architect/SKILL.md +43 -0
  97. package/skills/aws/aws-documentdb-architect/metadata.json +26 -0
  98. package/skills/aws/aws-documentdb-architect/references/commands/audit/live.md +135 -0
  99. package/skills/aws/aws-documentdb-architect/references/commands/audit/offline.md +127 -0
  100. package/skills/aws/aws-documentdb-architect/references/commands/audit.md +23 -0
  101. package/skills/aws/aws-documentdb-architect/references/evidence-ledger.md +52 -0
  102. package/skills/aws/aws-documentdb-architect/references/official-sources.md +15 -0
  103. package/skills/aws/aws-documentdb-architect/references/operations.md +165 -0
  104. package/skills/aws/aws-documentdb-architect/references/safety-checklist.md +22 -0
  105. package/skills/aws/aws-documentdb-architect/references/workflow-and-output.md +22 -0
  106. package/skills/aws/aws-dynamodb-data-modeling-performance-review/SKILL.md +5 -3
  107. package/skills/aws/aws-dynamodb-data-modeling-performance-review/metadata.json +7 -3
  108. package/skills/aws/aws-dynamodb-data-modeling-performance-review/references/consistency-indexing-replication.md +103 -0
  109. package/skills/aws/aws-dynamodb-data-modeling-performance-review/references/evidence-ledger.md +38 -0
  110. package/skills/aws/aws-dynamodb-patterns/CHANGELOG.md +87 -0
  111. package/skills/aws/aws-dynamodb-patterns/README.md +132 -0
  112. package/skills/aws/aws-dynamodb-patterns/SKILL.md +82 -0
  113. package/skills/aws/aws-dynamodb-patterns/assets/bedrock-embedding-input.json +6 -0
  114. package/skills/aws/aws-dynamodb-patterns/assets/content-review.json +6 -0
  115. package/skills/aws/aws-dynamodb-patterns/assets/create-table-with-lsi.json +41 -0
  116. package/skills/aws/aws-dynamodb-patterns/assets/create-table.json +27 -0
  117. package/skills/aws/aws-dynamodb-patterns/assets/create-table.sh +37 -0
  118. package/skills/aws/aws-dynamodb-patterns/assets/embedding-flow.py +89 -0
  119. package/skills/aws/aws-dynamodb-patterns/assets/query-input.json +13 -0
  120. package/skills/aws/aws-dynamodb-patterns/assets/query-pages.mjs +54 -0
  121. package/skills/aws/aws-dynamodb-patterns/assets/stream-read-policy.json +11 -0
  122. package/skills/aws/aws-dynamodb-patterns/assets/table-index-read-policy.json +20 -0
  123. package/skills/aws/aws-dynamodb-patterns/assets/table-resource-policy.json +22 -0
  124. package/skills/aws/aws-dynamodb-patterns/assets/table.cfn.yaml +55 -0
  125. package/skills/aws/aws-dynamodb-patterns/assets/typed-vector-item.json +15 -0
  126. package/skills/aws/aws-dynamodb-patterns/assets/vector-create-table.json +23 -0
  127. package/skills/aws/aws-dynamodb-patterns/assets/vector-search-policy.json +11 -0
  128. package/skills/aws/aws-dynamodb-patterns/assets/vector-search.json +10 -0
  129. package/skills/aws/aws-dynamodb-patterns/assets/vector-table.cfn.yaml +41 -0
  130. package/skills/aws/aws-dynamodb-patterns/evals/audit.test.py +87 -0
  131. package/skills/aws/aws-dynamodb-patterns/evals/backup-restore.test.py +163 -0
  132. package/skills/aws/aws-dynamodb-patterns/evals/commands.test.py +185 -0
  133. package/skills/aws/aws-dynamodb-patterns/evals/create-table.test.py +99 -0
  134. package/skills/aws/aws-dynamodb-patterns/evals/data-vectors-maintenance.test.py +201 -0
  135. package/skills/aws/aws-dynamodb-patterns/evals/embedding-commands.test.py +162 -0
  136. package/skills/aws/aws-dynamodb-patterns/evals/embedding-flow.test.py +167 -0
  137. package/skills/aws/aws-dynamodb-patterns/evals/eval.md +328 -0
  138. package/skills/aws/aws-dynamodb-patterns/evals/evals.json +185 -0
  139. package/skills/aws/aws-dynamodb-patterns/evals/modes.test.py +195 -0
  140. package/skills/aws/aws-dynamodb-patterns/evals/operations.test.py +288 -0
  141. package/skills/aws/aws-dynamodb-patterns/evals/query-pages.test.mjs +156 -0
  142. package/skills/aws/aws-dynamodb-patterns/evals/readme-and-loading.test.py +69 -0
  143. package/skills/aws/aws-dynamodb-patterns/evals/verify.py +166 -0
  144. package/skills/aws/aws-dynamodb-patterns/metadata.json +28 -0
  145. package/skills/aws/aws-dynamodb-patterns/references/commands/README.md +32 -0
  146. package/skills/aws/aws-dynamodb-patterns/references/commands/audit/live.md +64 -0
  147. package/skills/aws/aws-dynamodb-patterns/references/commands/audit/offline.md +28 -0
  148. package/skills/aws/aws-dynamodb-patterns/references/commands/audit.md +65 -0
  149. package/skills/aws/aws-dynamodb-patterns/references/commands/aws-cli.md +206 -0
  150. package/skills/aws/aws-dynamodb-patterns/references/commands/backup/on-demand.md +36 -0
  151. package/skills/aws/aws-dynamodb-patterns/references/commands/backup/pitr.md +41 -0
  152. package/skills/aws/aws-dynamodb-patterns/references/commands/backup.md +27 -0
  153. package/skills/aws/aws-dynamodb-patterns/references/commands/design.md +47 -0
  154. package/skills/aws/aws-dynamodb-patterns/references/commands/embedding.md +200 -0
  155. package/skills/aws/aws-dynamodb-patterns/references/commands/feature-plan.md +56 -0
  156. package/skills/aws/aws-dynamodb-patterns/references/commands/help.md +28 -0
  157. package/skills/aws/aws-dynamodb-patterns/references/commands/performance-test.md +95 -0
  158. package/skills/aws/aws-dynamodb-patterns/references/commands/recovery-target.md +47 -0
  159. package/skills/aws/aws-dynamodb-patterns/references/commands/refactor.md +82 -0
  160. package/skills/aws/aws-dynamodb-patterns/references/commands/restore/on-demand.md +32 -0
  161. package/skills/aws/aws-dynamodb-patterns/references/commands/restore/pitr.md +42 -0
  162. package/skills/aws/aws-dynamodb-patterns/references/commands/restore.md +76 -0
  163. package/skills/aws/aws-dynamodb-patterns/references/commands/select.md +22 -0
  164. package/skills/aws/aws-dynamodb-patterns/references/data-types-and-vectors.md +175 -0
  165. package/skills/aws/aws-dynamodb-patterns/references/embedding-integrations.md +237 -0
  166. package/skills/aws/aws-dynamodb-patterns/references/encryption.md +156 -0
  167. package/skills/aws/aws-dynamodb-patterns/references/evidence-index.md +116 -0
  168. package/skills/aws/aws-dynamodb-patterns/references/evidence-ledger.md +373 -0
  169. package/skills/aws/aws-dynamodb-patterns/references/iam-and-access.md +173 -0
  170. package/skills/aws/aws-dynamodb-patterns/references/language-adapters.md +251 -0
  171. package/skills/aws/aws-dynamodb-patterns/references/lsi-vs-gsi.md +116 -0
  172. package/skills/aws/aws-dynamodb-patterns/references/maintenance.md +56 -0
  173. package/skills/aws/aws-dynamodb-patterns/references/modeling.md +131 -0
  174. package/skills/aws/aws-dynamodb-patterns/references/monitoring.md +137 -0
  175. package/skills/aws/aws-dynamodb-patterns/references/official-sources.md +34 -0
  176. package/skills/aws/aws-dynamodb-patterns/references/operations.md +130 -0
  177. package/skills/aws/aws-dynamodb-patterns/references/provisioning.md +110 -0
  178. package/skills/aws/aws-dynamodb-patterns/references/recovery-and-replicas.md +148 -0
  179. package/skills/aws/aws-dynamodb-patterns/references/runtime-contract.md +140 -0
  180. package/skills/aws/aws-dynamodb-patterns/references/safety-checklist.md +35 -0
  181. package/skills/aws/aws-dynamodb-patterns/references/sources.md +170 -0
  182. package/skills/aws/aws-dynamodb-patterns/references/streams-and-dax.md +160 -0
  183. package/skills/aws/aws-dynamodb-patterns/references/workflow-and-output.md +34 -0
  184. package/skills/aws/aws-dynamodb-patterns/references/workflow.md +133 -0
  185. package/skills/aws/aws-dynamodb-patterns/scripts/review_due.py +61 -0
  186. package/skills/aws/aws-dynamodb-patterns/scripts/select_mode.py +127 -0
  187. package/skills/aws/aws-keyspaces-architect/SKILL.md +43 -0
  188. package/skills/aws/aws-keyspaces-architect/metadata.json +26 -0
  189. package/skills/aws/aws-keyspaces-architect/references/commands/audit/live.md +118 -0
  190. package/skills/aws/aws-keyspaces-architect/references/commands/audit/offline.md +125 -0
  191. package/skills/aws/aws-keyspaces-architect/references/commands/audit.md +22 -0
  192. package/skills/aws/aws-keyspaces-architect/references/evidence-ledger.md +49 -0
  193. package/skills/aws/aws-keyspaces-architect/references/official-sources.md +15 -0
  194. package/skills/aws/aws-keyspaces-architect/references/operations.md +154 -0
  195. package/skills/aws/aws-keyspaces-architect/references/safety-checklist.md +22 -0
  196. package/skills/aws/aws-keyspaces-architect/references/workflow-and-output.md +22 -0
  197. package/skills/aws/aws-maestro/SKILL.md +1 -1
  198. package/skills/aws/aws-maestro/metadata.json +1 -1
  199. package/skills/aws/aws-maestro/references/workflow-and-output.md +1 -0
  200. package/skills/azure/azure-cosmosdb-application-developer/SKILL.md +4 -2
  201. package/skills/azure/azure-cosmosdb-application-developer/metadata.json +1 -1
  202. package/skills/azure/azure-cosmosdb-pattern/CHANGELOG.md +10 -0
  203. package/skills/azure/azure-cosmosdb-pattern/README.md +102 -0
  204. package/skills/azure/azure-cosmosdb-pattern/SKILL.md +69 -0
  205. package/skills/azure/azure-cosmosdb-pattern/assets/account.arm.json +59 -0
  206. package/skills/azure/azure-cosmosdb-pattern/assets/content-review.json +9 -0
  207. package/skills/azure/azure-cosmosdb-pattern/assets/indexing-policy.json +7 -0
  208. package/skills/azure/azure-cosmosdb-pattern/assets/order.json +10 -0
  209. package/skills/azure/azure-cosmosdb-pattern/assets/provision.sh +32 -0
  210. package/skills/azure/azure-cosmosdb-pattern/assets/runtime.mjs +99 -0
  211. package/skills/azure/azure-cosmosdb-pattern/assets/vector-indexing-policy.json +7 -0
  212. package/skills/azure/azure-cosmosdb-pattern/assets/vector-policy.json +3 -0
  213. package/skills/azure/azure-cosmosdb-pattern/evals/eval.md +32 -0
  214. package/skills/azure/azure-cosmosdb-pattern/evals/fixtures/recovery-continuous.json +28 -0
  215. package/skills/azure/azure-cosmosdb-pattern/evals/prompts.json +24 -0
  216. package/skills/azure/azure-cosmosdb-pattern/evals/report.md +54 -0
  217. package/skills/azure/azure-cosmosdb-pattern/evals/runtime.test.mjs +146 -0
  218. package/skills/azure/azure-cosmosdb-pattern/evals/source-evidence.json +28 -0
  219. package/skills/azure/azure-cosmosdb-pattern/evals/test_package.py +355 -0
  220. package/skills/azure/azure-cosmosdb-pattern/metadata.json +25 -0
  221. package/skills/azure/azure-cosmosdb-pattern/references/access-control.md +42 -0
  222. package/skills/azure/azure-cosmosdb-pattern/references/change-feed-and-integrations.md +31 -0
  223. package/skills/azure/azure-cosmosdb-pattern/references/commands/audit/live.md +17 -0
  224. package/skills/azure/azure-cosmosdb-pattern/references/commands/audit/offline.md +15 -0
  225. package/skills/azure/azure-cosmosdb-pattern/references/commands/audit.md +8 -0
  226. package/skills/azure/azure-cosmosdb-pattern/references/commands/azure-cli.md +39 -0
  227. package/skills/azure/azure-cosmosdb-pattern/references/commands/backup/continuous.md +30 -0
  228. package/skills/azure/azure-cosmosdb-pattern/references/commands/backup/periodic.md +28 -0
  229. package/skills/azure/azure-cosmosdb-pattern/references/commands/backup.md +11 -0
  230. package/skills/azure/azure-cosmosdb-pattern/references/commands/design.md +13 -0
  231. package/skills/azure/azure-cosmosdb-pattern/references/commands/feature-plan.md +18 -0
  232. package/skills/azure/azure-cosmosdb-pattern/references/commands/help.md +13 -0
  233. package/skills/azure/azure-cosmosdb-pattern/references/commands/performance-test.md +24 -0
  234. package/skills/azure/azure-cosmosdb-pattern/references/commands/recovery-target.md +30 -0
  235. package/skills/azure/azure-cosmosdb-pattern/references/commands/refactor.md +14 -0
  236. package/skills/azure/azure-cosmosdb-pattern/references/commands/restore/continuous-deleted-resource.md +55 -0
  237. package/skills/azure/azure-cosmosdb-pattern/references/commands/restore/continuous-new-account.md +50 -0
  238. package/skills/azure/azure-cosmosdb-pattern/references/commands/restore/periodic-support.md +27 -0
  239. package/skills/azure/azure-cosmosdb-pattern/references/commands/restore.md +13 -0
  240. package/skills/azure/azure-cosmosdb-pattern/references/commands/select.md +11 -0
  241. package/skills/azure/azure-cosmosdb-pattern/references/data-types-and-vectors.md +51 -0
  242. package/skills/azure/azure-cosmosdb-pattern/references/embedding-integrations.md +56 -0
  243. package/skills/azure/azure-cosmosdb-pattern/references/encryption.md +53 -0
  244. package/skills/azure/azure-cosmosdb-pattern/references/evidence-index.md +72 -0
  245. package/skills/azure/azure-cosmosdb-pattern/references/evidence-ledger.md +174 -0
  246. package/skills/azure/azure-cosmosdb-pattern/references/indexing-and-capacity.md +37 -0
  247. package/skills/azure/azure-cosmosdb-pattern/references/language-adapters.md +112 -0
  248. package/skills/azure/azure-cosmosdb-pattern/references/maintenance.md +19 -0
  249. package/skills/azure/azure-cosmosdb-pattern/references/modeling.md +44 -0
  250. package/skills/azure/azure-cosmosdb-pattern/references/monitoring.md +23 -0
  251. package/skills/azure/azure-cosmosdb-pattern/references/provisioning.md +61 -0
  252. package/skills/azure/azure-cosmosdb-pattern/references/recovery.md +31 -0
  253. package/skills/azure/azure-cosmosdb-pattern/references/replication.md +22 -0
  254. package/skills/azure/azure-cosmosdb-pattern/references/runtime-contract.md +43 -0
  255. package/skills/azure/azure-cosmosdb-pattern/references/sources.md +61 -0
  256. package/skills/azure/azure-cosmosdb-pattern/references/workflow.md +18 -0
  257. package/skills/azure/azure-cosmosdb-pattern/scripts/recovery_guard.py +96 -0
  258. package/skills/azure/azure-cosmosdb-pattern/scripts/review_due.py +26 -0
  259. package/skills/azure/azure-cosmosdb-pattern/scripts/select_mode.py +108 -0
  260. package/skills/azure/azure-cosmosdb-pattern/scripts/validate_assets.py +53 -0
  261. package/skills/azure/azure-cosmosdb-platform-operator/SKILL.md +6 -2
  262. package/skills/azure/azure-cosmosdb-platform-operator/metadata.json +6 -3
  263. package/skills/azure/azure-cosmosdb-platform-operator/references/commands/audit/live.md +180 -0
  264. package/skills/azure/azure-cosmosdb-platform-operator/references/commands/audit/offline.md +160 -0
  265. package/skills/azure/azure-cosmosdb-platform-operator/references/commands/audit.md +26 -0
  266. package/skills/azure/azure-cosmosdb-platform-operator/references/consistency-capacity-security.md +136 -0
  267. package/skills/azure/azure-cosmosdb-platform-operator/references/cosmosdb-platform-operations.md +1 -1
  268. package/skills/azure/azure-cosmosdb-platform-operator/references/evidence-ledger.md +242 -0
  269. package/skills/azure/azure-cosmosdb-platform-operator/references/operations-cassandra.md +178 -0
  270. package/skills/azure/azure-cosmosdb-platform-operator/references/operations-mongodb.md +202 -0
  271. package/skills/azure/azure-cosmosdb-platform-operator/references/operations.md +126 -0
  272. package/skills/azure/azure-maestro/SKILL.md +1 -0
  273. package/skills/gcp/README.md +2 -1
  274. package/skills/gcp/gcp-bigtable-architect/SKILL.md +71 -0
  275. package/skills/gcp/gcp-bigtable-architect/metadata.json +28 -0
  276. package/skills/gcp/gcp-bigtable-architect/references/bigtable-design-guide.md +156 -0
  277. package/skills/gcp/gcp-bigtable-architect/references/commands/audit/live.md +122 -0
  278. package/skills/gcp/gcp-bigtable-architect/references/commands/audit/offline.md +140 -0
  279. package/skills/gcp/gcp-bigtable-architect/references/commands/audit.md +21 -0
  280. package/skills/gcp/gcp-bigtable-architect/references/evidence-ledger.md +83 -0
  281. package/skills/gcp/gcp-bigtable-architect/references/operations.md +111 -0
  282. package/skills/gcp/gcp-firebase-developer/SKILL.md +6 -3
  283. package/skills/gcp/gcp-firebase-developer/metadata.json +14 -4
  284. package/skills/gcp/gcp-firebase-developer/references/commands/audit/live.md +124 -0
  285. package/skills/gcp/gcp-firebase-developer/references/commands/audit/offline.md +146 -0
  286. package/skills/gcp/gcp-firebase-developer/references/commands/audit.md +27 -0
  287. package/skills/gcp/gcp-firebase-developer/references/evidence-ledger.md +190 -0
  288. package/skills/gcp/gcp-firebase-developer/references/firestore-mongodb-operations.md +189 -0
  289. package/skills/gcp/gcp-firebase-developer/references/firestore-operations.md +202 -0
  290. package/skills/gcp/gcp-firebase-developer/references/firestore.md +122 -0
  291. package/skills/gcp/gcp-maestro/SKILL.md +2 -1
  292. package/skills/huawei/README.md +2 -1
  293. package/skills/huawei/huawei-gaussdb-rds-dba/SKILL.md +7 -4
  294. package/skills/huawei/huawei-gaussdb-rds-dba/metadata.json +12 -4
  295. package/skills/huawei/huawei-gaussdb-rds-dba/references/commands/audit/live.md +68 -0
  296. package/skills/huawei/huawei-gaussdb-rds-dba/references/commands/audit/offline.md +106 -0
  297. package/skills/huawei/huawei-gaussdb-rds-dba/references/commands/audit.md +23 -0
  298. package/skills/huawei/huawei-gaussdb-rds-dba/references/dds-operations.md +135 -0
  299. package/skills/huawei/huawei-gaussdb-rds-dba/references/evidence-ledger.md +87 -0
  300. package/skills/huawei/huawei-geminidb-architect/SKILL.md +68 -0
  301. package/skills/huawei/huawei-geminidb-architect/metadata.json +26 -0
  302. package/skills/huawei/huawei-geminidb-architect/references/commands/audit/live.md +68 -0
  303. package/skills/huawei/huawei-geminidb-architect/references/commands/audit/offline.md +108 -0
  304. package/skills/huawei/huawei-geminidb-architect/references/commands/audit.md +23 -0
  305. package/skills/huawei/huawei-geminidb-architect/references/evidence-ledger.md +83 -0
  306. package/skills/huawei/huawei-geminidb-architect/references/geminidb-design-guide.md +114 -0
  307. package/skills/huawei/huawei-geminidb-architect/references/operations.md +135 -0
  308. package/skills/huawei/huawei-maestro/SKILL.md +2 -1
  309. package/skills/ionos/ionos-live-database-lifecycle-guard/SKILL.md +2 -0
  310. package/skills/ionos/ionos-live-database-lifecycle-guard/references/commands/audit/live.md +87 -0
  311. package/skills/ionos/ionos-live-database-lifecycle-guard/references/commands/audit/offline.md +109 -0
  312. package/skills/ionos/ionos-live-database-lifecycle-guard/references/commands/audit.md +27 -0
  313. package/skills/ionos/ionos-live-database-lifecycle-guard/references/evidence-ledger.md +69 -0
  314. package/skills/ionos/ionos-live-database-lifecycle-guard/references/mongodb-operations.md +220 -0
  315. package/skills/oci/README.md +6 -1
  316. package/skills/oci/oci-nosql-database-architect/SKILL.md +73 -0
  317. package/skills/oci/oci-nosql-database-architect/metadata.json +28 -0
  318. package/skills/oci/oci-nosql-database-architect/references/commands/audit/live.md +136 -0
  319. package/skills/oci/oci-nosql-database-architect/references/commands/audit/offline.md +150 -0
  320. package/skills/oci/oci-nosql-database-architect/references/commands/audit.md +28 -0
  321. package/skills/oci/oci-nosql-database-architect/references/evidence-ledger.md +96 -0
  322. package/skills/oci/oci-nosql-database-architect/references/nosql-design-guide.md +194 -0
  323. package/skills/oci/oci-nosql-database-architect/references/operations.md +194 -0
  324. package/skills/oci/oci-nosql-database-architect/references/sdk-matrix.md +43 -0
  325. package/skills/oci/oci-nosql-pattern/CHANGELOG.md +8 -0
  326. package/skills/oci/oci-nosql-pattern/README.md +81 -0
  327. package/skills/oci/oci-nosql-pattern/SKILL.md +62 -0
  328. package/skills/oci/oci-nosql-pattern/assets/content-review.json +10 -0
  329. package/skills/oci/oci-nosql-pattern/assets/create-table.sh +32 -0
  330. package/skills/oci/oci-nosql-pattern/assets/index-keys.json +11 -0
  331. package/skills/oci/oci-nosql-pattern/assets/migrator-export.json +22 -0
  332. package/skills/oci/oci-nosql-pattern/assets/migrator-import.json +29 -0
  333. package/skills/oci/oci-nosql-pattern/assets/orders.ddl +9 -0
  334. package/skills/oci/oci-nosql-pattern/assets/orders.tf +46 -0
  335. package/skills/oci/oci-nosql-pattern/assets/query-pages.mjs +33 -0
  336. package/skills/oci/oci-nosql-pattern/assets/query.json +13 -0
  337. package/skills/oci/oci-nosql-pattern/assets/query.sql +1 -0
  338. package/skills/oci/oci-nosql-pattern/assets/recovery-manifest.example.json +35 -0
  339. package/skills/oci/oci-nosql-pattern/assets/row.json +10 -0
  340. package/skills/oci/oci-nosql-pattern/assets/table-limits.json +6 -0
  341. package/skills/oci/oci-nosql-pattern/evals/cli-shapes.json +222 -0
  342. package/skills/oci/oci-nosql-pattern/evals/eval.md +26 -0
  343. package/skills/oci/oci-nosql-pattern/evals/prompts.json +89 -0
  344. package/skills/oci/oci-nosql-pattern/evals/report.md +41 -0
  345. package/skills/oci/oci-nosql-pattern/evals/test_package.py +350 -0
  346. package/skills/oci/oci-nosql-pattern/evals/test_runtime.mjs +77 -0
  347. package/skills/oci/oci-nosql-pattern/metadata.json +25 -0
  348. package/skills/oci/oci-nosql-pattern/references/access.md +29 -0
  349. package/skills/oci/oci-nosql-pattern/references/commands/audit/live.md +10 -0
  350. package/skills/oci/oci-nosql-pattern/references/commands/audit/offline.md +8 -0
  351. package/skills/oci/oci-nosql-pattern/references/commands/audit.md +6 -0
  352. package/skills/oci/oci-nosql-pattern/references/commands/backup/migrator.md +12 -0
  353. package/skills/oci/oci-nosql-pattern/references/commands/backup/sdk.md +10 -0
  354. package/skills/oci/oci-nosql-pattern/references/commands/backup.md +7 -0
  355. package/skills/oci/oci-nosql-pattern/references/commands/design.md +10 -0
  356. package/skills/oci/oci-nosql-pattern/references/commands/feature-plan.md +10 -0
  357. package/skills/oci/oci-nosql-pattern/references/commands/help.md +8 -0
  358. package/skills/oci/oci-nosql-pattern/references/commands/performance-test.md +12 -0
  359. package/skills/oci/oci-nosql-pattern/references/commands/refactor.md +9 -0
  360. package/skills/oci/oci-nosql-pattern/references/commands/restore/migrator.md +13 -0
  361. package/skills/oci/oci-nosql-pattern/references/commands/restore/sdk.md +11 -0
  362. package/skills/oci/oci-nosql-pattern/references/commands/restore.md +8 -0
  363. package/skills/oci/oci-nosql-pattern/references/commands/select.md +8 -0
  364. package/skills/oci/oci-nosql-pattern/references/embedding-integrations.md +25 -0
  365. package/skills/oci/oci-nosql-pattern/references/encryption.md +18 -0
  366. package/skills/oci/oci-nosql-pattern/references/evidence-index.md +44 -0
  367. package/skills/oci/oci-nosql-pattern/references/evidence-ledger.md +73 -0
  368. package/skills/oci/oci-nosql-pattern/references/indexes.md +19 -0
  369. package/skills/oci/oci-nosql-pattern/references/language-adapters.md +160 -0
  370. package/skills/oci/oci-nosql-pattern/references/maintenance.md +15 -0
  371. package/skills/oci/oci-nosql-pattern/references/modeling.md +26 -0
  372. package/skills/oci/oci-nosql-pattern/references/monitoring.md +21 -0
  373. package/skills/oci/oci-nosql-pattern/references/provisioning.md +44 -0
  374. package/skills/oci/oci-nosql-pattern/references/recovery-boundary.md +32 -0
  375. package/skills/oci/oci-nosql-pattern/references/replicas.md +18 -0
  376. package/skills/oci/oci-nosql-pattern/references/runtime-contract.md +23 -0
  377. package/skills/oci/oci-nosql-pattern/references/sources.md +57 -0
  378. package/skills/oci/oci-nosql-pattern/references/ttl.md +19 -0
  379. package/skills/oci/oci-nosql-pattern/references/types-and-vectors.md +27 -0
  380. package/skills/oci/oci-nosql-pattern/scripts/check_recovery.py +52 -0
  381. package/skills/oci/oci-nosql-pattern/scripts/review_due.py +32 -0
  382. package/skills/oci/oci-nosql-pattern/scripts/select_mode.py +96 -0
  383. package/skills/ovhcloud/ovhcloud-mongodb-architect/SKILL.md +43 -0
  384. package/skills/ovhcloud/ovhcloud-mongodb-architect/metadata.json +25 -0
  385. package/skills/ovhcloud/ovhcloud-mongodb-architect/references/commands/audit/live.md +90 -0
  386. package/skills/ovhcloud/ovhcloud-mongodb-architect/references/commands/audit/offline.md +112 -0
  387. package/skills/ovhcloud/ovhcloud-mongodb-architect/references/commands/audit.md +24 -0
  388. package/skills/ovhcloud/ovhcloud-mongodb-architect/references/evidence-ledger.md +93 -0
  389. package/skills/ovhcloud/ovhcloud-mongodb-architect/references/official-sources.md +15 -0
  390. package/skills/ovhcloud/ovhcloud-mongodb-architect/references/operations.md +216 -0
  391. package/skills/ovhcloud/ovhcloud-mongodb-architect/references/safety-checklist.md +22 -0
  392. package/skills/ovhcloud/ovhcloud-mongodb-architect/references/workflow-and-output.md +22 -0
  393. package/skills/scaleway/scaleway-managed-mongodb-architect/SKILL.md +43 -0
  394. package/skills/scaleway/scaleway-managed-mongodb-architect/metadata.json +24 -0
  395. package/skills/scaleway/scaleway-managed-mongodb-architect/references/commands/audit/live.md +99 -0
  396. package/skills/scaleway/scaleway-managed-mongodb-architect/references/commands/audit/offline.md +114 -0
  397. package/skills/scaleway/scaleway-managed-mongodb-architect/references/commands/audit.md +24 -0
  398. package/skills/scaleway/scaleway-managed-mongodb-architect/references/evidence-ledger.md +43 -0
  399. package/skills/scaleway/scaleway-managed-mongodb-architect/references/official-sources.md +14 -0
  400. package/skills/scaleway/scaleway-managed-mongodb-architect/references/operations.md +114 -0
  401. package/skills/scaleway/scaleway-managed-mongodb-architect/references/safety-checklist.md +22 -0
  402. package/skills/scaleway/scaleway-managed-mongodb-architect/references/workflow-and-output.md +22 -0
  403. package/templates/nosql-audit-template.md +127 -0
  404. package/templates/nosql-operations-template.md +60 -0
  405. package/tests/_generate_maestro_routing_fixtures.py +11 -0
  406. package/tests/fixtures/README.md +2 -2
  407. package/tests/fixtures/alibaba-maestro-routing/expected/050-happy-tablestore-partition-key.json +6 -0
  408. package/tests/fixtures/alibaba-maestro-routing/expected/adv-tablestore-not-polardb.json +6 -0
  409. package/tests/fixtures/alibaba-maestro-routing/inputs/050-happy-tablestore-partition-key.json +7 -0
  410. package/tests/fixtures/alibaba-maestro-routing/inputs/adv-tablestore-not-polardb.json +7 -0
  411. package/tests/fixtures/alibaba-maestro-routing/taxonomy.json +13 -0
  412. package/tests/fixtures/aws-maestro-routing/expected/042-happy-dynamodb-patterns.json +6 -0
  413. package/tests/fixtures/aws-maestro-routing/expected/043-happy-dynamodb-vector-index.json +6 -0
  414. package/tests/fixtures/aws-maestro-routing/inputs/042-happy-dynamodb-patterns.json +7 -0
  415. package/tests/fixtures/aws-maestro-routing/inputs/043-happy-dynamodb-vector-index.json +7 -0
  416. package/tests/fixtures/aws-maestro-routing/taxonomy.json +15 -1
  417. package/tests/fixtures/azure-maestro-routing/expected/028-happy-cosmosdb-pattern-feature-plan.json +6 -0
  418. package/tests/fixtures/azure-maestro-routing/expected/029-happy-cosmosdb-pattern-refactor.json +6 -0
  419. package/tests/fixtures/azure-maestro-routing/expected/adv-cosmos-hot-partition-not-key-vault.json +6 -0
  420. package/tests/fixtures/azure-maestro-routing/expected/adv-cosmos-partition-key-not-key-vault.json +6 -0
  421. package/tests/fixtures/azure-maestro-routing/expected/adv-cosmos-throttling-investigation.json +6 -0
  422. package/tests/fixtures/azure-maestro-routing/inputs/028-happy-cosmosdb-pattern-feature-plan.json +7 -0
  423. package/tests/fixtures/azure-maestro-routing/inputs/029-happy-cosmosdb-pattern-refactor.json +7 -0
  424. package/tests/fixtures/azure-maestro-routing/inputs/adv-cosmos-hot-partition-not-key-vault.json +7 -0
  425. package/tests/fixtures/azure-maestro-routing/inputs/adv-cosmos-partition-key-not-key-vault.json +7 -0
  426. package/tests/fixtures/azure-maestro-routing/inputs/adv-cosmos-throttling-investigation.json +7 -0
  427. package/tests/fixtures/azure-maestro-routing/taxonomy.json +21 -2
  428. package/tests/fixtures/gcp-maestro-routing/expected/049-happy-bigtable-row-key.json +6 -0
  429. package/tests/fixtures/gcp-maestro-routing/expected/adv-bigtable-not-firestore.json +8 -0
  430. package/tests/fixtures/gcp-maestro-routing/inputs/049-happy-bigtable-row-key.json +7 -0
  431. package/tests/fixtures/gcp-maestro-routing/inputs/adv-bigtable-not-firestore.json +7 -0
  432. package/tests/fixtures/gcp-maestro-routing/taxonomy.json +15 -0
  433. package/tests/fixtures/huawei-maestro-routing/expected/050-happy-geminidb-cassandra-partition.json +6 -0
  434. package/tests/fixtures/huawei-maestro-routing/expected/adv-geminidb-mongo-routes-dds.json +7 -0
  435. package/tests/fixtures/huawei-maestro-routing/inputs/050-happy-geminidb-cassandra-partition.json +7 -0
  436. package/tests/fixtures/huawei-maestro-routing/inputs/adv-geminidb-mongo-routes-dds.json +7 -0
  437. package/tests/fixtures/huawei-maestro-routing/taxonomy.json +15 -0
  438. package/tests/fixtures/nosql-scenarios/scenarios.json +472 -0
  439. package/tests/fixtures/oci-maestro-routing/expected/031-happy-nosql-database-architect.json +6 -0
  440. package/tests/fixtures/oci-maestro-routing/expected/032-happy-nosql-global-active-table.json +6 -0
  441. package/tests/fixtures/oci-maestro-routing/expected/033-happy-nosql-pattern-recovery.json +6 -0
  442. package/tests/fixtures/oci-maestro-routing/expected/034-happy-nosql-pattern-refactor.json +6 -0
  443. package/tests/fixtures/oci-maestro-routing/expected/adv-nosql-live-mutation.json +6 -0
  444. package/tests/fixtures/oci-maestro-routing/expected/adv-nosql-not-autonomous.json +7 -0
  445. package/tests/fixtures/oci-maestro-routing/inputs/031-happy-nosql-database-architect.json +7 -0
  446. package/tests/fixtures/oci-maestro-routing/inputs/032-happy-nosql-global-active-table.json +7 -0
  447. package/tests/fixtures/oci-maestro-routing/inputs/033-happy-nosql-pattern-recovery.json +7 -0
  448. package/tests/fixtures/oci-maestro-routing/inputs/034-happy-nosql-pattern-refactor.json +7 -0
  449. package/tests/fixtures/oci-maestro-routing/inputs/adv-nosql-live-mutation.json +7 -0
  450. package/tests/fixtures/oci-maestro-routing/inputs/adv-nosql-not-autonomous.json +7 -0
  451. package/tests/fixtures/oci-maestro-routing/taxonomy.json +27 -0
  452. package/tests/requirements-ci.txt +8 -0
  453. package/tests/validate-aws-skill-quality.py +7 -0
  454. package/tests/validate-nosql-audit.py +741 -0
  455. package/tests/validate-nosql-operations.py +136 -0
  456. package/tests/validate-nosql-pattern-evals.py +96 -0
  457. package/tests/validate-nosql-scenarios.py +94 -0
  458. package/tests/validate-skill-manifest.py +6 -1
  459. package/tests/validate-skill-references.py +225 -0
@@ -0,0 +1,242 @@
1
+ # Evidence ledger — Azure Cosmos DB for NoSQL
2
+
3
+ Every material claim in
4
+ [consistency-capacity-security.md](consistency-capacity-security.md) cites one
5
+ row below as `[COSMOS-Exx]`. `tests/validate-skill-references.py` fails the
6
+ build if a citation has no row, a row is never cited, or a source is not on
7
+ learn.microsoft.com.
8
+
9
+ Scope: **Azure Cosmos DB for NoSQL** only. The MongoDB, Cassandra, Gremlin and
10
+ Table APIs map consistency and features differently; do not apply these rows
11
+ to them. `VERIFIED` = the section was retrieved on the retrieval date and
12
+ supports the claim as worded; it is documentation verification, not a
13
+ behavioral test. Preview features can change without notice: re-fetch before
14
+ relying on them.
15
+
16
+ | ID | Claim | Source | Section | Retrieved | Status |
17
+ | --- | --- | --- | --- | --- | --- |
18
+ | COSMOS-E01 | Five consistency levels, strongest to weakest: Strong, Bounded staleness, Session, Consistent prefix, Eventual. Read consistency applies to a single read within a logical partition. | <https://learn.microsoft.com/azure/cosmos-db/consistency-levels> | Consistency levels; Scope of read consistency | 2026-11-08 | VERIFIED |
19
+ | COSMOS-E02 | Strong and Bounded staleness read from two replicas (local minority), so their read RU cost is twice the weaker levels; write RU cost is identical across levels; Strong commits writes in every region (global majority). | <https://learn.microsoft.com/azure/cosmos-db/consistency-levels> | Consistency levels and throughput | 2026-11-08 | VERIFIED |
20
+ | COSMOS-E03 | Session tokens are partition-bound; a client with no token for a physical partition, or a re-created client, reads with eventual behavior until its writes rebuild the token cache; tokens passed between clients must not be modified; Session is the most widely used level. | <https://learn.microsoft.com/azure/cosmos-db/consistency-levels> | Guarantees associated with consistency levels | 2026-11-08 | VERIFIED |
21
+ | COSMOS-E04 | Under Consistent prefix, single-document writes see eventual consistency, while writes in one transactional batch become visible together. | <https://learn.microsoft.com/azure/cosmos-db/consistency-levels> | Consistent prefix consistency | 2026-11-08 | VERIFIED |
22
+ | COSMOS-E05 | A `ConsistencyLevel` override can only relax below the account default; `ReadConsistencyStrategy` (Default, Session, Eventual, Latest Committed, Global Strong) can also strengthen above it, at client or request level, and takes precedence when both are set. It is in preview, supported in direct mode only, and not available in gateway mode. | <https://learn.microsoft.com/azure/cosmos-db/how-to-manage-consistency> | Use Read Consistency Strategy | 2026-11-08 | VERIFIED |
23
+ | COSMOS-E06 | `ReadConsistencyStrategy` is documented for Java SDK v4.69+ and .NET SDK v3.46+ only; no other SDK is listed. | <https://learn.microsoft.com/azure/cosmos-db/how-to-manage-consistency> | Use Read Consistency Strategy | 2026-11-08 | VERIFIED |
24
+ | COSMOS-E07 | The integrated cache serves only Session and Eventual reads; other levels bypass it; writes at any level still populate it. | <https://learn.microsoft.com/azure/cosmos-db/integrated-cache> | Integrated cache consistency | 2026-11-08 | VERIFIED |
25
+ | COSMOS-E08 | A cache hit requires the dedicated gateway endpoint, gateway connection mode (.NET/Java default to direct and must override) and Session or Eventual consistency; `MaxIntegratedCacheStaleness` defaults to 5 minutes and 0 means reads never use the cache. | <https://learn.microsoft.com/azure/cosmos-db/how-to-configure-integrated-cache> | Verify cache hits; Adjust MaxIntegratedCacheStaleness | 2026-11-08 | VERIFIED |
26
+ | COSMOS-E09 | SLA coverage for the dedicated gateway needs at least three nodes; the dedicated gateway has no latency SLA; the integrated cache is available for the API for NoSQL only. | <https://learn.microsoft.com/azure/cosmos-db/integrated-cache-faq> | Frequently asked questions | 2026-11-08 | VERIFIED |
27
+ | COSMOS-E10 | Serverless accounts run in a single region and regions cannot be added later; provisioned throughput supports unlimited regions and an SLA on point reads/writes, serverless only an SLO. | <https://learn.microsoft.com/azure/cosmos-db/throughput-serverless> | Detailed comparison | 2026-11-08 | VERIFIED |
28
+ | COSMOS-E11 | A serverless container begins at 5,000 RU/s and each physical partition handles up to 5,000 RU/s; serverless containers reject throughput settings and serverless accounts cannot have shared-throughput databases. | <https://learn.microsoft.com/azure/cosmos-db/serverless> | Use serverless resources | 2026-11-08 | VERIFIED |
29
+ | COSMOS-E12 | Each logical partition is capped at 10,000 RU/s and 20 GB (data plus index); hierarchical partition keys allow up to three levels when one key value would exceed 20 GB; when logical partitions collectively exceed their physical partition's throughput, operations are rate-limited. | <https://learn.microsoft.com/azure/cosmos-db/set-throughput> | Comparison of models; Set throughput on a database | 2026-11-08 | VERIFIED |
30
+ | COSMOS-E13 | Autoscale scales between 0.1 x Tmax and Tmax, bills the highest RU/s reached each hour (minimum 0.1 x Tmax), does not rate-limit within the configured range, and shared-database autoscale is not recommended because one container's burst can throttle others. | <https://learn.microsoft.com/azure/cosmos-db/provision-throughput-autoscale> | Comparison; Throughput and storage limits for autoscale | 2026-11-08 | VERIFIED |
31
+ | COSMOS-E14 | Data-plane access (items, queries, change feed, stored procedures, conflicts) uses Cosmos DB native RBAC with built-in roles "Cosmos DB Built-in Data Reader" and "Cosmos DB Built-in Data Contributor"; it does not support `notDataActions`; it cannot be managed in the portal; creating its definitions and assignments needs control-plane `sqlRoleDefinitions`/`sqlRoleAssignments` permissions. | <https://learn.microsoft.com/azure/cosmos-db/how-to-connect-role-based-access-control> | Grant data plane role-based access | 2026-11-08 | VERIFIED |
32
+ | COSMOS-E15 | Control-plane access (read and regenerate account keys and connection strings, backup and restore, database/container management, account properties) is separate from data-plane access and is granted through Azure RBAC role definitions. | <https://learn.microsoft.com/azure/cosmos-db/how-to-connect-role-based-access-control> | Grant control plane role-based access | 2026-11-08 | VERIFIED |
33
+ | COSMOS-E16 | Key-based authentication is disabled by setting `properties.disableLocalAuth=true`, which needs at least `Microsoft.DocumentDb/databaseAccounts/*/write`; connecting with a key should then fail. | <https://learn.microsoft.com/azure/cosmos-db/how-to-connect-role-based-access-control> | Disable key-based authentication; Validate that key-based authentication is disabled | 2026-11-08 | VERIFIED |
34
+ | COSMOS-E17 | Accounts with multiple write regions cannot use Strong consistency; Strong for accounts spanning more than 5,000 miles (8,000 km) is blocked by default; multi-region Strong write latency is two times the RTT between the two farthest regions plus 10 ms at p99. | <https://learn.microsoft.com/azure/cosmos-db/consistency-levels> | Strong consistency and multiple write regions; Write latency and Strong consistency | 2026-11-08 | VERIFIED |
35
+ | COSMOS-E18 | Region-outage RPO by level, for accounts in more than one region: Session, Consistent prefix and Eventual under 15 minutes; Bounded staleness K and T; Strong zero (single write region only). A single-region account has RPO under 240 minutes at any level. | <https://learn.microsoft.com/azure/cosmos-db/consistency-levels> | Consistency levels and data durability | 2026-11-08 | VERIFIED |
36
+ | COSMOS-E19 | Serverless containers offer no guarantee of predictable throughput or latency; maximum serverless throughput is the number of physical partitions times 5,000 RU/s. | <https://learn.microsoft.com/azure/cosmos-db/serverless-performance> | Request unit changes | 2026-11-08 | VERIFIED |
37
+ | COSMOS-E20 | A serverless API for NoSQL account can be changed in place to provisioned throughput: containers become manual provisioned at partitions x 5,000 RU/s; the change is one-time and irreversible, has no duration SLA, and blocks management operations while it runs. | <https://learn.microsoft.com/azure/cosmos-db/how-to-change-capacity-mode> | Change from serverless to provisioned capacity mode; Limitations | 2026-11-08 | VERIFIED |
38
+ | COSMOS-E21 | Microsoft's session-token example for the Python SDK reads the token from a read response (`ReadItem`, then `last_response_headers["x-ms-session-token"]`) and passes it on a later read, so a read response also carries a session token. The documentation does not say whether each SDK caches tokens from reads automatically. | <https://learn.microsoft.com/azure/cosmos-db/how-to-manage-consistency> | Utilize session tokens | 2026-11-08 | VERIFIED |
39
+ | COSMOS-E101 | Two backup modes exist: periodic and continuous; continuous has 7-day, 30-day and 35-day retention tiers, and an account in continuous mode cannot be switched back to periodic. | <https://learn.microsoft.com/azure/cosmos-db/online-backup-and-restore> | Backup and restore in Azure Cosmos DB: "Continuous backup mode lets you restore to any point in time within the configured retention tier" | 2026-11-08 | VERIFIED |
40
+ | COSMOS-E102 | Periodic mode is the default for existing accounts; restores are requested through the support team and the maximum retention is a month with a minimum interval of one hour. | <https://learn.microsoft.com/azure/cosmos-db/online-backup-and-restore> | Backup and restore in Azure Cosmos DB: "backup is taken at a periodic interval and the data is restored by creating a request with the support team" | 2026-11-08 | VERIFIED |
41
+ | COSMOS-E103 | Periodic mode takes a full backup every 4 hours and keeps only the latest two by default; interval and retention are configurable in the portal. | <https://learn.microsoft.com/azure/cosmos-db/periodic-backup-restore-introduction> | Periodic backup and restore: "At any point of time, only the latest two backups are stored by default." | 2026-11-08 | VERIFIED |
42
+ | COSMOS-E104 | Periodic restore always creates a new account in the write region of the source account; any mix of containers, shared-throughput databases or the whole account can be restored. | <https://learn.microsoft.com/azure/cosmos-db/periodic-backup-restore-introduction> | What is restored into a new account?: "The restore action always restores data into a new account, which is located in the write region of the source account." | 2026-11-08 | VERIFIED |
43
+ | COSMOS-E105 | Periodic restore does not bring back account keys (new keys are generated) or firewall, virtual network, data plane RBAC and private endpoint settings. | <https://learn.microsoft.com/azure/cosmos-db/periodic-backup-restore-introduction> | What isn't restored?: "Firewall, virtual network, data plane RBAC, or private endpoint settings." | 2026-11-08 | VERIFIED |
44
+ | COSMOS-E106 | Periodic restore or retention changes are allowed for principals in the CosmosdbBackupOperator role, owner or contributor. | <https://learn.microsoft.com/azure/cosmos-db/periodic-backup-restore-introduction> | Required permissions to manage retention or restoration: "Principals who are part of the role CosmosdbBackupOperator, owner, or contributor are allowed to request a restore or change the retention period." | 2026-11-08 | VERIFIED |
45
+ | COSMOS-E107 | Continuous-mode account restore always restores into a new account. | <https://learn.microsoft.com/azure/cosmos-db/continuous-backup-restore-introduction> | Continuous backup with point-in-time restore: "The restore action always restores data into a new account." | 2026-11-08 | VERIFIED |
46
+ | COSMOS-E108 | Deleted containers and databases can be restored into a new account or into an existing account under continuous backup. | <https://learn.microsoft.com/azure/cosmos-db/continuous-backup-restore-introduction> | Continuous backup with point-in-time restore: "They can be restored into a new account or into an existing account." | 2026-11-08 | VERIFIED |
47
+ | COSMOS-E109 | Continuous restore does not bring back firewall, virtual network, data plane RBAC or private endpoint settings; the same list also omits source regions, stored procedures, triggers, UDFs and RBAC assignments, and a subset of containers in a shared-throughput database. | <https://learn.microsoft.com/azure/cosmos-db/continuous-backup-restore-introduction> | What isn't restored?: "Firewall, virtual network, data plane role-based access control, or private endpoint settings." | 2026-11-08 | VERIFIED |
48
+ | COSMOS-E110 | Continuous backups are taken in every region of the account; they are locally redundant by default and zone redundant if availability zones are enabled for that region. | <https://learn.microsoft.com/azure/cosmos-db/continuous-backup-restore-introduction> | Continuous backup with point-in-time restore: "Backups taken for each region account are locally redundant by default, and zone redundant if your account has availability zone feature enabled for that region." | 2026-11-08 | VERIFIED |
49
+ | COSMOS-E111 | The 30-day and 35-day continuous tiers incur a monthly backup storage charge; all tiers incur a charge each time a restore is initiated. | <https://learn.microsoft.com/azure/cosmos-db/continuous-backup-restore-introduction> | Pricing: "Accounts enabled with continuous backup policy at the 30-day or 35-day tier incur a monthly charge for backup storage." | 2026-11-08 | VERIFIED |
50
+ | COSMOS-E112 | Analytical store data is not included in backups and restores for Synapse Link accounts. | <https://learn.microsoft.com/azure/cosmos-db/online-backup-and-restore> | Backup and restore in Azure Cosmos DB: "analytical store data isn't included in the backups and restores" | 2026-11-08 | VERIFIED |
51
+ | COSMOS-E113 | Zone redundancy distributes replicas across availability zones; it is configured per region, not account-wide. | <https://learn.microsoft.com/azure/cosmos-db/high-availability> | Resilience to availability zone failures: "When you enable zone redundancy, Azure distributes the replicas of your data across multiple availability zones" | 2026-11-08 | VERIFIED |
52
+ | COSMOS-E114 | Availability zone failover and recovery are fully managed by Microsoft and need no customer action. | <https://learn.microsoft.com/azure/cosmos-db/high-availability> | Resilience to availability zone failures: "Availability zone failover and recovery for Azure Cosmos DB are fully managed by Microsoft." | 2026-11-08 | VERIFIED |
53
+ | COSMOS-E115 | For a single-write-region multi-region account without per-partition failover, service-managed failover is automatic but can take one hour or more. | <https://learn.microsoft.com/azure/cosmos-db/high-availability> | Resilience to region failures: "If service-managed failover is enabled, Azure Cosmos DB initiates failover automatically, but this might take one hour or more." | 2026-11-08 | VERIFIED |
54
+ | COSMOS-E116 | Multi-write-region accounts route to healthy regions automatically through SDK configuration with no manual intervention. | <https://learn.microsoft.com/azure/cosmos-db/high-availability> | Resilience to region failures: "Automatic routing to healthy regions via SDK configuration; no manual intervention required." | 2026-11-08 | VERIFIED |
55
+ | COSMOS-E117 | Per-partition automatic failover (PPAF) fails individual partitions of a single-write-region account over to a secondary region. | <https://learn.microsoft.com/azure/cosmos-db/high-availability> | Resilience to region failures: "PPAF enables single-write region accounts to automatically fail over individual partitions to a secondary region" | 2026-11-08 | VERIFIED |
56
+ | COSMOS-E118 | A manual failover is triggered by changing the region that holds failoverPriority=0. | <https://learn.microsoft.com/azure/cosmos-db/manage-with-powershell> | Trigger Manual Failover: "Changing the location for failoverPriority=0 triggers a manual failover for an Azure Cosmos DB account." | 2026-11-08 | VERIFIED |
57
+ | COSMOS-E119 | Zone-redundant regions are charged at a premium, waived for multi-region-write accounts and autoscale collections. | <https://learn.microsoft.com/azure/cosmos-db/high-availability> | Resilience to availability zone failures: "Regions where zone redundancy is enabled are charged at a premium." | 2026-11-08 | VERIFIED |
58
+ | COSMOS-E120 | Microsoft publishes SLAs for availability, latency, throughput and consistency that vary by configuration. | <https://learn.microsoft.com/azure/cosmos-db/high-availability> | Service-level agreement: "Azure Cosmos DB provides SLAs for a range of configurations and service characteristics, including availability, latency, throughput, and consistency." | 2026-11-08 | VERIFIED |
59
+ | COSMOS-E121 | Billing meters: database operations (RU/s provisioned or consumed) and consumed storage, plus extra charges for backup storage, analytical storage, availability zones and multi-region writes. | <https://learn.microsoft.com/azure/cosmos-db/plan-manage-costs> | Plan and manage costs for Azure Cosmos DB: "An additional charge applies when you use Azure Cosmos DB features like backup storage, analytical storage, availability zones, and multiregion writes." | 2026-11-08 | VERIFIED |
60
+ | COSMOS-E122 | Provisioned throughput billing is at one-hour granularity. | <https://learn.microsoft.com/azure/cosmos-db/optimize-cost-throughput> | Optimize provisioned throughput cost: "the billing is at the granularity of one hour" | 2026-11-08 | VERIFIED |
61
+ | COSMOS-E123 | Periodic backup: two copies are free and extra copies are billed as backup storage. | <https://learn.microsoft.com/azure/cosmos-db/periodic-backup-restore-introduction> | Backup storage pricing: "Two backups are provided free and extra backups are charged according to the region-based pricing for backup storage" | 2026-11-08 | VERIFIED |
62
+ | COSMOS-E124 | Reserved capacity is an upfront commitment on request units over time. | <https://learn.microsoft.com/azure/cosmos-db/optimize-cost-throughput> | Optimize with reserved capacity: "Azure Cosmos DB reserved capacity model is an upfront commitment on requests units needed over time." | 2026-11-08 | VERIFIED |
63
+ | COSMOS-E125 | Diagnostic logs sent to Log Analytics are billed separately by ingested volume. | <https://learn.microsoft.com/azure/cosmos-db/troubleshoot-request-rate-too-large> | How to identify the hot partition: "Enabling diagnostic logs incurs a separate charge for the Log Analytics service, which is billed based on the volume of data ingested." | 2026-11-08 | VERIFIED |
64
+ | COSMOS-E126 | Platform metrics for Microsoft.DocumentDB/DatabaseAccounts flow to Azure Monitor; the list includes NormalizedRUConsumption, TotalRequests, TotalRequestUnits, ProvisionedThroughput, AutoscaleMaxThroughput, DataUsage, IndexUsage, ReplicationLatency and ServerSideLatencyDirect/Gateway. | <https://learn.microsoft.com/azure/cosmos-db/monitor-reference> | Azure Cosmos DB monitoring data reference: "The following table lists the metrics available for the Microsoft.DocumentDB/DatabaseAccounts resource type." | 2026-11-08 | VERIFIED |
65
+ | COSMOS-E127 | Hot partitions are found with Insights > Throughput > Normalized RU Consumption (%) by PartitionKeyRangeId; one range near 100 percent while others stay low signals a hot partition. | <https://learn.microsoft.com/azure/cosmos-db/troubleshoot-request-rate-too-large> | How to identify the hot partition: "navigate to Insights > Throughput > Normalized RU Consumption (%) By PartitionKeyRangeID" | 2026-11-08 | VERIFIED |
66
+ | COSMOS-E128 | The documentation points to Azure Monitor alerts and the Azure Monitor Baseline Alerts site for sample alerts but lists no Cosmos-specific thresholds. | <https://learn.microsoft.com/azure/cosmos-db/monitor> | Alerts: "Azure Monitor alerts proactively notify you when specific conditions are found in your monitoring data." | 2026-11-08 | VERIFIED |
67
+ | COSMOS-E129 | A 429 is returned when operations in a given second consume more than the provisioned RUs; RU availability resets each second. | <https://learn.microsoft.com/azure/cosmos-db/troubleshoot-request-rate-too-large> | Diagnose and troubleshoot Request rate too large (429) exceptions: "In a given second, if the operations consume more than the provisioned request units, Azure Cosmos DB returns a 429 exception." | 2026-11-08 | VERIFIED |
68
+ | COSMOS-E130 | The 429 message variants include request rate large, metadata request rate, transient service error and TXN_WAIT_FOR_TRANSACTION_END. | <https://learn.microsoft.com/azure/cosmos-db/troubleshoot-request-rate-too-large> | Diagnose and troubleshoot Request rate too large (429) exceptions: "Request rate is large. More Request Units might be needed, so no changes were made." | 2026-11-08 | VERIFIED |
69
+ | COSMOS-E131 | One to five percent of requests with 429 and acceptable latency is described as healthy use of provisioned RU/s; client SDKs retry 429s automatically, typically up to nine times. | <https://learn.microsoft.com/azure/cosmos-db/troubleshoot-request-rate-too-large> | Step 1: Check the metrics to determine the percentage of requests with 429 error: "In general, for a production workload, if you see between 1-5% of requests with 429 responses" | 2026-11-08 | VERIFIED |
70
+ | COSMOS-E132 | A hot partition is one or a few logical partition keys consuming a disproportionate share of RU/s, for example date-keyed IoT writes or one dominant tenant. | <https://learn.microsoft.com/azure/cosmos-db/troubleshoot-request-rate-too-large> | Step 2: Determine if there's a hot partition: "A hot partition arises when one or a few logical partition keys consume a disproportionate amount of the total RU/s" | 2026-11-08 | VERIFIED |
71
+ | COSMOS-E133 | Control-plane built-in role Cosmos DB Operator exists in Azure RBAC. | <https://learn.microsoft.com/azure/cosmos-db/role-based-access-control> | Cosmos DB Operator role: "In the Roles section, use the search phrase Cosmos DB and locate the Cosmos DB Operator role definition." | 2026-11-08 | VERIFIED |
72
+ | COSMOS-E134 | Azure Policy is enforced at the resource provider, so SDK management operations that bypass it ignore policies; built-in policies include disabling public network access and key-based metadata write access. | <https://learn.microsoft.com/azure/cosmos-db/policy> | Use Azure Policy to implement governance and controls for Azure Cosmos DB resources: "Azure Policy is enforced at the resource provider level for Azure services." | 2026-11-08 | VERIFIED |
73
+ | COSMOS-E135 | Built-in Azure Policy definitions audit or deny public network access and deploy diagnostic settings for Cosmos DB accounts. | <https://learn.microsoft.com/azure/cosmos-db/security-controls-policy> | Azure Policy Regulatory Compliance controls for Azure Cosmos DB: "Resource logs should be enabled to track activities and events that take place on your resources" | 2026-11-08 | VERIFIED |
74
+ | COSMOS-E136 | Resource tags can be set on a Cosmos DB account at creation and on update. | <https://learn.microsoft.com/azure/cosmos-db/manage-with-powershell> | Update Tags of an Azure Cosmos DB account: "Tags can be set both at account creation using New-AzCosmosDBAccount and on account update using Update-AzCosmosDBAccount." | 2026-11-08 | VERIFIED |
75
+ | COSMOS-E137 | The portal create flow describes tags as name/value pairs for categorizing resources and consolidated billing. | <https://learn.microsoft.com/azure/cosmos-db/how-to-manage-database-account> | Create an account: "Tags are name/value pairs that enable you to categorize resources and view consolidated billing by applying the same tag to multiple resources and resource groups." | 2026-11-08 | VERIFIED |
76
+ | COSMOS-E138 | Encryption at rest is always on with no switch and uses AES-256 in every region. | <https://learn.microsoft.com/azure/cosmos-db/database-encryption-at-rest> | Encryption at rest in Azure Cosmos DB: "Azure Cosmos DB uses AES-256 encryption on all regions where the account is running." | 2026-11-08 | VERIFIED |
77
+ | COSMOS-E139 | Databases, media attachments and backups are all encrypted at rest. | <https://learn.microsoft.com/azure/cosmos-db/database-encryption-at-rest> | Encryption at rest in Azure Cosmos DB: "all your databases, media attachments, and backups are encrypted" | 2026-11-08 | VERIFIED |
78
+ | COSMOS-E140 | Customer-managed keys add a second layer on top of service-managed keys and must be stored in Azure Key Vault, one key per account. | <https://learn.microsoft.com/azure/cosmos-db/how-to-setup-cmk> | Configure customer-managed keys: "You must store customer-managed keys in Azure Key Vault and provide a key for each Azure Cosmos DB account" | 2026-11-08 | VERIFIED |
79
+ | COSMOS-E141 | The Key Vault must be reachable via public network access or allow trusted Microsoft services to bypass its firewall, so a private-endpoint-only vault cannot host the key. | <https://learn.microsoft.com/azure/cosmos-db/how-to-setup-cmk> | Configure your Azure Key Vault instance: "Your Azure Key Vault instance must be accessible through public network access or allow trusted Microsoft services to bypass its firewall." | 2026-11-08 | VERIFIED |
80
+ | COSMOS-E142 | Soft Delete and Purge Protection are required on the Key Vault. | <https://learn.microsoft.com/azure/cosmos-db/how-to-setup-cmk> | Configure your Azure Key Vault instance: "Using customer-managed keys with Azure Cosmos DB requires you to set two properties on the Azure Key Vault instance" | 2026-11-08 | VERIFIED |
81
+ | COSMOS-E143 | Customer-managed keys can be enabled on existing accounts as well as new ones. | <https://learn.microsoft.com/azure/cosmos-db/how-to-setup-cmk> | Configure customer-managed keys: "If you wish to enable customer-managed keys on your existing Azure Cosmos DB accounts" | 2026-11-08 | VERIFIED |
82
+ | COSMOS-E144 | Creating a continuous-backup account with customer-managed keys currently supports only a user-assigned managed identity. | <https://learn.microsoft.com/azure/cosmos-db/how-to-setup-cmk> | Use customer-managed keys with continuous backup: "Currently, only user-assigned managed identity is supported for creating continuous backup accounts." | 2026-11-08 | VERIFIED |
83
+ | COSMOS-E145 | The service-wide minimum TLS version is 1.2, with a per-account minimalTlsVersion property. | <https://learn.microsoft.com/azure/cosmos-db/self-serve-minimum-tls-enforcement> | Minimum TLS version: "The minimum service-wide accepted version is TLS 1.2." | 2026-11-08 | VERIFIED |
84
+ | COSMOS-E146 | TLS 1.3 support was enabled for Azure Cosmos DB effective March 31, 2025. | <https://learn.microsoft.com/azure/cosmos-db/self-serve-minimum-tls-enforcement> | Minimum TLS version: "Effective March 31, 2025, support for TLS 1.3 is enabled for Azure Cosmos DB." | 2026-11-08 | VERIFIED |
85
+ | COSMOS-E147 | Private Link exposes the account through a private endpoint, a set of private IPs in a virtual network subnet. | <https://learn.microsoft.com/azure/cosmos-db/how-to-configure-private-endpoints> | Configure Azure Private Link for an Azure Cosmos DB account: "By using Azure Private Link, you can connect to an Azure Cosmos DB account through a private endpoint." | 2026-11-08 | VERIFIED |
86
+ | COSMOS-E148 | Private Link filters at application level and does not stop public DNS resolution of the account endpoint. | <https://learn.microsoft.com/azure/cosmos-db/how-to-configure-private-endpoints> | Configure Azure Private Link for an Azure Cosmos DB account: "Filtering of incoming requests happens at application level, not at transport or network level." | 2026-11-08 | VERIFIED |
87
+ | COSMOS-E149 | Setting publicNetworkAccess to Disabled overrides the allow-from-Azure-datacenters option. | <https://learn.microsoft.com/azure/cosmos-db/how-to-configure-firewall> | Configure IP firewall: "Setting publicNetworkAccess to Disabled takes precedence over the Accept connection from within Azure datacenters option." | 2026-11-08 | VERIFIED |
88
+ | COSMOS-E150 | Accounts can be configured with IP firewall, virtual network service endpoints and private endpoints. | <https://learn.microsoft.com/azure/cosmos-db/manage-with-powershell> | Create an Azure Cosmos DB account: "Azure Cosmos DB accounts can be configured with IP Firewall, Virtual Network service endpoints, and private endpoints." | 2026-11-08 | VERIFIED |
89
+ | COSMOS-E151 | Resource logs are captured per request and are also called data plane logs, covering operations such as delete, insert and readFeed. | <https://learn.microsoft.com/azure/cosmos-db/monitor-resource-logs> | Azure Cosmos DB resource logs: "Some examples of the data plane operations include delete, insert, and readFeed." | 2026-11-08 | VERIFIED |
90
+ | COSMOS-E152 | Data-plane logs are queried by the DataPlaneRequests category (CDBDataPlaneRequests table or AzureDiagnostics). | <https://learn.microsoft.com/azure/cosmos-db/monitor> | Analyze monitoring data: "To query for all data-plane logs from Azure Cosmos DB:" | 2026-11-08 | VERIFIED |
91
+ | COSMOS-E153 | Control-plane auditing uses the ControlPlaneRequests diagnostic log category. | <https://learn.microsoft.com/azure/cosmos-db/audit-control-plane-logs> | Enable diagnostic logs for control plane operations: "Select ControlPlaneRequests for log type and select the Send to Log Analytics option." | 2026-11-08 | VERIFIED |
92
+ | COSMOS-E154 | Disable key-based metadata write access before auditing control-plane operations so SDK-key clients cannot change resources unlogged. | <https://learn.microsoft.com/azure/cosmos-db/audit-control-plane-logs> | How to audit Azure Cosmos DB control plane operations: "Before you audit the control plane operations in Azure Cosmos DB, disable the key-based metadata write access on your account." | 2026-11-08 | VERIFIED |
93
+ | COSMOS-E201 | Azure Cosmos DB for MongoDB (RU) and Azure DocumentDB (with MongoDB compatibility, formerly vCore-based Azure Cosmos DB for MongoDB) are different services. This reference covers the RU-based account only. | <https://learn.microsoft.com/azure/documentdb/overview> | Naming and history: "Azure DocumentDB (with MongoDB compatibility) and Azure Cosmos DB for MongoDB (RU) are different services." | 2026-11-08 | VERIFIED |
94
+ | COSMOS-E202 | Azure DocumentDB was previously named vCore-based Azure Cosmos DB for MongoDB; the rename did not change existing clusters, connection strings or APIs. Its clusters are dedicated vCore-based clusters, whereas the RU service uses request-unit-based throughput. | <https://learn.microsoft.com/azure/documentdb/faq> | Frequently asked questions about Azure DocumentDB (with MongoDB compatibility): "Azure DocumentDB uses dedicated vCore-based clusters, and Azure Cosmos DB for MongoDB (RU) uses request-unit-based throughput." | 2026-11-08 | VERIFIED |
95
+ | COSMOS-E203 | Azure Cosmos DB for MongoDB (RU) implements the MongoDB wire protocol (Microsoft does not run MongoDB); the introduction page steers new MongoDB Query Language needs and migrations to Azure DocumentDB. | <https://learn.microsoft.com/azure/cosmos-db/mongodb/introduction> | What is Azure Cosmos DB for MongoDB?: "This API supports the MongoDB wire protocol, so you can use your existing MongoDB drivers, software development kits (SDKs), and tools." | 2026-11-08 | VERIFIED |
96
+ | COSMOS-E204 | Microsoft states that for migrating an existing MongoDB application or using MongoDB Query Language features, Azure DocumentDB should be considered instead of the RU-based API. | <https://learn.microsoft.com/azure/cosmos-db/mongodb/introduction> | What is Azure Cosmos DB for MongoDB?: "Are you looking to migrate an existing MongoDB application or use MongoDB Query Language (MQL) features?" | 2026-11-08 | VERIFIED |
97
+ | COSMOS-E205 | The Azure Cosmos DB account-level online backup article lists MongoDB among the APIs it applies to and defines two backup modes; continuous mode has 7-day, 30-day and 35-day tiers. | <https://learn.microsoft.com/azure/cosmos-db/online-backup-and-restore> | Backup modes: "This mode has three tiers: 7-day, 30-day, and 35-day retention." | 2026-11-08 | VERIFIED |
98
+ | COSMOS-E206 | Periodic mode is the default for all existing accounts: the interval can be as low as one hour, retention extends to a month at most, and restore is by support request. A continuous-mode account cannot be switched back to periodic. | <https://learn.microsoft.com/azure/cosmos-db/online-backup-and-restore> | Backup modes: "The maximum retention period extends to a month. The minimum backup interval can be one hour." | 2026-11-08 | VERIFIED |
99
+ | COSMOS-E207 | Periodic mode takes a full backup every 4 hours and keeps only the latest two by default; interval and retention can be changed in the Azure portal. | <https://learn.microsoft.com/azure/cosmos-db/periodic-backup-restore-introduction> | How Azure Cosmos DB performs data backup: "Azure Cosmos DB automatically takes a full backup of your database every 4 hours. At any point of time, only the latest two backups are stored by default." | 2026-11-08 | VERIFIED |
100
+ | COSMOS-E208 | Periodic mode backs up only the write region and a restore always creates a new single-region account in the write region of the source account. Keys, firewall, virtual network, data-plane RBAC and private endpoint settings, regions, stored procedures, triggers, UDFs, RBAC assignments, TTL-expired documents, analytical data and materialized views are not restored. | <https://learn.microsoft.com/azure/cosmos-db/periodic-backup-restore-introduction> | How Azure Cosmos DB performs data backup: "The restore action always restores data into a new account, which is located in the write region of the source account." | 2026-11-08 | VERIFIED |
101
+ | COSMOS-E209 | Periodic backups are stored in Blob storage in the write region and replicated to the paired region through geo-redundant storage; backups cannot be accessed directly and the Azure Cosmos DB team restores them on request. Periodic restore and retention changes are open to CosmosdbBackupOperator, owner or contributor principals; two backups are free and extra backups are charged for backup storage. | <https://learn.microsoft.com/azure/cosmos-db/periodic-backup-restore-introduction> | Understand the cost of backups: "Two backups are provided free and extra backups are charged according to the region-based pricing for backup storage" | 2026-11-08 | VERIFIED |
102
+ | COSMOS-E210 | In periodic mode the data is restored by creating a request with the support team. | <https://learn.microsoft.com/azure/cosmos-db/online-backup-and-restore> | Backup modes: "In this mode, backup is taken at a periodic interval and the data is restored by creating a request with the support team." | 2026-11-08 | VERIFIED |
103
+ | COSMOS-E211 | Continuous-mode point-in-time restore does not restore a subset of containers under a shared throughput database, firewall, virtual network, data-plane RBAC or private endpoint settings, the source regions, stored procedures, triggers, UDFs or RBAC assignments; they must be re-added after the restore. | <https://learn.microsoft.com/azure/cosmos-db/continuous-backup-restore-introduction> | What isn't restored?: "The following configurations aren't restored after the point-in-time recovery" | 2026-11-08 | VERIFIED |
104
+ | COSMOS-E212 | CONFLICT within the continuous-backup article: one section says deleted containers and databases can be restored into a new account or into an existing account, while a note in the next section says "The restore action always restores data into a new account." Treat the restore target as unresolved and confirm in the portal before relying on in-place restore. | <https://learn.microsoft.com/azure/cosmos-db/continuous-backup-restore-introduction> | What is restored into a new account?: "The restore action always restores data into a new account." | 2026-11-08 | CONFLICT |
105
+ | COSMOS-E213 | API for MongoDB accounts with continuous backup cannot create a unique index on an existing collection; unique indexes must be created with the collection through the create collection extension command. | <https://learn.microsoft.com/azure/cosmos-db/continuous-backup-restore-introduction> | Current limitations: "Azure Cosmos DB for MongoDB accounts with continuous backup don't support creating a unique index for an existing collection." | 2026-11-08 | VERIFIED |
106
+ | COSMOS-E214 | Continuous backups are stored in locally redundant storage blobs by default (zone-redundant in regions with zone redundancy) and the storage redundancy cannot be updated in continuous mode. | <https://learn.microsoft.com/azure/cosmos-db/continuous-backup-restore-introduction> | Backup storage redundancy: "By default, Azure Cosmos DB stores continuous mode backup data in locally redundant storage blobs." | 2026-11-08 | VERIFIED |
107
+ | COSMOS-E215 | Continuous backups are not automatically geo-disaster resistant; another region must be added explicitly for resiliency of the account and its backup. | <https://learn.microsoft.com/azure/cosmos-db/continuous-backup-restore-introduction> | Current limitations: "Another region should be explicitly added for resiliency of the account and the backup." | 2026-11-08 | VERIFIED |
108
+ | COSMOS-E216 | Continuous backup billing: 30-day and 35-day tiers are charged for backup storage, the 7-day tier is not, and every restore is charged regardless of tier. | <https://learn.microsoft.com/azure/cosmos-db/continuous-backup-restore-introduction> | Compare the continuous backup tiers: "The 30-day and 35-day tiers are charged for backup storage. The 7-day tier isn't charged for backup storage." | 2026-11-08 | VERIFIED |
109
+ | COSMOS-E217 | A restore into an account with lower RU/s or fewer partitions than the source is not possible, and restores across subscriptions are not possible. | <https://learn.microsoft.com/azure/cosmos-db/online-backup-and-restore> | Frequently asked questions: "You can't restore into an account with lower RU/s or fewer partitions." | 2026-11-08 | VERIFIED |
110
+ | COSMOS-E218 | Analytical store data (Synapse Link) is excluded from backups and restores; automatic backups are always on and the audit of backup mode can be done with Azure Resource Graph. | <https://learn.microsoft.com/azure/cosmos-db/online-backup-and-restore> | Frequently asked questions: "All Azure Cosmos DB accounts always have automatic backups." | 2026-11-08 | VERIFIED |
111
+ | COSMOS-E219 | Backups are managed entirely by the platform: restore, retention and redundancy changes are controlled by the account permission model and backups are not exposed to listing, deletion or disabling; backups kept under the retention policy cannot be altered, re-encrypted, deleted or disabled. | <https://learn.microsoft.com/azure/cosmos-db/online-backup-and-restore> | Immutability of Cosmos DB backups: "Cosmos DB backups are completely managed by the platform." | 2026-11-08 | VERIFIED |
112
+ | COSMOS-E220 | Backup data is encrypted with Microsoft-managed service keys and travels over a secure non-public network; for customer-managed-key accounts the backup is protected by envelope encryption. | <https://learn.microsoft.com/azure/cosmos-db/online-backup-and-restore> | Online backup and on-demand data restore in Azure Cosmos DB: "Azure Cosmos DB backups are encrypted with Microsoft-managed service keys." | 2026-11-08 | VERIFIED |
113
+ | COSMOS-E221 | The MongoDB API global distribution tutorial recommends adding regions based on Azure region pairs for business continuity and disaster recovery, and says adding regions has a cost. | <https://learn.microsoft.com/azure/cosmos-db/mongodb/tutorial-global-distribution> | Selecting global database regions: "For BCDR, it is recommended to add regions based on the region pairs" | 2026-11-08 | VERIFIED |
114
+ | COSMOS-E222 | Multi-region writes can be enabled on an API for MongoDB account (Replicate data globally pane) and are described as a true active-active setup in which data from the same shard can be written to multiple regions. | <https://learn.microsoft.com/azure/cosmos-db/mongodb/how-to-configure-multi-region-write> | Configure multi-region writes in Azure Cosmos DB for MongoDB: "Unlike other MongoDB services, Azure Cosmos DB for MongoDB enables you to write data from the same shard to multiple regions." | 2026-11-08 | VERIFIED |
115
+ | COSMOS-E223 | The account-level Reliability article (framed around Azure Cosmos DB for NoSQL, with no MongoDB applies-to marker) says service-managed failover is decided by Microsoft, may take one hour or more to trigger, and may lose unreplicated writes; a forced failover is the faster option. | <https://learn.microsoft.com/azure/cosmos-db/high-availability> | Service-managed failover: "the process of declaring an outage and triggering service-managed failover can take significant time - potentially one hour or more." | 2026-11-08 | VERIFIED |
116
+ | COSMOS-E224 | The same Reliability article gives an RPO for region outages in accounts with at least two regions that depends on consistency level: less than 15 minutes for Session, Consistent prefix and Eventual, K and T for Bounded staleness, and 0 for Strong. | <https://learn.microsoft.com/azure/cosmos-db/high-availability> | Potential data loss during region outages: "When you deploy an Azure Cosmos DB account in multiple regions, data durability depends on the consistency level you configure on the account." | 2026-11-08 | VERIFIED |
117
+ | COSMOS-E225 | For multiple-region accounts the minimum bounded-staleness K and T is 100,000 write operations or 300 seconds, which sets the minimum RPO under bounded staleness. | <https://learn.microsoft.com/azure/cosmos-db/high-availability> | Potential data loss during region outages: "For multiple-region accounts, the minimum value of K and T is 100,000 write operations or 300 seconds." | 2026-11-08 | VERIFIED |
118
+ | COSMOS-E226 | In the API for MongoDB the driver treats the write region as the primary replica and all other regions as read replicas; the write concern maps to the account default consistency level and read concerns map dynamically to Cosmos DB consistency levels. | <https://learn.microsoft.com/azure/cosmos-db/mongodb/consistency-mapping> | Consistency levels for Azure Cosmos DB and the API for MongoDB: "the MongoDB driver treats your write region as the primary replica and all other regions are read replica." | 2026-11-08 | VERIFIED |
119
+ | COSMOS-E227 | Billing dimension: provisioned throughput is billed hourly on the maximum throughput provisioned in the hour, in 100 RU/s increments (billing is for any portion of a wall-clock hour). | <https://learn.microsoft.com/azure/cosmos-db/understand-your-bill> | Understand your Azure Cosmos DB bill: "You are billed hourly for the maximum provisioned throughput for a given hour, in increments of 100 RU/s." | 2026-11-08 | VERIFIED |
120
+ | COSMOS-E228 | Billing dimension: storage is billed as a flat rate for the GB consumed by data and indexes in a given hour. | <https://learn.microsoft.com/azure/cosmos-db/understand-your-bill> | Understand your Azure Cosmos DB bill: "You are billed a flat rate for the total amount of storage (in GBs) consumed by your data and indexes for a given hour." | 2026-11-08 | VERIFIED |
121
+ | COSMOS-E229 | Billing dimension: adding or removing regions is allowed at any time, and throughput and storage are billed per region added. | <https://learn.microsoft.com/azure/cosmos-db/understand-your-bill> | Billing example: multi-region Azure Cosmos DB account, single region writes: "You can add/remove Azure regions anywhere in the world to your Azure Cosmos DB database account at any time." | 2026-11-08 | VERIFIED |
122
+ | COSMOS-E230 | Billing dimension: data replicated out of the write region is billed as egress at data transfer rates. | <https://learn.microsoft.com/azure/cosmos-db/understand-your-bill> | Billing example: multi-region Azure Cosmos DB account, single region writes: "You're billed for egress as per data transfer rates." | 2026-11-08 | VERIFIED |
123
+ | COSMOS-E231 | Azure Cosmos DB offers two capacity modes, provisioned throughput and serverless, and charges differ significantly between them (account-level cost article, no MongoDB applies-to marker; serverless availability for the MongoDB API was not separately confirmed in this pass). | <https://learn.microsoft.com/azure/cosmos-db/plan-manage-costs> | Provisioned throughput or serverless: "Azure Cosmos DB is available in two different capacity modes: provisioned throughput and serverless." | 2026-11-08 | VERIFIED |
124
+ | COSMOS-E232 | The Cost Estimator is documented for the API for MongoDB and maps find, insert, update, delete and aggregate operations to Reads, Writes, Updates, Deletes and Queries; it is in public preview and its output is an estimate, not a quote. | <https://learn.microsoft.com/azure/cosmos-db/mongodb/estimate-ru-capacity-planner> | Estimate RU/s using the Azure Cosmos DB Cost Estimator - Azure Cosmos DB for MongoDB: "This article describes how to use the Azure Cosmos DB Cost Estimator to get an estimate of the required RU/s and cost of your workload" | 2026-11-08 | VERIFIED |
125
+ | COSMOS-E233 | Request charge is measured in RUs for every API, including the API for MongoDB, and can be read after an operation with the getLastRequestStatistics command or in the Data Explorer query stats. | <https://learn.microsoft.com/azure/cosmos-db/mongodb/find-request-unit-charge> | Find the request unit charge for operations executed in Azure Cosmos DB for MongoDB: "No matter which API you use to interact with your Azure Cosmos DB container, costs are always measured by RUs." | 2026-11-08 | VERIFIED |
126
+ | COSMOS-E234 | Azure Monitor platform metrics for Azure Cosmos DB include MongoRequests (Mongo Requests) and MongoRequestCharge (Mongo Request Charge), alongside NormalizedRUConsumption, TotalRequests, TotalRequestUnits, ProvisionedThroughput, DataUsage, IndexUsage, DocumentCount, ReplicationLatency and ServiceAvailability. The data reference page is marked NoSQL-applicable but lists the Mongo metrics explicitly. | <https://learn.microsoft.com/azure/cosmos-db/monitor-reference> | Metrics by category: "The following tables list Azure Cosmos DB metrics categorized by metric type." | 2026-11-08 | VERIFIED |
127
+ | COSMOS-E235 | The MongoRequests resource-log category writes to the CDBMongoRequests table and covers data plane operations for Mongo API accounts. | <https://learn.microsoft.com/azure/cosmos-db/monitor-reference> | Resource logs: "This table details data plane operations, specifically for Mongo API accounts." | 2026-11-08 | VERIFIED |
128
+ | COSMOS-E236 | PartitionKeyRUConsumption (CDBPartitionKeyRUConsumption) records RU consumption per logical partition key within each physical partition and can be used to identify hot partitions; PartitionKeyStatistics reports approximate outlier partition keys by storage. | <https://learn.microsoft.com/azure/cosmos-db/monitor-reference> | Resource logs: "This data can be used to identify hot partitions from a request volume perspective." | 2026-11-08 | VERIFIED |
129
+ | COSMOS-E237 | Diagnostic settings can send resource logs to Log Analytics, Storage or Event Hubs; example Kusto queries exist for the API for MongoDB (CDBMongoRequests with RequestCharge, DurationMs, RateLimitingDelayMs, ErrorCode 429 or 16500 throttling and ErrorCode 50 timeouts). | <https://learn.microsoft.com/azure/cosmos-db/mongodb/diagnostic-queries> | Troubleshoot issues with advanced diagnostics queries with Azure Cosmos DB for MongoDB: "Requests throttled (statusCode = 429 or 16500) in a specific time window" | 2026-11-08 | VERIFIED |
130
+ | COSMOS-E238 | Azure Monitor alerts can be created on any metric or log data source; the partitioning article recommends Azure Monitor alerts to watch for logical partition size approaching 20 GB. No MongoDB-specific alert list was found. | <https://learn.microsoft.com/azure/cosmos-db/partitioning-overview> | Logical partitions: "Use Azure Monitor Alerts to monitor whether a logical partition's size is approaching 20 GB" | 2026-11-08 | VERIFIED |
131
+ | COSMOS-E239 | Throttling in the API for MongoDB surfaces as error 16500 (TooManyRequests) when the RUs consumed exceed the collection provisioned rate; remedies are scaling throughput, retrying, or server-side retry. | <https://learn.microsoft.com/azure/cosmos-db/mongodb/error-codes-solutions> | Common errors and solutions: "The total number of request units consumed is more than the provisioned request-unit rate for the collection and has been throttled." | 2026-11-08 | VERIFIED |
132
+ | COSMOS-E240 | Error 50 (ExceededTimeLimit) means a request ran past the 60-second timeout; insufficient RUs is one documented cause, and retrying a write after this error may create a duplicate write. | <https://learn.microsoft.com/azure/cosmos-db/mongodb/error-codes-solutions> | Common errors and solutions: "The request has exceeded the timeout of 60 seconds of execution." | 2026-11-08 | VERIFIED |
133
+ | COSMOS-E241 | Multi-document transactions fail with error 2 (Transaction is not active) when they exceed a fixed 5-second time limit. | <https://learn.microsoft.com/azure/cosmos-db/mongodb/error-codes-solutions> | Common errors and solutions: "The multi-document transaction surpassed the fixed 5-second time limit." | 2026-11-08 | VERIFIED |
134
+ | COSMOS-E242 | Server-side retry (SSR) automates retries of rate-limited MongoDB operations; it is enabled with the DisableRateLimitingResponses capability (up to 15 minutes to apply), retries up to a 60-second timeout after which the client gets ExceededTimeLimit (50), and its effect is visible in resource logs through estimatedDelayFromRateLimitingInMilliseconds. | <https://learn.microsoft.com/azure/cosmos-db/mongodb/prevent-rate-limiting-errors> | Prevent rate-limiting errors for Azure Cosmos DB for MongoDB operations: "Enable Server Side Retry (SSR) to automate operation retries." | 2026-11-08 | VERIFIED |
135
+ | COSMOS-E243 | Each physical partition provides up to 10,000 RU/s and each logical partition maps to one physical partition, so a logical partition is also limited to 10,000 RU/s. | <https://learn.microsoft.com/azure/cosmos-db/partitioning-overview> | Physical partitions: "The 10,000 RU/s limit for physical partitions implies that logical partitions also have a 10,000 RU/s limit" | 2026-11-08 | VERIFIED |
136
+ | COSMOS-E244 | Each logical partition can store up to 20 GB of data; hierarchical partition keys are the documented option for keys that exceed it. | <https://learn.microsoft.com/azure/cosmos-db/partitioning-overview> | Logical partitions: "Each logical partition can store up to 20 GB of data." | 2026-11-08 | VERIFIED |
137
+ | COSMOS-E245 | Choosing a partition key that distributes throughput consumption evenly across logical partitions is the documented way to avoid hot partitions; physical partitions are not controllable. | <https://learn.microsoft.com/azure/cosmos-db/partitioning-overview> | Physical partitions: "Choosing a partition key that evenly distributes throughput consumption across logical partitions ensures balanced" | 2026-11-08 | VERIFIED |
138
+ | COSMOS-E246 | A container or shared throughput database on manual throughput needs at least 400 RU/s, and the minimum rises with storage and with the highest throughput ever provisioned. | <https://learn.microsoft.com/azure/cosmos-db/concepts-limits> | Minimum throughput limits: "An Azure Cosmos DB container (or shared throughput database) using manual throughput must have a minimum throughput of 400 RU/s." | 2026-11-08 | VERIFIED |
139
+ | COSMOS-E247 | MongoDB API specific limits: 60 seconds maximum execution time for MongoDB operations on server versions 3.6 and 4.0, a 6-level nesting limit in index definitions, a 30-minute server-side idle connection timeout, and documents up to 16 MB that need feature enablement in the Azure portal. | <https://learn.microsoft.com/azure/cosmos-db/concepts-limits> | API for MongoDB-specific limits: "Large document sizes up to 16 MB require feature enablement in the Azure portal." | 2026-11-08 | VERIFIED |
140
+ | COSMOS-E248 | Set the driver idle connection timeout to 2-3 minutes because the default Azure Load Balancer timeout is 4 minutes. | <https://learn.microsoft.com/azure/cosmos-db/concepts-limits> | API for MongoDB-specific limits: "Set the idle connection timeout in the driver settings to 2-3 minutes because the default timeout for Azure LoadBalancer is 4 minutes" | 2026-11-08 | VERIFIED |
141
+ | COSMOS-E249 | Azure Cosmos DB for MongoDB has a built-in role-based access control system for data plane operations (versions 3.6 or higher), enabled per account with the EnableMongoRoleBasedAccessControl capability. | <https://learn.microsoft.com/azure/cosmos-db/mongodb/how-to-setup-rbac> | Configure role-based access control in Azure Cosmos DB for MongoDB: "Azure Cosmos DB for MongoDB provides a built-in role-based access control system for data plane operations." | 2026-11-08 | VERIFIED |
142
+ | COSMOS-E250 | Data-plane least privilege is expressed with custom roles (privileges on a database and collection with actions such as insert and find) assigned to users created with az cosmosdb mongodb role definition and user definition commands; users authenticate with SCRAM-SHA-256. | <https://learn.microsoft.com/azure/cosmos-db/mongodb/how-to-setup-rbac> | Create roles and users: "Define custom roles and users to control access to your database account." | 2026-11-08 | VERIFIED |
143
+ | COSMOS-E251 | Control-plane built-in role Cosmos DB Operator manages Azure Cosmos DB accounts but not data, and prevents access to account keys and connection strings. | <https://learn.microsoft.com/azure/role-based-access-control/built-in-roles/databases> | Cosmos DB Operator: "Lets you manage Azure Cosmos DB accounts, but not access data in them. Prevents access to account keys and connection strings." | 2026-11-08 | VERIFIED |
144
+ | COSMOS-E252 | Other control-plane built-in roles: DocumentDB Account Contributor can manage Azure Cosmos DB accounts, and Cosmos DB Account Reader Role can read account data. | <https://learn.microsoft.com/azure/role-based-access-control/built-in-roles/databases> | DocumentDB Account Contributor: "Can manage Azure Cosmos DB accounts. Azure Cosmos DB is formerly known as DocumentDB." | 2026-11-08 | VERIFIED |
145
+ | COSMOS-E253 | Backup-related built-in roles: CosmosBackupOperator can submit a restore request for a database or container, and CosmosRestoreOperator can perform the restore action for an account with continuous backup mode. | <https://learn.microsoft.com/azure/role-based-access-control/built-in-roles/databases> | CosmosRestoreOperator: "Can perform restore action for Cosmos DB database account with continuous backup mode" | 2026-11-08 | VERIFIED |
146
+ | COSMOS-E254 | Setting disableKeyBasedMetadataWriteAccess to true blocks create or update of resources through account keys so changes must come from a principal with an Azure role through Azure Resource Manager, CLI, PowerShell or the portal. | <https://learn.microsoft.com/azure/cosmos-db/audit-control-plane-logs> | Disable key based metadata write access: "When key based metadata write access is disabled, clients connecting to the Azure Cosmos DB account through account keys are prevented from accessing the account." | 2026-11-08 | VERIFIED |
147
+ | COSMOS-E255 | The MongoDB account creation walkthrough has a Tags tab: tags are name/value pairs used to categorize resources and view consolidated billing across resources and resource groups. | <https://learn.microsoft.com/azure/cosmos-db/mongodb/connect-using-mongoose> | Create an Azure Cosmos DB account: "Tags are name/value pairs that enable you to categorize resources and view consolidated billing by applying the same tag to multiple resources and resource groups." | 2026-11-08 | VERIFIED |
148
+ | COSMOS-E256 | Microsoft advises not to place personal, sensitive or confidential information in resource names or resource tags for MongoDB collections because those fields are not treated as customer data. | <https://learn.microsoft.com/azure/cosmos-db/mongodb/how-to-create-container> | Create using Azure portal: "Don't include any personal, sensitive, or confidential information in resource names (for example, table name, database name) and resource tags." | 2026-11-08 | VERIFIED |
149
+ | COSMOS-E257 | Encryption at rest is always on with no control to turn it off, uses AES-256 in all regions, and applies to databases, media attachments and backups using Microsoft-managed (service-managed) keys. | <https://learn.microsoft.com/azure/cosmos-db/database-encryption-at-rest> | Data encryption in Azure Cosmos DB: "encryption at rest is "on" by default. There are no controls to turn it off or on." | 2026-11-08 | VERIFIED |
150
+ | COSMOS-E258 | Data is encrypted in transit over the network and at rest, giving end-to-end encryption. | <https://learn.microsoft.com/azure/cosmos-db/database-encryption-at-rest> | Data encryption in Azure Cosmos DB: "Your data is now encrypted in transit (over the network) and at rest (nonvolatile storage), giving you end-to-end encryption." | 2026-11-08 | VERIFIED |
151
+ | COSMOS-E259 | Customer-managed keys (CMK) add a second layer of encryption on top of service-managed keys, with keys stored in Azure Key Vault; one key per account is used to encrypt all data in that account. | <https://learn.microsoft.com/azure/cosmos-db/how-to-setup-cmk> | Configure customer-managed keys for your Azure Cosmos DB account with Azure Key Vault: "Optionally, you can choose to add a second layer of encryption with keys you manage" | 2026-11-08 | VERIFIED |
152
+ | COSMOS-E260 | The Key Vault must have Soft Delete and Purge Protection enabled; it must be reachable by public network access or allow trusted Microsoft services to bypass its firewall, and a vault reachable only through private endpoints cannot host the keys. | <https://learn.microsoft.com/azure/cosmos-db/how-to-setup-cmk> | Configure your Azure Key Vault instance: "An instance that is exclusively accessible through private endpoints can't be used to host your customer-managed keys." | 2026-11-08 | VERIFIED |
153
+ | COSMOS-E261 | CONFLICT: the encryption-at-rest FAQ says CMK is available for new accounts and should be deployed at account creation, while the CMK article references a procedure to enable customer-managed keys on existing accounts. Treat enabling CMK on an existing account as documented only by the CMK article and re-check it before relying on it. | <https://learn.microsoft.com/azure/cosmos-db/database-encryption-at-rest> | Frequently asked questions: "Yes, this feature is available for new Azure Cosmos DB accounts. It should be deployed at the time of account creation." | 2026-11-08 | CONFLICT |
154
+ | COSMOS-E262 | When restoring a continuous-backup account that uses CMK, a user-assigned identity is required in the restore request because the source account managed identity cannot be carried over to the target account. | <https://learn.microsoft.com/azure/cosmos-db/how-to-setup-cmk> | Restore a continuous account that is configured with managed identity: "A user-assigned identity is required in the restore request because the source account managed identity (user-assigned and system-assigned identities) can't be carried over automatically to the target database account." | 2026-11-08 | VERIFIED |
155
+ | COSMOS-E263 | By default an account is reachable from the internet with a valid authorization token; the IP firewall restricts it, and for API for MongoDB accounts with IP firewall rules the Data Explorer client IP must be added to the allowed list. | <https://learn.microsoft.com/azure/cosmos-db/how-to-configure-firewall> | Configure an IP firewall by using the Azure portal: "you must add the client IP address or IP range used to access Data Explorer to the account" | 2026-11-08 | VERIFIED |
156
+ | COSMOS-E264 | The Mongo shell and Cassandra shell integrations in Data Explorer are not supported with virtual network access. | <https://learn.microsoft.com/azure/cosmos-db/how-to-configure-vnet-service-endpoint> | Frequently asked questions: "Currently, the Mongo shell and Cassandra shell integrations in the Azure Cosmos DB Data Explorer aren't supported with virtual network access." | 2026-11-08 | VERIFIED |
157
+ | COSMOS-E265 | Private endpoints (group ID MongoDB, private DNS zone privatelink.mongo.cosmos.azure.com) are supported for API for MongoDB accounts on server version 3.6 or higher but not for accounts on 3.2 with documents.azure.com endpoints. | <https://learn.microsoft.com/azure/cosmos-db/how-to-configure-private-endpoints> | Current limitations: "a private endpoint is supported for accounts on server version 3.6 or higher" | 2026-11-08 | VERIFIED |
158
+ | COSMOS-E266 | With Private Link, MongoDB tools and libraries must support Service Name Identification (SNI) or pass the appName parameter from the connection string. | <https://learn.microsoft.com/azure/cosmos-db/how-to-configure-private-endpoints> | Current limitations: "tools and libraries must support Service Name Identification (SNI) or pass the appName parameter from the connection string to properly connect." | 2026-11-08 | VERIFIED |
159
+ | COSMOS-E267 | Setting the publicNetworkAccess flag to Disabled at account creation blocks all public and virtual network traffic and takes precedence over IP or virtual network rules. | <https://learn.microsoft.com/azure/cosmos-db/how-to-configure-private-endpoints> | Blocking public network access during account creation: "This flag takes precedence over any IP or virtual network rule." | 2026-11-08 | VERIFIED |
160
+ | COSMOS-E268 | Adding a private endpoint to an existing account causes about five minutes of downtime unless IP or virtual network rules are added first to allow client connections. | <https://learn.microsoft.com/azure/cosmos-db/how-to-configure-private-endpoints> | Add private endpoints to an existing Azure Cosmos DB account with no downtime: "By default, adding a private endpoint to an existing account results in a short downtime of approximately five minutes." | 2026-11-08 | VERIFIED |
161
+ | COSMOS-E269 | Control plane operations are logged to the ControlPlaneRequests diagnostic category sent to Log Analytics, Storage or Event Hubs. | <https://learn.microsoft.com/azure/cosmos-db/audit-control-plane-logs> | Enable diagnostic logs for control plane operations: "Select ControlPlaneRequests for log type and select the Send to Log Analytics option." | 2026-11-08 | VERIFIED |
162
+ | COSMOS-E270 | Database and collection level control plane operations for the API for MongoDB (Mongo Database and Collection created, updated, throughput updated, deleted) are listed among the operations available as Azure Monitor metrics. | <https://learn.microsoft.com/azure/cosmos-db/audit-control-plane-logs> | Control plane operations for database or containers: "The following are the control plane operations available at the database and container level." | 2026-11-08 | VERIFIED |
163
+ | COSMOS-E271 | The CDBMongoRequests table records Mongo API data plane requests with operation name, RequestCharge, DurationMs, ErrorCode and client address; the command text (PIICommandText) is logged only if opted in. | <https://learn.microsoft.com/azure/azure-monitor/reference/tables/cdbmongorequests> | Columns: "Full text query (if opted in) for this Mongo API request." | 2026-11-08 | VERIFIED |
164
+ | COSMOS-E301 | Azure Cosmos DB for Apache Cassandra is a fully managed Azure Cosmos DB API that supports CQL and existing Cassandra drivers; it runs on the Azure Cosmos DB engine, not on Apache Cassandra nodes. | <https://learn.microsoft.com/azure/cosmos-db/cassandra/introduction> | What is Azure Cosmos DB for Apache Cassandra?: "Azure Cosmos DB for Apache Cassandra is a fully managed NoSQL database service that enables you to run Cassandra workloads in the cloud with minimal changes to your application code." | 2026-11-08 | VERIFIED |
165
+ | COSMOS-E302 | Microsoft distinguishes Azure Managed Instance for Apache Cassandra as a separate first-party service that hosts pure open-source Apache Cassandra clusters with full native platform compatibility, recommended for lift-and-shift migrations. | <https://learn.microsoft.com/azure/cosmos-db/cassandra/introduction> | Azure Managed Instance for Apache Cassandra: "Azure Managed Instance for Apache Cassandra is a first-party Azure service for hosting and maintaining pure open-source Apache Cassandra clusters with full native platform compatibility." | 2026-11-08 | VERIFIED |
166
+ | COSMOS-E303 | Azure Managed Instance for Apache Cassandra is a separate service whose datacenters are virtual machine scale sets placed in a virtual network and priced per instance; its operations (nodetool repair, patching, snapshot backups, scaling) are not those of the Azure Cosmos DB API. | <https://learn.microsoft.com/azure/managed-instance-apache-cassandra/introduction> | Azure Managed Instance for Apache Cassandra: "The pricing model is flexible, on-demand, instance-based, and has no licensing fees." | 2026-11-08 | VERIFIED |
167
+ | COSMOS-E304 | Azure Managed Instance for Apache Cassandra emits node metrics that can go to Prometheus or Grafana and integrates with Azure Monitor for metrics and diagnostic logging, a monitoring surface separate from the Cosmos DB API account. | <https://learn.microsoft.com/azure/managed-instance-apache-cassandra/introduction> | Key benefits: "The service is also integrated with Azure Monitor for metrics and diagnostic logging" | 2026-11-08 | VERIFIED |
168
+ | COSMOS-E305 | Point-in-time (continuous) backup is documented for the NoSQL, MongoDB, Gremlin and Table APIs; the same page states the API for Cassandra is not supported for continuous backup. | <https://learn.microsoft.com/azure/cosmos-db/continuous-backup-restore-introduction> | Current limitations: "Azure Cosmos DB APIs for SQL, MongoDB, Gremlin, and Table supported for continuous backup. API for Cassandra isn't supported now." | 2026-11-08 | VERIFIED |
169
+ | COSMOS-E306 | The online backup article lists Apache Cassandra among the APIs it applies to; periodic mode is the default backup mode for all existing accounts and the maximum retention extends to a month with a minimum interval of one hour. | <https://learn.microsoft.com/azure/cosmos-db/online-backup-and-restore> | Backup modes: "This mode is the default backup mode for all existing accounts." | 2026-11-08 | VERIFIED |
170
+ | COSMOS-E307 | The periodic backup article (applies-to lists Apache Cassandra) states a full backup every 4 hours with only the latest two kept by default; interval and retention can be changed in the Azure portal; deleted containers or shared-throughput databases keep their snapshots for 30 days. | <https://learn.microsoft.com/azure/cosmos-db/periodic-backup-restore-introduction> | How Azure Cosmos DB performs data backup: "Azure Cosmos DB automatically takes a full backup of your database every 4 hours. At any point of time, only the latest two backups are stored by default." | 2026-11-08 | VERIFIED |
171
+ | COSMOS-E308 | Periodic backups are taken only in the write region, stored in Blob storage and replicated by geo-redundant storage; a restore always creates a new single-region account in the source write region and is performed by the Azure Cosmos DB team on request. | <https://learn.microsoft.com/azure/cosmos-db/periodic-backup-restore-introduction> | How Azure Cosmos DB performs data backup: "The restore action always restores data into a new account, which is located in the write region of the source account." | 2026-11-08 | VERIFIED |
172
+ | COSMOS-E309 | Not restored from a periodic backup: account keys, firewall, virtual network, data-plane RBAC and private endpoint settings, regions, stored procedures, triggers, UDFs, RBAC assignments, TTL-expired documents, analytical data and materialized views. | <https://learn.microsoft.com/azure/cosmos-db/periodic-backup-restore-introduction> | What isn't restored?: "The following configurations aren't restored after the point-in-time recovery" | 2026-11-08 | VERIFIED |
173
+ | COSMOS-E310 | Principals in the CosmosdbBackupOperator role, owners and contributors can request a restore or change retention; two backups are free and extra backups are charged at regional backup storage rates. | <https://learn.microsoft.com/azure/cosmos-db/periodic-backup-restore-introduction> | Understand the cost of backups: "Two backups are provided free and extra backups are charged according to the region-based pricing for backup storage" | 2026-11-08 | VERIFIED |
174
+ | COSMOS-E311 | Analytical store data is excluded from backup and restore, and restores cannot target an account with lower RU/s or fewer partitions, or a different subscription. | <https://learn.microsoft.com/azure/cosmos-db/online-backup-and-restore> | Frequently asked questions: "You can't restore into an account with lower RU/s or fewer partitions." | 2026-11-08 | VERIFIED |
175
+ | COSMOS-E312 | Backups are platform managed and immutable under the retention policy (not alterable, re-encrypted, deleted or disabled) and cannot be listed, deleted or disabled by customers. | <https://learn.microsoft.com/azure/cosmos-db/online-backup-and-restore> | Immutability of Cosmos DB backups: "Cosmos DB backups are completely managed by the platform." | 2026-11-08 | VERIFIED |
176
+ | COSMOS-E313 | Cassandra CREATE KEYSPACE options for region, class, replication_factor and datacenter are ignored; regions are added at the account level, and every region keeps a replica set of four replicas that cannot be modified. | <https://learn.microsoft.com/azure/cosmos-db/cassandra/cassandra-support> | Keyspace and Table options: "In every region, Azure Cosmos DB replicates the data across the replica set that is made up of four replicas and this replica set configuration can't be modified." | 2026-11-08 | VERIFIED |
177
+ | COSMOS-E314 | The write consistency level of Apache Cassandra is mapped to the account default consistency level and cannot be changed per request; read consistency is mapped dynamically per read request. | <https://learn.microsoft.com/azure/cosmos-db/cassandra/consistency-mapping> | Multi-region writes vs single-region writes: "The write consistency level of Apache Cassandra is mapped to the default consistency level configured on your Azure Cosmos DB account." | 2026-11-08 | VERIFIED |
178
+ | COSMOS-E315 | With single-region writes an account can keep strong consistency and still have high availability across regions with service-managed failover. | <https://learn.microsoft.com/azure/cosmos-db/cassandra/consistency-mapping> | Multi-region writes vs single-region writes: "With single-region writes, you can maintain strong consistency, while still maintaining a level of high availability across regions with" | 2026-11-08 | VERIFIED |
179
+ | COSMOS-E316 | An account with multiple write regions cannot be configured for strong consistency, and the API for Cassandra adoption guide states a distributed system cannot provide an RPO of zero and an RTO of zero. | <https://learn.microsoft.com/azure/cosmos-db/cassandra/cassandra-adoption> | Multi-region deployments: "A distributed system can't provide an RPO of zero and a Recovery Time Objective (RTO) of zero." | 2026-11-08 | VERIFIED |
180
+ | COSMOS-E317 | Lightweight transactions are not supported on accounts with multiple region writes enabled. | <https://learn.microsoft.com/azure/cosmos-db/cassandra/cassandra-support> | Lightweight Transactions (LWT): "Lightweight transactions currently aren't supported for accounts that have multiple region writes enabled." | 2026-11-08 | VERIFIED |
181
+ | COSMOS-E318 | The account-level Reliability article (framed around the API for NoSQL, no Apache Cassandra marker) says Microsoft decides when service-managed failover occurs, it can take an hour or more, and unreplicated writes can be lost. | <https://learn.microsoft.com/azure/cosmos-db/high-availability> | Service-managed failover: "the process of declaring an outage and triggering service-managed failover can take significant time - potentially one hour or more." | 2026-11-08 | VERIFIED |
182
+ | COSMOS-E319 | The same Reliability article gives an RPO table for accounts in at least two regions by consistency level: under 15 minutes for Session, Consistent prefix and Eventual, K and T for Bounded staleness, 0 for Strong. It is not stated per API. | <https://learn.microsoft.com/azure/cosmos-db/high-availability> | Potential data loss during region outages: "When you deploy an Azure Cosmos DB account in multiple regions, data durability depends on the consistency level you configure on the account." | 2026-11-08 | VERIFIED |
183
+ | COSMOS-E320 | Billing dimension (account-level article, not API-specific): provisioned throughput is billed hourly on the maximum RU/s in the hour in 100 RU/s steps. | <https://learn.microsoft.com/azure/cosmos-db/understand-your-bill> | Understand your Azure Cosmos DB bill: "You are billed hourly for the maximum provisioned throughput for a given hour, in increments of 100 RU/s." | 2026-11-08 | VERIFIED |
184
+ | COSMOS-E321 | Billing dimension: storage is billed on GB consumed by data and indexes per hour. | <https://learn.microsoft.com/azure/cosmos-db/understand-your-bill> | Understand your Azure Cosmos DB bill: "You are billed a flat rate for the total amount of storage (in GBs) consumed by your data and indexes for a given hour." | 2026-11-08 | VERIFIED |
185
+ | COSMOS-E322 | Billing dimension: each added region carries its own throughput and storage and replication egress is billed at data transfer rates. | <https://learn.microsoft.com/azure/cosmos-db/understand-your-bill> | Billing example: multi-region Azure Cosmos DB account, single region writes: "You're billed for egress as per data transfer rates." | 2026-11-08 | VERIFIED |
186
+ | COSMOS-E323 | Keyspaces and tables take a cosmosdb_provisioned_throughput option with a minimum of 400 RU/s; keyspace throughput is shared across tables. | <https://learn.microsoft.com/azure/cosmos-db/cassandra/cassandra-support> | Keyspace and Table options: "The Keyspace throughput allows sharing throughput across multiple tables." | 2026-11-08 | VERIFIED |
187
+ | COSMOS-E324 | Autoscale provisioned throughput is available for the API for Cassandra and can be set with CQL (cosmosdb_autoscale_max_throughput) at keyspace or table level. | <https://learn.microsoft.com/azure/cosmos-db/cassandra/scale-account-throughput> | Manage scaling: "In addition to standard (manual) or programmatic ways of provisioning throughput, you can also configure Azure Cosmos DB containers in autoscale provisioned throughput." | 2026-11-08 | VERIFIED |
188
+ | COSMOS-E325 | Capacity is expressed as request units; the adoption guide recommends profiling every request to estimate the RUs to provision. | <https://learn.microsoft.com/azure/cosmos-db/cassandra/cassandra-adoption> | Request units: "We highly recommend that you profile your requests." | 2026-11-08 | VERIFIED |
189
+ | COSMOS-E326 | Azure Monitor metrics for the API for Cassandra are CassandraRequests, CassandraRequestCharges and CassandraConnectionClosures, besides the shared metrics (TotalRequestUnits, NormalizedRUConsumption, ProvisionedThroughput, DataUsage, IndexUsage, ServiceAvailability). | <https://learn.microsoft.com/azure/cosmos-db/monitor-reference> | Metrics by category: "The following tables list Azure Cosmos DB metrics categorized by metric type." | 2026-11-08 | VERIFIED |
190
+ | COSMOS-E327 | The data plane resource-log table for this API is CDBCassandraRequests (category CassandraRequests). | <https://learn.microsoft.com/azure/cosmos-db/cassandra/error-codes-solution> | Explore Data Plane Operations: "Use the CDBCassandraRequests table to see data plane operations specifically for your API for Cassandra account." | 2026-11-08 | VERIFIED |
191
+ | COSMOS-E328 | CDBPartitionKeyRUConsumption gives RU consumption for logical keys per region within each physical partition, used to find hot partition keys. | <https://learn.microsoft.com/azure/cosmos-db/cassandra/error-codes-solution> | Troubleshoot Query Consumption: "The CDBPartitionKeyRUConsumption table contains details on request unit (RU) consumption for logical keys in each region within each of their physical partitions." | 2026-11-08 | VERIFIED |
192
+ | COSMOS-E329 | The monitoring reference has an Error codes for Cassandra table for the API for Cassandra account. | <https://learn.microsoft.com/azure/cosmos-db/monitor-reference> | Error codes for Cassandra: "The following table lists error codes for your API for Cassandra account." | 2026-11-08 | VERIFIED |
193
+ | COSMOS-E330 | Azure Monitor alerts can be defined on any metric or log source; no Cassandra-specific recommended alert list was found. | <https://learn.microsoft.com/azure/cosmos-db/monitor> | Alerts: "Azure Monitor alerts proactively notify you when specific conditions are found in your monitoring data." | 2026-11-08 | VERIFIED |
194
+ | COSMOS-E331 | Rate-limited requests that server-side retry handled can be seen as 429 in the Metrics pane and in resource logs via estimatedDelayFromRateLimitingInMilliseconds. | <https://learn.microsoft.com/azure/cosmos-db/cassandra/prevent-rate-limiting-errors> | Frequently asked questions: "You can view the rate limiting errors (429) that are retried server-side in the Azure Cosmos DB Metrics pane." | 2026-11-08 | VERIFIED |
195
+ | COSMOS-E332 | Operations fail with OverloadedException or 429 when they exceed a table throughput limit; the API translates rate limiting into overloaded errors on the Cassandra native protocol. | <https://learn.microsoft.com/azure/cosmos-db/cassandra/prevent-rate-limiting-errors> | Prevent rate-limiting errors for Azure Cosmos DB for Apache Cassandra operations: "Azure Cosmos DB for Apache Cassandra operations may fail with rate-limiting (OverloadedException/429) errors" | 2026-11-08 | VERIFIED |
196
+ | COSMOS-E333 | Server-side retry (account level, all keyspaces and tables) is enabled with the DisableRateLimitingResponses capability alongside EnableCassandra (up to 15 minutes to apply); requests are retried until a 60-second time-out, after which the client gets a read or write time-out. | <https://learn.microsoft.com/azure/cosmos-db/cassandra/prevent-rate-limiting-errors> | Frequently asked questions: "Requests are retried continuously (over and over again) until a 60-second time-out is reached." | 2026-11-08 | VERIFIED |
197
+ | COSMOS-E334 | Server-side retry helps for short spikes under a minute; persistent overload needs more RU/s, and the client read time-out should exceed the 60-second server retry window (90 seconds recommended). | <https://learn.microsoft.com/azure/cosmos-db/cassandra/prevent-rate-limiting-errors> | Frequently asked questions: "Server-side retry (SSR) is most beneficial when there's a sudden spike for a short duration of less than 1 minute" | 2026-11-08 | VERIFIED |
198
+ | COSMOS-E335 | Cassandra partition limits in the API: up to 20 GB per logical partition and up to 30 GB of data per physical partition; a replication factor of 4 (quorum of 3) is always used. | <https://learn.microsoft.com/azure/cosmos-db/cassandra/cassandra-partitioning> | Differences between Apache Cassandra and Azure Cosmos DB: "The API for Cassandra for Azure Cosmos DB allows up to 20 GB per logical partition, and up to 30GB of data per physical partition." | 2026-11-08 | VERIFIED |
199
+ | COSMOS-E336 | Each physical partition delivers up to 10,000 RU/s, so a logical partition is also limited to 10,000 RU/s; choose a key that spreads consumption evenly. | <https://learn.microsoft.com/azure/cosmos-db/partitioning-overview> | Physical partitions: "The 10,000 RU/s limit for physical partitions implies that logical partitions also have a 10,000 RU/s limit" | 2026-11-08 | VERIFIED |
200
+ | COSMOS-E337 | OverloadException (429) is thrown when the request rate is too great, typically because too little throughput is provisioned for the table. | <https://learn.microsoft.com/azure/cosmos-db/cassandra/troubleshoot-nohostavailable-exception> | Exception messages: "OverloadException is thrown when the request rate is too great" | 2026-11-08 | VERIFIED |
201
+ | COSMOS-E338 | The gc_grace_seconds value must be zero if specified. | <https://learn.microsoft.com/azure/cosmos-db/cassandra/cassandra-support> | Keyspace and Table options: "All the options are ignored when creating the table, except gc_grace_seconds" | 2026-11-08 | VERIFIED |
202
+ | COSMOS-E339 | Azure RBAC covers provisioning, key rotation, metrics and the read-write and read-only passwords or keys obtained from the portal. | <https://learn.microsoft.com/azure/cosmos-db/cassandra/cassandra-support> | Permission and role management: "Azure Cosmos DB supports Azure role-based access control (Azure RBAC) for provisioning, rotating keys, viewing metrics and read-write and read-only passwords/keys" | 2026-11-08 | VERIFIED |
203
+ | COSMOS-E340 | Azure Cosmos DB does not support roles for CRUD activities in the API for Cassandra, so there is no per-keyspace data-plane role model. | <https://learn.microsoft.com/azure/cosmos-db/cassandra/cassandra-support> | Permission and role management: "Azure Cosmos DB doesn't support roles for CRUD activities." | 2026-11-08 | VERIFIED |
204
+ | COSMOS-E341 | Control-plane built-in role Cosmos DB Operator manages Azure Cosmos DB accounts but not data and prevents access to account keys and connection strings. | <https://learn.microsoft.com/azure/role-based-access-control/built-in-roles/databases> | Cosmos DB Operator: "Lets you manage Azure Cosmos DB accounts, but not access data in them. Prevents access to account keys and connection strings." | 2026-11-08 | VERIFIED |
205
+ | COSMOS-E342 | Other control-plane built-in roles: DocumentDB Account Contributor (manage accounts) and Cosmos DB Account Reader Role (read account data). | <https://learn.microsoft.com/azure/role-based-access-control/built-in-roles/databases> | DocumentDB Account Contributor: "Can manage Azure Cosmos DB accounts. Azure Cosmos DB is formerly known as DocumentDB." | 2026-11-08 | VERIFIED |
206
+ | COSMOS-E343 | The Cassandra account creation walkthrough has a Tags tab: name/value pairs to categorize resources and view consolidated billing. | <https://learn.microsoft.com/azure/cosmos-db/cassandra/create-account-java> | Create an Azure Cosmos DB account: "Tags are name/value pairs that you can use to categorize resources and view consolidated billing by applying the same tag to multiple resources and resource groups." | 2026-11-08 | VERIFIED |
207
+ | COSMOS-E344 | Encryption at rest is always on with no switch, AES-256, Microsoft-managed keys; applies to all APIs including Cassandra. | <https://learn.microsoft.com/azure/cosmos-db/database-encryption-at-rest> | Data encryption in Azure Cosmos DB: "encryption at rest is "on" by default. There are no controls to turn it off or on." | 2026-11-08 | VERIFIED |
208
+ | COSMOS-E345 | Data is encrypted in transit over the network and at rest. | <https://learn.microsoft.com/azure/cosmos-db/database-encryption-at-rest> | Data encryption in Azure Cosmos DB: "Your data is now encrypted in transit (over the network) and at rest (nonvolatile storage), giving you end-to-end encryption." | 2026-11-08 | VERIFIED |
209
+ | COSMOS-E346 | With customer-managed keys enabled, id, ttl, _ts, _etag, _rid, _self, _attachments and _epk become reserved field names on Cassandra API tables (otherwise only names starting with __sys_ are reserved). | <https://learn.microsoft.com/azure/cosmos-db/how-to-setup-cmk> | Configure customer-managed keys for your Azure Cosmos DB account with Azure Key Vault: "The following field names are reserved on Cassandra API tables in accounts using customer-managed Keys" | 2026-11-08 | VERIFIED |
210
+ | COSMOS-E347 | The Key Vault must have soft delete and purge protection and must not be reachable only through private endpoints. | <https://learn.microsoft.com/azure/cosmos-db/how-to-setup-cmk> | Configure your Azure Key Vault instance: "An instance that is exclusively accessible through private endpoints can't be used to host your customer-managed keys." | 2026-11-08 | VERIFIED |
211
+ | COSMOS-E348 | For Cassandra accounts with IP firewall rules the Data Explorer client IP must be on the allowed list. | <https://learn.microsoft.com/azure/cosmos-db/how-to-configure-firewall> | Configure an IP firewall by using the Azure portal: "you must add the client IP address or IP range used to access Data Explorer to the account" | 2026-11-08 | VERIFIED |
212
+ | COSMOS-E349 | The Cassandra shell integration in Data Explorer is not supported with virtual network access. | <https://learn.microsoft.com/azure/cosmos-db/how-to-configure-vnet-service-endpoint> | Frequently asked questions: "Currently, the Mongo shell and Cassandra shell integrations in the Azure Cosmos DB Data Explorer aren't supported with virtual network access." | 2026-11-08 | VERIFIED |
213
+ | COSMOS-E350 | The private endpoint GroupId holds the API type of the account, and Cassandra is an allowed value (private DNS zone privatelink.cassandra.cosmos.azure.com). | <https://learn.microsoft.com/azure/cosmos-db/how-to-configure-private-endpoints> | Create a private endpoint by using a Resource Manager template: "In the PowerShell script, the GroupId variable can contain only one value." | 2026-11-08 | VERIFIED |
214
+ | COSMOS-E351 | Setting publicNetworkAccess to Disabled at account creation blocks all public and virtual network traffic and takes precedence over IP and virtual network rules. | <https://learn.microsoft.com/azure/cosmos-db/how-to-configure-private-endpoints> | Blocking public network access during account creation: "This flag takes precedence over any IP or virtual network rule." | 2026-11-08 | VERIFIED |
215
+ | COSMOS-E352 | Adding a private endpoint to an existing account causes about five minutes of downtime unless IP or virtual network rules are added first. | <https://learn.microsoft.com/azure/cosmos-db/how-to-configure-private-endpoints> | Add private endpoints to an existing Azure Cosmos DB account with no downtime: "By default, adding a private endpoint to an existing account results in a short downtime of approximately five minutes." | 2026-11-08 | VERIFIED |
216
+ | COSMOS-E353 | Control plane operations are logged to the ControlPlaneRequests category sent to Log Analytics, Storage or Event Hubs. | <https://learn.microsoft.com/azure/cosmos-db/audit-control-plane-logs> | Enable diagnostic logs for control plane operations: "Select ControlPlaneRequests for log type and select the Send to Log Analytics option." | 2026-11-08 | VERIFIED |
217
+ | COSMOS-E354 | Cassandra keyspace and table creation, update and throughput-update events appear in the control plane logs. | <https://learn.microsoft.com/azure/cosmos-db/audit-control-plane-logs> | View the control plane operations: "The following screenshots capture logs when the keyspace or a table of a Cassandra account are created and when the throughput is updated." | 2026-11-08 | VERIFIED |
218
+ | COSMOS-E355 | With full text diagnostics enabled, logged Cassandra queries contain PII including parameter values; DataPlaneRequests should stay unselected for API for Cassandra diagnostic settings and resource-specific destination tables are advised. | <https://learn.microsoft.com/azure/cosmos-db/cassandra/diagnostic-queries> | Prerequisites: "Note that enabling full text diagnostics, the queries returned will contain PII data." | 2026-11-08 | VERIFIED |
219
+ | COSMOS-E356 | Setting disableKeyBasedMetadataWriteAccess to true stops account keys from changing resources so changes must come through an Azure role. | <https://learn.microsoft.com/azure/cosmos-db/audit-control-plane-logs> | Disable key based metadata write access: "When key based metadata write access is disabled, clients connecting to the Azure Cosmos DB account through account keys are prevented from accessing the account." | 2026-11-08 | VERIFIED |
220
+ | COSMOS-E357 | Storage: the API for Cassandra is backed by the Azure Cosmos DB document engine, which maintains metadata and can change physical storage needs; the difference is most noticeable for small rows and can be offset because compaction and tombstones are not implemented. | <https://learn.microsoft.com/azure/cosmos-db/cassandra/cassandra-adoption> | Storage: "In some cases, the difference might be offset because Azure Cosmos DB doesn't implement compaction or tombstones." | 2026-11-08 | VERIFIED |
221
+ | COSMOS-E358 | Customer-managed keys add a second layer of encryption on top of service-managed keys; keys are stored in Azure Key Vault. | <https://learn.microsoft.com/azure/cosmos-db/how-to-setup-cmk> | Configure customer-managed keys for your Azure Cosmos DB account with Azure Key Vault: "Optionally, you can choose to add a second layer of encryption with keys you manage" | 2026-11-08 | VERIFIED |
222
+ | COSMOS-E901 | az account show returns the details of the current or named subscription, used as the audit identity check. | <https://learn.microsoft.com/cli/azure/account> | az account show: "If the subscription isn't specified, shows the details of the default subscription." | 2026-11-09 | VERIFIED |
223
+ | COSMOS-E902 | az cosmosdb show gets the details of a Cosmos DB account and az cosmosdb list lists accounts; the page does not enumerate returned fields. | <https://learn.microsoft.com/cli/azure/cosmosdb> | az cosmosdb show: "Get the details of an Azure Cosmos DB database account." | 2026-11-09 | VERIFIED |
224
+ | COSMOS-E903 | az cosmosdb restorable-database-account list lists accounts that can be restored (account-name and location filters). | <https://learn.microsoft.com/cli/azure/cosmosdb/restorable-database-account> | az cosmosdb restorable-database-account list: "List all the database accounts that can be restored." | 2026-11-09 | VERIFIED |
225
+ | COSMOS-E904 | az cosmosdb network-rule list lists virtual network rules of an account. | <https://learn.microsoft.com/cli/azure/cosmosdb/network-rule> | az cosmosdb network-rule list: "Lists the virtual network accounts associated with a Cosmos DB account." | 2026-11-09 | VERIFIED |
226
+ | COSMOS-E905 | az network private-endpoint-connection list takes the resource ID via --id and lists private endpoint connections. | <https://learn.microsoft.com/cli/azure/network/private-endpoint-connection> | az network private-endpoint-connection list: "Name of the resource. If provided, --type and --resource-group must be provided too." | 2026-11-09 | VERIFIED |
227
+ | COSMOS-E906 | az monitor diagnostic-settings list returns the active diagnostic settings for a resource. | <https://learn.microsoft.com/cli/azure/monitor/diagnostic-settings> | az monitor diagnostic-settings list: "Gets the active diagnostic settings list for the specified resource." | 2026-11-09 | VERIFIED |
228
+ | COSMOS-E907 | az monitor metrics list reads metric values for a resource; --metrics takes metric names. | <https://learn.microsoft.com/cli/azure/monitor/metrics> | az monitor metrics list: "Space-separated list of metric names to retrieve." | 2026-11-09 | VERIFIED |
229
+ | COSMOS-E908 | az monitor metrics list-definitions lists the metric definitions for a resource. | <https://learn.microsoft.com/cli/azure/monitor/metrics> | az monitor metrics list-definitions: "List the metric definitions for the resource." | 2026-11-09 | VERIFIED |
230
+ | COSMOS-E909 | az cosmosdb sql database list lists SQL databases of an account. | <https://learn.microsoft.com/cli/azure/cosmosdb/sql/database> | az cosmosdb sql database list: "List the SQL databases under an Azure Cosmos DB account." | 2026-11-09 | VERIFIED |
231
+ | COSMOS-E910 | az cosmosdb sql container show/list return SQL container details. | <https://learn.microsoft.com/cli/azure/cosmosdb/sql/container> | az cosmosdb sql container show: "Show the details of a SQL container under an Azure Cosmos DB SQL database." | 2026-11-09 | VERIFIED |
232
+ | COSMOS-E911 | az cosmosdb sql container throughput show gets container throughput. | <https://learn.microsoft.com/cli/azure/cosmosdb/sql/container/throughput> | az cosmosdb sql container throughput show: "Get the throughput of the SQL container under an Azure Cosmos DB SQL database." | 2026-11-09 | VERIFIED |
233
+ | COSMOS-E912 | az cosmosdb sql role definition list lists SQL data-plane role definitions. | <https://learn.microsoft.com/cli/azure/cosmosdb/sql/role/definition> | az cosmosdb sql role definition list: "List all SQL role definitions under an Azure Cosmos DB account." | 2026-11-09 | VERIFIED |
234
+ | COSMOS-E913 | az cosmosdb mongodb database list lists MongoDB databases of an account. | <https://learn.microsoft.com/cli/azure/cosmosdb/mongodb/database> | az cosmosdb mongodb database list: "List the MongoDB databases under an Azure Cosmos DB account." | 2026-11-09 | VERIFIED |
235
+ | COSMOS-E914 | az cosmosdb mongodb collection show/list return MongoDB collection details. | <https://learn.microsoft.com/cli/azure/cosmosdb/mongodb/collection> | az cosmosdb mongodb collection show: "Show the details of a MongoDB collection under an Azure Cosmos DB MongoDB database." | 2026-11-09 | VERIFIED |
236
+ | COSMOS-E915 | az cosmosdb mongodb collection throughput show gets collection throughput. | <https://learn.microsoft.com/cli/azure/cosmosdb/mongodb/collection/throughput> | az cosmosdb mongodb collection throughput show: "Get the throughput of the MongoDB collection under an Azure Cosmos DB MongoDB database." | 2026-11-09 | VERIFIED |
237
+ | COSMOS-E916 | az cosmosdb mongodb role definition list lists MongoDB role definitions. | <https://learn.microsoft.com/cli/azure/cosmosdb/mongodb/role/definition> | az cosmosdb mongodb role definition list: "List all MongoDb role definitions under an Azure Cosmos DB account." | 2026-11-09 | VERIFIED |
238
+ | COSMOS-E917 | az cosmosdb cassandra keyspace list lists Cassandra keyspaces of an account. | <https://learn.microsoft.com/cli/azure/cosmosdb/cassandra/keyspace> | az cosmosdb cassandra keyspace list: "List the Cassandra keyspaces under an Azure Cosmos DB account." | 2026-11-09 | VERIFIED |
239
+ | COSMOS-E918 | az cosmosdb cassandra table show/list return Cassandra table details. | <https://learn.microsoft.com/cli/azure/cosmosdb/cassandra/table> | az cosmosdb cassandra table show: "Show the details of a Cassandra table under an Azure Cosmos DB Cassandra keyspace." | 2026-11-09 | VERIFIED |
240
+ | COSMOS-E919 | az cosmosdb cassandra table throughput show gets table throughput. | <https://learn.microsoft.com/cli/azure/cosmosdb/cassandra/table/throughput> | az cosmosdb cassandra table throughput show: "Get the throughput of the Cassandra table under an Azure Cosmos DB Cassandra keyspace." | 2026-11-09 | VERIFIED |
241
+ | COSMOS-E920 | The Cosmos DB Database Accounts - Get response (DatabaseAccountGetResults) carries a top-level location string, for example West US. | <https://learn.microsoft.com/rest/api/cosmos-db-resource-provider/database-accounts/get> | DatabaseAccountGetResults, location: "The location of the resource group to which the resource belongs." | 2026-11-11 | VERIFIED |
242
+ | COSMOS-E921 | Azure Monitor supports Maximum and Average for NormalizedRUConsumption but only Count for TotalRequests, so each needs its own aggregation. | <https://learn.microsoft.com/azure/azure-monitor/reference/supported-metrics/microsoft-documentdb-databaseaccounts-metrics> | Total Requests: "Number of requests made TotalRequests No Count Count" | 2026-11-11 | VERIFIED |
@@ -0,0 +1,178 @@
1
+ # Azure Cosmos DB for Apache Cassandra operations
2
+
3
+ Operational coverage for **Azure Cosmos DB for Apache Cassandra** (the CQL API of
4
+ an Azure Cosmos DB account). Every section uses the same heading and states one
5
+ status. Cite evidence rows from [the evidence ledger](evidence-ledger.md) as
6
+ `[COSMOS-Exx]`. `tests/validate-nosql-operations.py` enforces this structure.
7
+
8
+ Scope and naming: this is the Cassandra API on the Azure Cosmos DB engine, billed
9
+ in request units [COSMOS-E301]. It is **not** Azure Managed Instance for Apache
10
+ Cassandra, a separate first-party service that hosts pure open-source Cassandra
11
+ clusters (virtual machine scale sets in your virtual network, instance-based
12
+ pricing, nodetool-style operations) [COSMOS-E302] [COSMOS-E303]. Its metrics and
13
+ diagnostics are a different surface [COSMOS-E304]. Nothing below applies to the
14
+ managed instance service, and nothing is inferred from the API for NoSQL or
15
+ MongoDB.
16
+
17
+ Statuses:
18
+
19
+ - `VERIFIED`: the provider documents the capability; every statement below cites a
20
+ VERIFIED row.
21
+ - `PARTIAL`: some of it is documented and some is not, or it is limited (by tier,
22
+ mode, Region or API); say which part is which.
23
+ - `UNSUPPORTED`: provider documentation states the capability does not exist. Cite it.
24
+ - `UNVERIFIED`: no official page settled it in this pass. Say what was searched.
25
+ - `NOT APPLICABLE`: the capability does not apply to this service. Say why.
26
+
27
+ ## Backup and restore
28
+
29
+ **Status:** VERIFIED
30
+
31
+ - Continuous backup with point-in-time restore is **not supported** for the API
32
+ for Cassandra; Microsoft lists it for the NoSQL, MongoDB, Gremlin and Table APIs
33
+ only [COSMOS-E305].
34
+ - Periodic backup is the default mode for existing accounts; interval can be as
35
+ low as one hour and retention up to a month [COSMOS-E306]. Default is a full
36
+ backup every 4 hours with the latest two kept; deleted containers or
37
+ shared-throughput databases keep snapshots for 30 days [COSMOS-E307].
38
+ - Restore is by request to the Azure Cosmos DB team and always creates a new
39
+ single-region account in the source write region; backups are taken only in the
40
+ write region and replicated by geo-redundant storage [COSMOS-E308].
41
+ - Not restored: account keys, firewall, virtual network, data-plane RBAC and
42
+ private endpoint settings, regions, stored procedures, triggers, UDFs, RBAC
43
+ assignments, TTL-expired documents, analytical data, materialized views
44
+ [COSMOS-E309].
45
+ - Restore rights belong to CosmosdbBackupOperator, owners and contributors; two
46
+ backups are free [COSMOS-E310]. Restores cannot target fewer partitions or lower
47
+ RU/s, and analytical data is excluded [COSMOS-E311].
48
+ - Backups are platform managed and immutable under the retention policy
49
+ [COSMOS-E312].
50
+
51
+ ## Disaster recovery and replication
52
+
53
+ **Status:** PARTIAL
54
+
55
+ - Regions are added at the account level; CREATE KEYSPACE replication options are
56
+ ignored, and each region keeps four replicas that cannot be modified
57
+ [COSMOS-E313].
58
+ - Single-write-region accounts can keep strong consistency with service-managed
59
+ failover across regions [COSMOS-E315]; accounts with multiple write regions
60
+ cannot use strong consistency, and no distributed system gives RPO and RTO of
61
+ zero [COSMOS-E316]. Write consistency follows the account default
62
+ [COSMOS-E314].
63
+ - Lightweight transactions are not supported with multiple region writes
64
+ [COSMOS-E317].
65
+ - The account-level Reliability article is framed around the API for NoSQL and
66
+ has no Cassandra marker: service-managed failover is Microsoft-decided, may take
67
+ an hour or more and may lose unreplicated writes [COSMOS-E318]; RPO depends on
68
+ consistency level [COSMOS-E319]. Treat these as account-level statements not
69
+ confirmed for the Cassandra API: do not promise them to a Cassandra workload
70
+ without that confirmation.
71
+ - Unverified for this API: an availability SLA figure and RTO specific to the
72
+ Cassandra API.
73
+ - Backups are not geo-resilient beyond the periodic GRS copy [COSMOS-E308].
74
+
75
+ ## Cost
76
+
77
+ **Status:** VERIFIED
78
+
79
+ Billing dimensions only. Pricing: <https://azure.microsoft.com/pricing/details/cosmos-db/>
80
+ and the calculator <https://azure.microsoft.com/pricing/calculator/>.
81
+
82
+ - Throughput: provisioned RU/s billed hourly at the hour maximum in 100 RU/s
83
+ steps [COSMOS-E320]; set per keyspace (shared) or per table with a 400 RU/s
84
+ minimum [COSMOS-E323]; autoscale available via CQL [COSMOS-E324].
85
+ - Storage: data and indexes per GB per hour [COSMOS-E321]; physical size can
86
+ differ from native Cassandra [COSMOS-E357].
87
+ - Replication: each added region carries throughput and storage, and replication
88
+ egress is billed [COSMOS-E322].
89
+ - Backup: periodic keeps two free and charges extra copies [COSMOS-E310].
90
+ - Sizing: profile requests to estimate RUs [COSMOS-E325].
91
+
92
+ ## Monitoring
93
+
94
+ **Status:** PARTIAL
95
+
96
+ - Metrics: CassandraRequests, CassandraRequestCharges and
97
+ CassandraConnectionClosures plus shared metrics such as NormalizedRUConsumption
98
+ and ProvisionedThroughput [COSMOS-E326].
99
+ - Resource logs: CDBCassandraRequests for data plane operations and
100
+ CDBPartitionKeyRUConsumption for hot keys [COSMOS-E327] [COSMOS-E328]; the
101
+ monitoring reference lists Cassandra error codes [COSMOS-E329].
102
+ - 429s retried by server-side retry appear in the Metrics pane [COSMOS-E331].
103
+ - Alerts: Azure Monitor alerts apply generically [COSMOS-E330]; no
104
+ Cassandra-specific provider-recommended alert set was found.
105
+
106
+ ## Performance
107
+
108
+ **Status:** VERIFIED
109
+
110
+ - Throttling surfaces as OverloadedException or 429 [COSMOS-E332] [COSMOS-E337].
111
+ - Server-side retry is an account-level setting (capability
112
+ DisableRateLimitingResponses, up to 15 minutes) with a 60-second retry window;
113
+ set client read time-out above it [COSMOS-E333] [COSMOS-E334].
114
+ - Limits: 20 GB per logical and 30 GB per physical partition, replication factor 4
115
+ [COSMOS-E335]; 10,000 RU/s per partition, so choose evenly distributed keys
116
+ [COSMOS-E336].
117
+ - gc_grace_seconds must be zero [COSMOS-E338].
118
+
119
+ ## IAM
120
+
121
+ **Status:** VERIFIED
122
+
123
+ - Control plane: Azure RBAC for provisioning, key rotation, metrics and obtaining
124
+ read-write or read-only passwords [COSMOS-E339]; built-in roles Cosmos DB
125
+ Operator (no data or keys) [COSMOS-E341], DocumentDB Account Contributor and
126
+ Cosmos DB Account Reader Role [COSMOS-E342].
127
+ - Data plane: the API does **not** support roles for CRUD activities, so access is
128
+ by account-key credentials rather than per-keyspace roles [COSMOS-E340].
129
+ - Limit blast radius with firewall and private endpoints (below) and by restricting
130
+ who can read keys.
131
+ - Block key-based metadata writes with disableKeyBasedMetadataWriteAccess
132
+ [COSMOS-E356].
133
+
134
+ ## Tagging
135
+
136
+ **Status:** PARTIAL
137
+
138
+ - Resource tags are set on the account at creation for categorization and billing
139
+ views [COSMOS-E343].
140
+ - Unverified: tag-based access control and tag support below account level.
141
+ Searched Learn for Cassandra account tags and the keyspace resource template.
142
+
143
+ ## Encryption
144
+
145
+ **Status:** PARTIAL
146
+
147
+ - At rest: always on, AES-256, Microsoft-managed keys, no switch [COSMOS-E344].
148
+ In transit: encrypted over the network [COSMOS-E345].
149
+ - Customer-managed keys add a second layer using Azure Key Vault [COSMOS-E358].
150
+ The vault needs soft delete and purge protection and cannot be reachable only by
151
+ private endpoints [COSMOS-E347].
152
+ - With CMK, id, ttl, _ts, _etag, _rid, _self, _attachments and _epk are reserved
153
+ field names on Cassandra tables [COSMOS-E346].
154
+ - Unverified: minimum TLS version for the Cassandra endpoint.
155
+
156
+ ## Network isolation
157
+
158
+ **Status:** VERIFIED
159
+
160
+ - IP firewall rules apply; Data Explorer client IPs must be allow-listed
161
+ [COSMOS-E348]. The Cassandra shell in Data Explorer does not work with virtual
162
+ network access [COSMOS-E349].
163
+ - Private endpoints support the Cassandra API type [COSMOS-E350].
164
+ - Set publicNetworkAccess to Disabled at creation to block public traffic
165
+ [COSMOS-E351]; adding endpoints later needs rules first to avoid about five
166
+ minutes of downtime [COSMOS-E352].
167
+
168
+ ## Audit logging
169
+
170
+ **Status:** VERIFIED
171
+
172
+ - Control plane: enable ControlPlaneRequests [COSMOS-E353]; keyspace and table
173
+ create, update and throughput events are logged [COSMOS-E354].
174
+ - Data plane: CDBCassandraRequests records requests [COSMOS-E327]; full-text
175
+ query logging includes parameter values (PII), so enable deliberately
176
+ [COSMOS-E355].
177
+ - Use disableKeyBasedMetadataWriteAccess so changes are attributable to Azure roles
178
+ [COSMOS-E356].