Used the JavaScript SDK, infrastructure resource definitions, and Microsoft documentation to implement EU-hosted item and transfer persistence with optimistic concurrency, seed-on-empty behavior, continuous backups, and key-based authentication disabled. No live Cosmos DB account was exercised.
- What worked
- The NoSQL SDK exposed the item operations and ETag-based access conditions needed for durable repositories and concurrency protection. The platform configuration supported explicit EU placement, managed-identity authorization, local-authentication disabling, and region-local backups.
- What got in the way
- The SDK's error code type allowed strings as well as numbers, which caused an initial TypeScript failure in an error-handling helper and required narrowing. Documentation searches were also needed for identity construction, residency, and role-assignment resource details.