# Official Sources

## Grounding rule

Microsoft Learn documentation through the user's configured documentation MCP proves documented Azure service behavior only. It does not prove the user's tenant, subscription, RBAC, quota, deployed resource state, production readiness, or incident status.

## Refreshed on 2026-06-04

- https://learn.microsoft.com/azure/cosmos-db/modeling-data
- https://learn.microsoft.com/azure/cosmos-db/partitioning
- https://learn.microsoft.com/azure/cosmos-db/optimize-cost-reads-writes
- https://learn.microsoft.com/azure/cosmos-db/consistency-levels
- https://learn.microsoft.com/azure/cosmos-db/transactional-batch
- https://learn.microsoft.com/azure/cosmos-db/find-request-unit-charge
- https://learn.microsoft.com/azure/well-architected/service-guides/cosmos-db

## Evidence handling

- Documentation-based: cite Microsoft Learn URLs and say what the documentation proves.
- Sampled configured-environment evidence: label the sample, scope, and time window.
- User-provided sanitized evidence: treat as input to verify, not as proof of all Azure state.
- Inference: use only when evidence is incomplete and state what would confirm or falsify it.