Azure Cosmos DB

Have feedback for Azure Cosmos DB product? Submit your idea here or upvote other ideas. All feedback is monitored and reviewed by the Azure Cosmos DB team. 

This site is for feature suggestions only. For technical questions or issues, please submit them to StackOverflow,where we and the community can better help you.

Please use the following categories when submitting your idea.

SQL API: Query language features, syntax using SQL API, indexing, any other core features in Azure Cosmos DB.

Gremlin API: Graph features and capabilities using Gremlin API.

Cassandra API: Features and capabilities using Cassandra API.

MongoDB API: Features and capabilities using MongoDB API.

Table API: Features and capabilities using Table API.

Etcd API: Features related to using etcd as a configuration store for Kubernetes.

Built-in Apache Spark: Features related to built-in Apache Spark in Azure Cosmos DB.

Built-in Notebooks: Features related to built-in Notebooks in Azure Cosmos DB.

SDK: Features related to Azure Cosmos DB SDKs for SQL API.

Change Feed: Features related to Change Feed.

Management: All management features, backup/restore,monitoring, ARM, PowerShell and CLI.

Portal: All features for Azure Portal and Cosmos DB Explorer.

Emulator: Features related to the Azure Cosmos Emulator.

Other: Features not related to any other category.

Security:
Authentication, authorization,permissions and encryption features.

Monitoring:
Metrics, monitoring, alerts,and diagnostics features.

