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.

Azure Synapse Link: Features related to Azure Cosmos DBanalytical store and Azure Synapse Analytics run-time support

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. ChangeFeed Integration w/ Azure Functions

    In a manner similar to a [Blob|ServiceBusQueue|etc]Trigger to execute an Azure Function, it would be helpful to have a ChangeFeed trigger. Ideally the trigger should support action (Create/Update/Delete) filtering as well as filters addition to Document attributes.

    77 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Enable DocumentDB in North Central US region

    Everything about DocumentDB looks great except that it is not available in the region we use. Are some regions first-class and others second-class?

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

    Azure DocumentDB now supports provisioning DocumentDB accounts in the North Central US region. This brings the total region count to 18, including: Central US, East US, South Central US, West US, North Europe, West Europe, East Asia, Southeast Asia, both regions in Japan and Australia, all three regions in India, and both preview regions in Germany. The India regions are available to volume licensing customers and partners with a local enrollment in India.

    Han Wong
    Program Manager
    Azure DocumentDB

  3. Linq Provider should respect JsonConverters on properties

    [JsonProperty("ca")]
    [JsonConverter(typeof(DateTimeToEpochConverter))]
    public DateTime CreatedAt { get; set; }

    DateTime compareDate;
    Client.CreateDocumentQuery<T>(...).Where(item => item.CreatedAt > compareDate);

    In this example, the compareDate should also be converted by the DateTimeToEpochConverter.

    76 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 →

    The DocumentDB LINQ provider in SDK 1.10.0 now supports conversions of common JsonConverters: StringEnumConverter, IsoDateTimeConverter and UnixDateTimeConverter while translating predicates.
    Please let us know if there are other converters that you need covered within LINQ queries.

    Thank you,
    Aravind Ramachandran
    Program Manager
    Azure DocumentDB

  4. Compound indexes

    Compound indexes are required for efficiently sorting on multiple fields. See https://docs.mongodb.com/manual/tutorial/sort-results-with-indexes/.

    74 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  MongoDB API  ·  Flag idea as inappropriate…  ·  Admin →
  5. Add time-to-live feature to documents.

    Often data has expiry date, so it would be useful to set time to live for each document.

    68 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Provide a Typescript definition for all javascript Sdk

    Typescript is very helpfull to manage javascript project.
    Beside that the javascript ecosystem is becoming more and more important.
    Having a typescript definition of every DocumentDB Javascript Sdk will help their adoption.

    67 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. Check if database exist

    When trying to create a database via the CreateDatabaseAsync method of the DocumentClient class (.NET SDK) which already exist the following error message is thrown:

    Exception:Thrown: "Exception: Microsoft.Azure.Documents.ConflictException, message: {"Errors":["The input name presented is already taken. Ensure to provide a unique name property for this resource type."]}

    It would be great to have a method to check if a database already exist, such as "DatabaseExistsAsync(databaseName)" which uses the database name or "DatabaseExistsAsync(database)" which takes an instance of the Database class.

    65 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Add built-in cast function for SQL queries

    Need built-in function for casting string datatypes to INT, NUMBER, DOUBLE, etc. in SQL queries as our data loader is converting the number to string during document creation. We have a requirement to filter on numeric values in our application.

    64 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  SQL API  ·  Flag idea as inappropriate…  ·  Admin →
  9. CosmosDB, Mongo API, Delete Many with Partition Key configured

    We have an IoT based solution and archive old data to blob storage. Our data is moved to archive using the shard key. Removing the data once archived is a pain and slow as each individual document has to be deleted rather than using DeleteMany(x=>x.shardId == id).

    More info found at:
    https://stackoverflow.com/questions/51301711/cosmosdb-mongo-api-delete-many-with-partition-key-configured

    63 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 comments  ·  MongoDB API  ·  Flag idea as inappropriate…  ·  Admin →
  10. MongoDB API : aggregation operation is too slow

    the aggregation operation is too slow ...

    63 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  MongoDB API  ·  Flag idea as inappropriate…  ·  Admin →
  11. Add support for $match in aggregation pipeline (not only as first argument)

    $match is currently only supported when it is the first and only stage of the aggregation pipeline. It would be good to use $match at any stage in the aggregation pipeline. For example if you need to unwind the data, it is a lot easier to perform $unwind first and then $match.

    {

    &quot;_t&quot; : &quot;OKMongoResponse&quot;,
    
    &quot;ok&quot; : 0,
    &quot;code&quot; : 118,
    &quot;errmsg&quot; : &quot;$match is currently only supported when it is the first and only stage of the aggregation pipeline. Please restructure your query to combine multiple $match stages into a single $match stage.&quot;,
    &quot;$err&quot; : &quot;$match is currently
    62 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  MongoDB API  ·  Flag idea as inappropriate…  ·  Admin →
  12. .NET Core Support

    Please support .NET core with Table API for Comos DB

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

    My apologies, this was marked incorrectly.

    This item is now complete. We have just released version 1.0 of our Table API for .NET Standard.

    You can download the Nuget package here, https://www.nuget.org/packages/Microsoft.Azure.Cosmos.Table/1.0.0

    The GitHub repo with samples and more details can be found here, https://github.com/Azure-Samples/azure-cosmos-table-dotnet-core-getting-started.

    Thank you for your request and votes.

  13. Upgrading existing accounts from MongoDB Server Version 3.2 to 3.6

    Currently, the MongoDB 3.6 version is only available to newly created accounts.

    Could be usefull to add the ability to upgrade existing accounts to MongoDB Server Version 3.6.

    54 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  MongoDB API  ·  Flag idea as inappropriate…  ·  Admin →
  14. cosmos db Grah API for .net core pelase!!!

    i read many comments demanding Graph API, and Gremlin Traversal language to be compatible with .NET Core

    53 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Gremlin API  ·  Flag idea as inappropriate…  ·  Admin →
  15. More granular RU, auto-scale RU, separate read-write RU

    This is marked as "completed" in some other posts, but it's still very much an issue.

    We could use DocumentDB in more scenarios if the collections could be smaller and/or assumed lower or highly variable query volume. AWS DynamoDB billing, for example, is more granular and feels more flexible in many scenarios.

    https://aws.amazon.com/dynamodb/pricing/

    One use case is pilot projects where we may want to use noSQL DBs for agility. We can't create small collections cost-efficiently on Azure, and partitions aren't viable for this purpose. So we would end up maintaining many small, potentially underutilized, 400RU collections.

    It would also be…

    52 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 →

    Marking as completed. Users now have the ability to create a single database at 400 RU/s and share among multiple, smaller collections for more granular RU for multiple, smaller collections.

    Separate RU for read/write is unplanned and unlikely to be added to our roadmap.

    Autoscale is on a separate User Voice item, please feel free to upvote there.

    Thank you.

  16. .NET SDK support in UWP apps

    The following message is generated if one attempts to add the Microsoft.Azure.DocumentDb nuget package to a Universal Windows Platform app:
    Some packages are not compatible with UAP,Version=v10.0 (win10-x64-aot).

    50 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SQL API  ·  Flag idea as inappropriate…  ·  Admin →
  17. Support documents larger than 512 KB.

    We are running into lots of limitations due to 512KB document size limitation because in our case only 10% of data exceeds this limitation but it is a big overhead to split the main objects into multiple documents. This could work but is inefficient and makes the querying very difficult.

    46 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 →
  18. Cosmos DB connector for Power BI is still in beta, Please make a stable version

    Cosmos DB connector for Power BI is still in beat and our customer are unwilling to accept this. Can we make a stable version of it?

    41 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  19. Provide Sharding and Replication capabilities similar to that of RavenDB

    RavenDB provides a very flexible sharding and replication plugin. This is preventing us of adopting Azure DocumentDB.

    Sharding
    While I do understand DocumentDB probably shards internally, we also need the ability to shard data across regions/sites/multiple DocumentDBs.

    Replication
    Flexible replication allows us to create one way replication to read replicas which are globally distributed.

    40 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. multiple write regions for a single collection

    Support multiple write regions natively in a single cosmos db collection. Currently to build globally distributed apps, the application need to query two separate collections and merge the results. Enable true global distribution with active - active pattern and not just global replication.

    39 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base