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. monitor and kill queries

    Add ability to monitor (ie. see SQL query) and kill long running user queries from within Data Explorer.

    18 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Portal  ·  Flag idea as inappropriate…  ·  Admin →
  2. Expose index transformation progress in the portal

    When going to the Scale and Settings tab I can see in the browser dev tools that the header x-ms-documentdb-collection-index-transformation-progress is returned to the client however this information is not shown anywhere in the UI.

    It would be useful if this information was displayed in the portal (possibly only if less than 100/ a transformation is currently in progress)

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

    Thanks for your suggestion.

    The index transformation value use see in the header is actually not always an accurate value. There are four replicas in a replica set, each with it’s own copy of the index. When this header is returned it can from a different partition, each which may be at its own percentage of progress during an index rebuild.

    This is something we hope to provide at some point but is on our backlog. Will mark as unplanned for now and change if this moves in the future.

    thanks.

  3. Interactive JavaScript Shell

    It would be great to have a JavaScript shell (either on the Azure site or something we can connect to) to throw code against for testing purposes as well as do single operations.

    11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Portal  ·  Flag idea as inappropriate…  ·  Admin →
  4. Make triggers be able to fire from Azure portal

    Triggers in DocumentDB should act like triggers in SQL Server, which means when you update documents from Azure portal, the triggers should be fired as well. Right now, this feature is missing. Triggers only can be fired from application code.

    10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Portal  ·  Flag idea as inappropriate…  ·  Admin →
  5. Data Explorer: Allow lazy loading collections to avoid perf overhead when tehre are many collections

    Currently all collections are shown in the Data Explorer. This takes quite some time when an account has many collections. An option to lazy load collections would be nice.

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Portal  ·  Flag idea as inappropriate…  ·  Admin →
  6. Add pre/post trigger support to Data Explorer

    Today, you can demo most of Cosmos DB to DBAs and IT Pros using the portal and Data Explorer.

    Unfortunately, to demo pre/post triggers, you would need to open an IDE and write an application and that loses most of the non-developer audience at a conference or user group talk.

    It would be great if we could, optionally select a pre/post trigger to run as part of the "New Document" experience in the Data Explorer.

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Portal  ·  Flag idea as inappropriate…  ·  Admin →
  7. data explorer should not require IP exceptions

    data explorer should not require IP exceptions

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

Feedback and Knowledge Base