Server-side: Stored procedures, Triggers,and User-Defined Functions.
  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Standalone local instance

    I would be great to have a standalone version for offline development and unit testing. Something like Storage Emulator.

    3,787 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    94 comments  ·  Flag idea as inappropriate…  ·  Admin →

    We’re excited to announce the public preview of the DocumentDB Emulator (https://azure.microsoft.com/blog/documentdb-emulator-for-local-development-and-dotnet-core-support/), which provides a local development experience for the Azure DocumentDB service. Using the DocumentDB Emulator, you can develop and test your application locally without an internet connection, without creating an Azure subscription, and without incurring any costs.

    This has long been the most requested feature on the user voice site, so we are thrilled to roll this out everyone that’s voted for it. Please let us know if you have any feedback, questions or suggestions.

    Thank you,
    Aravind Ramachandran
    Azure DocumentDB

  2. Add support for aggregate functions like Count, Sum, and Avg along with Grouping

    It would be great to have some baseline aggregation functions support without having to return all the records and then perform aggregates on them in code.

    2,611 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    83 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Provide support for DISTINCT

    Need to provide support for SELECT DISTINCT xyz FROM c.

    1,621 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    73 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Backup Solution for DocumentDB

    It seems that there is no backup for DocumentDB. You should provide a backup solution for DocumentDB.

    1,261 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    36 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Batch Operation Support

    Document DB should support batch operations in REST API and SDK level. It would be very useful to insert 1000 entities in one transaction.

    1,210 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    21 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. DocumentDB Free Tier

    DocumentDB offering should provide a free tier for dev/testing.
    I'm maintaining the MongoDB provider for NEventStore (https://github.com/NEventStore/NEventStore.Persistence.MongoDB) and would try to build a DocumentDB Persistence Provider.

    Would be even better to have an "open source" subscription for oss projects on azure (dev/testing)!

    1,118 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    18 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. Manage Azure DocumentDB using PowerShell

    We need a PowerShell module for managing Azure DocumentDB

    1,117 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    41 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Allow me to set JsonSerializerSettings

    Today I have to use JsonProperty or JsonConverter attributes to decorate my objects one property at a time.
    This is painful when dealing with large objects and error prone.
    It would be a much better idea to support the use of JsonSerializerSettings to set global behavior for JSON.NET ... just like WebApi and ASP.NET does today.

    1,073 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  26 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Allow Database Level Pricing

    I am looking to convert an application from MongoDB to DocumentDB as I would prefer a managed solution but the collection pricing is absurd. The current model has 1 or 2 collections with 10+ GB of data that will grow at high rates but there are another 30 collections or more with most of them having only 10-20 records. Paying a minimum of $25 per collection is out of the question especially for dev workloads. The pricing model would change your development behaviour to just stuff everything in the same collection but then you loose a lot of the ability…

    976 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    50 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. "Order By" in queries

    I cannot find any documentation on what order the data from a query will return.
    I would love to be able to explicitly specify an "order by" clause to dictate that order

    945 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    35 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Partitioned Collections with < 10k RU/s

    Please allow partitioned collections with fewer than 10k RU reserved.

    I really would like to use partitioned collection but according and the pricing model $6/month for each 100 RU seems fair. But the minimum RU/s for partitioned collections are > 10.000 RU/s which is min $600 a month.

    752 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Flag idea as inappropriate…  ·  Admin →

    We are pleased to announce that partitioned collections have an entry point 75% cheaper than before. Instead of provisioning 10,100 RU/sec as a minimum, you can now provision a partitioned collection at 2,500 RU/sec and scale in increments of 100 RU/sec. Partitioned collections enable you to dynamically scale your provisioning from as low as 2,500 RU/sec to millions of RU/sec with no limit on storage consumption.

    Please download SDK 1.12.0+ or use the Azure Portal to provision these collections.

    -DocumentDB team

  12. Support OData Protocol

    Since OData is a standard API supported by Microsoft and intrinsically supports JSON, and DocumentDB is JSON-based, it's a good fit. A standard protocol would also greatly increase interop potential, like SQL, which you are supporting.

    707 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 comments  ·  Flag idea as inappropriate…  ·  Admin →

    The Table API for Azure Cosmos DB uses ODATA as the primary protocol for querying. See
    https://docs.microsoft.com/en-us/azure/cosmos-db/table-introduction
    https://docs.microsoft.com/en-us/azure/cosmos-db/tutorial-query-table
    https://docs.microsoft.com/en-us/azure/cosmos-db/tutorial-develop-table-dotnet

    Applications written for Azure Table storage can take advantage of premium capabilities like provisioned throughput, single-digit millisecond latency, global distribution, and automatic secondary indexing.

  13. 668 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    29 comments  ·  MongoDB API  ·  Flag idea as inappropriate…  ·  Admin →
  14. Have DocumentDB in Brazil datacenter

    Enable DocumentDB in Brazil Datacenter

    670 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Transparent Data Encryption (TDE)

    DocumentDB should support Transparent Data Encryption.

    653 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    32 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Unique constraint on document properties

    While document ID's are unique, I would like a unique constraint on a given property as well. Today, the only ways I see to accomplish this is either with a client-side query or a pre-trigger (also requiring a query).

    I'd like a "unique" constraint to be applicable for given property names within a collection.

    619 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. Allow multi Order By

    From what I see it is impossible to run a query with more than one column in the Order By.

    616 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    17 comments  ·  SQL API  ·  Flag idea as inappropriate…  ·  Admin →
  18. I want atomic counter

    I want a counter is a valid atomic in the collection. Such as use with automatic sequential number.

    556 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    15 comments  ·  Flag idea as inappropriate…  ·  Admin →

    We now have support for generating a globally unique Int64 ID with the DocumentID() function.

    The function returns a unique number that identifies the document in a collection. The number is extracted from the document’s _rid field. The number is 64 bit long.

    Syntax:
    DOCUMENTID()

    Example:
    SELECT f.id, DOCUMENTID
    FROM Families f

    However, for an Identity column equivalent for this we are declining this due to scalability constraints. Hopefully this will meet your needs.

    Thanks for your suggestion.

  19. 552 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    25 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Add "elastic pool"

    Today at BUILD we saw Azure SQL DB announce elastic pools. This is awesome and what I hoped capacity units would be.

    This is definitely needed if we're going to build SaaS apps with DocumentDB

    1) assign collections to a pool of resources and have resources allocated dynamically to collections as needed based on demand. Hot collections just get more, idle collections get less

    2) elastic query to easily write one query against all collections in a pool

    3) jobs to be able to manage sprocs etc. across collections easily

    496 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 13 14
  • Don't see your idea?

Azure Cosmos DB

Categories

Feedback and Knowledge Base