I'd love to see more fine-grained permissions. In particular, an 'Edit' permission would be extremely helpful. The user with an Edit permission would be able to change any of the data for the resource except the ID, and would not be able to delete the document.
Use case: Provide users with direct but limited access to the DocumentDB database, rather than having to route all their requests through my own API.10 votes
Work on this items has not progressed. After reviewing this we need to revert this back to under-review.
This work is planned but is more long-term road map.
Thank you for your patience.
Allow a set of keys for read-write or read-only that are restricted to the Collection level or the DB level. Enable multiple applications to have different levels of permission to a single Cosmos DB.9 votes
We plan to introduce long-lived tokens for Azure Cosmos DB accounts to address this scenario. Please email firstname.lastname@example.org for questions, or if you would like to learn about alternate approaches to solve this scenario.
We are using Cosmos DB with Mongo API .We are unable to restrict the user to collection or database level. The only option available is read write keys and read only keys which works on the DB account level.7 votes
We are reviewing this and will update as this status changes.
Add operations to read, write and delete of firewall rule for Cosmos DB.
I could find some other services like SQL, MariaDB and PostgreSQL are having those kinds of operations,
so I was wondering why Cosmos DB doesn’t.1 vote
Thanks for your suggestion. This is not currently on our road map. Will keep on backlog and revisit in future planning cycles.
- Don't see your idea?