Thank you for your feedback. Providing this functionality is on our backlog but there is no ETA we can share at this time. We will provide updates when they become available. For any further questions, or to discuss your specific scenario, send us an email at firstname.lastname@example.org.
Work for this feature is now planned. Will update here when work on this feature starts and when it becomes generally available.
Thank you.Ruslan commented
Not everything is about RU usage, this is simply bad dev experience. It's not super straightforward, when you decide you need to order by a certain field, to process all existing documents in the database so that they have the required lower-cased property. We have the ability to do that in our project thanks to our custom schema versioning solution, but without it it's not an easy task in a big database, and it's a lot easier for devs to give up on "nice to have" features.
I suspect it's difficult to implement, considering the number of optimizations in place in Azure Cosmos DB, but please revisit this soon.
Reopening this user voice item as our support for Skip/Take (Offset/Limit) was only limited to single partition queries.
The newly released .NET SDK v3 now includes support for x-partition queries using Offset/Limit. You can learn more about v3 SDK and try it and provide feedback on our github repo here.
We will also be back-porting this functionality to our .NET v2 SDK. This work will begin shortly and we anticipate it to be released in September.
Once that is released we will mark this feature as complete.
Thank you for your patience and votes.