Azure Cosmos DB now provides the ability to access the change feed (https://docs.microsoft.com/en-us/azure/cosmos-db/change-feed). A common pattern to implement eventing patterns is
1. Store every version/change as a separate item
2. Read the change feed to merge/consolidate changes and trigger appropriate actions downstream.
You can also expire old versions using TTL: https://docs.microsoft.com/en-us/azure/cosmos-db/time-to-live
Work on this feature has started. Will update here when this becomes generally available.
Thank you for your suggestion and votes.
We just shipped a preview of this functionality today you can try out. In the coming weeks we will enable support to trigger within the Azure Functions Premium plan to receive serverless scale and a function plan to RabbitMQ endpoints within a private network. Please provide feedback and let us know if this meets needs as expected. Details can be found here: