Each DocumentDB DOCUMENT has an ETAG PROPERTY that is updated each time the document is updated and you can enforce that the ETag must be identical to what you opened before when you replace the your document.

The problem with the ETag is that it is attached to the document not the stored JSON object. So all methods we have for fetching a typed Order and write typed LINQ statements against the order is effectively made unusable. You should not (in my opinion) manually add the ETag to the ORDERS object as JSONProperty either. In theory you could add a property in your objects like.

Each DocumentDB document has an ETag property that is updated each time the document is updated and you can enforce that the ETag must be identical to what you opened before when you replace the your document.

The problem with the ETag is that it is attached to the document not the stored JSON object. So all methods we have for fetching a typed Order and write typed Linq statements against the order is effectively made unusable. You should not (in my opinion) manually add the ETag to the orders object as JSONProperty either. In theory you could add a property in your objects like.