Thank you for your suggestion. This is not currently on our road map.
As suggested by others, customers are implementing this pattern using the same container with a partition key per tenant or a synthetic key with the tenant id and one or more other properties.
Will mark this as unplanned and leave open and will revisit this in future planning cycles.
Thank you for your suggestion and votes.Anonymous commented
I have a suggestion for this case. If you make the tenant name or id the partition key, then you would be forced to provide it because otherwise you would be running a cross-partition query, which you need to enable explicitly in the request. It doesn't offer a security boundary though, and I'm not sure if tenant id is a proper partition key for you.
We are currently have on our road map this feature for Point-in-Time Restore (PITR) with continuous and on-demand backups. We will update the status here as this feature progresses.
For any questions, please reach out to us at AskCosmosDB@microsoft.com
For applications that require cross document join, please consider the Gremlin API: https://docs.microsoft.com/en-us/azure/cosmos-db/create-graph-dotnet, which has primitives for joins, traversals, and other graph operations.
We are evaluating expanding the SQL grammar to support graph functionality, which will provide the ability to perform cross-document JOINs. Please upvote this item to help us prioritize this work.
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.
Work on this feature has started. Will update here when this becomes generally available.
Thank you for your suggestion and votes.