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. .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.

  2. table api sort

    Table API Sorting: Return query results using Table API in lexicographical order for RowKey as per current functionality in Azure Table Storage

    28 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.

  3. Make it possible to set "Account level throughput" on a Table API account through ARM template

    As far as I know, the only way to set "Account level throughput" to "On" for a CosmosDB instance with Table API is to do it through the Azure Portal. It should be possible to automate this through an ARM template.

    https://stackoverflow.com/questions/56772236/is-it-possible-to-provision-throughput-on-database-level-through-code-or-arm-tem

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

    This is possible today.

    This arm template creates a Cosmos Table with initial throughput set.
    https://azure.microsoft.com/en-us/resources/templates/101-cosmosdb-table/

    This template updates the throughput for an existing table.
    https://azure.microsoft.com/en-us/resources/templates/101-cosmosdb-table-ru-update/

    We are currently working on allowing customers to redeploy the same template used to provision the account and table resource to update throughput as well. This should be available in October or early November.

    Thanks.

  4. 9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Table API  ·  Flag idea as inappropriate…  ·  Admin →
  5. Data Migration tool to migrate Existing Azure Table Storage to Cosmos DB to use Table APIs

    Currently there is no way to migrate from existing table storage to Cosmos DB Table APIs. There are migration tools to do this but for the use with Document APIs. I need to use Table APIs on Cosmos DB after migration.

    8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Table API  ·  Flag idea as inappropriate…  ·  Admin →
  6. odata library does not table query of Cosmos entities

    When I tried to send a query with datetime to Cosmos the service supports it but the preview library based on Odata does not. Here is the exception.
    System.AggregateException occurred
    HResult=0x80131500
    Message=One or more errors occurred.
    Source=mscorlib
    StackTrace:
    at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
    at System.Threading.Tasks.Task1.GetResultCore(Boolean waitCompletionNotification)
    at System.Threading.Tasks.Task
    1.get_Result()
    at OurJourney.Filters.PopulateJournalEntries.OnActionExecuting(ActionExecutingContext context) in C:\tfs\Carita\OurJourney\OurJourney\Filters\PopulateJournalEntries.cs:line 92
    at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
    at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.<InvokeNextActionFilterAsync>d__10.MoveNext()

    Inner Exception 1:
    ODataException: Unrecognized 'Edm.String' literal 'datetime'2017-10-01T00:11:42.234Z'' at '82' in 'PartitionKey eq 'c624795e-2e0e-4f57-b92c-53473f0e80cb' and StartDateTimeOffset ge datetime'2017-10-01T00:11:42.234Z''.

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Table API  ·  Flag idea as inappropriate…  ·  Admin →
  7. Allow us to set throughput at database level for Table API too

    As of today we are limited to set throughput at either account or table level, which makes it too unrealistic to migrate applications with a large number of azure storage tables.

    It's also makes is very hard to start small and scale with Table API, as one then might be tempted to start with Azure Storage Tables instead. But due to index limits azure storage tables, one needs to implement several hacks for it to scale, and then the one quickly end up with a data model not optimized for Cosmos DB, hence making the barrier to migrate at a…

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Table API  ·  Flag idea as inappropriate…  ·  Admin →
  8. nuget constraints for CosmosDB.Tables and Storage.Blob are incompatible

    V2.0.0.0 of CosmosDB.Tables

    Microsoft.Azure.Storage.Common (>= 8.6.0-preview && <= 9.0.0.1-preview)

    9.4.2 of Blobs requires >= 9.4.2 of Storage.Common

    How am I supposed to create a single library that accesses both tables and blobs? Disappointing that the CosmosDB.Tables library doesn't support .net standard directly.

    Meanwhile, the old AzureStorage library appears to be tied to an older (v11) version of Newtonsoft.Json.

    Please sort this out - feels like being stuck in DLL **** all over again :-(

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Table API  ·  Flag idea as inappropriate…  ·  Admin →
  9. Support multiple tables per subscription unit

    CosmosDB table API only supports one table for the base subscription unit.

    I know that table API can mix entities in a single table and that since all properties in Cosmos DB are indexed, there is less need to use multiple tables as there is in Azure Table Storage.

    But Azure Table Storage supports multiple tables per subscription, which means that I can't "pick up" an existing Azure Table Storage app and easily redeploy it to CosmosDB. I first have to refactor the app to support a single table and then if I'm not happy I can't easily switch back.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Table API  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base