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.
Gremlin API: Graph features and capabilities using Gremlin 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.
-
Autoscale Throughput (UR/s)
Depending on the average amount of incomming requests/ required RU's, (or other parameters,)
I would like to autoscale the througput(RU/s) of a collection.1,719 votesFor any questions, please reach out to us at AskCosmosDB@microsoft.com
-
[CosmosDB] Be able to manage Backup and Restore with Portal and APIs
Please provide the ability to manage backup and restore on our own.
Restore through support is not clear and inconvenient.
It turned out restore is only available through paid support plan.
This document https://docs.microsoft.com/en-us/azure/cosmos-db/online-backup-and-restore#restoring-a-database-from-an-online-backup does not say it in any word.
The situation made our customer extremely unhappy.
445 votesWe are currently have on our road map this feature for Point-in-Time Restore (PITR) with continuous and on-demand backups. We will update the status here as this feature progresses.
Thanks.
-
Add ability to rename databases and collections
It should be possible to rename databases and collections.
This feature is universal in all if not the vast majority of database products.
Lack of ability to rename anything makes it very hard for us to manage releases if we are adding new data. Currently, we have to create a copy of the existing database (which is a feat in itself, since this again is not core functionality), make the change there, and then re-point the website to the updated database. All this time, we are incurring extra costs and inconvenience.
Renaming things also allows us to correct typos, which…
402 votesThe ability to rename databases and collections is not currently something that is in our road map.
Currently the way to accomplish this task in Cosmos DB is to create a new collection with the changed name then use bulk exec or change feed to populate it.
Thanks for your request and input on this. We may consider this for a future planning cycle.
thanks.
-
Support the CouchDB replication protocol
Support the CouchDB replication protocol so that we can sync with PouchDB or Couchbase Lite NoSQL databases on mobile devices for superior online / offline capabilities.
236 votesUsing Change Feed functionality (https://docs.microsoft.com/en-us/azure/cosmos-db/change-feed)
you might be able to sync with PouchDB or Couchbase Lite. -
Improve scaling down experience: remove redundant physical partitions
During initial import we increased RU to 200K. Cosmos Db SQL API created 20 physical partitions with 10K throughput each.
During regular day we just need 30K Ru. That would mean each physical partition would have only 1,5K RU allocated and a lot of redundant partitions with possible expensive cross-partition calls (total data size is less than 30GB)Is there way to decrease amount of physical partitions to reasonable value?
In a nutshell it is not fair pricing, when you are limited to 1,5K RU and a lot of cross-partition calls you have to pay extra117 votesWork for this feature is now being planned. Will update when work on this feature starts and when it becomes generally available.
Thank you.
-
Deploy Stored Procedures from Source Control
It would be great if we could deploy sprocs from visualstudio.com as we can with Azure Functions or Azure Web Sites.
72 votesWe are now planning on including support for deploying Cosmos DB stored procedures from our Resource Provider.
This will allow users to create stored procedures when deploying Cosmos resources from an ARM Template. Support will also be added to PowerShell and az cli in the near future as well.
Combined this capability will allow users to deploy Cosmos resources from templates or scripts when deployed from source control.
Will update here for future progress on this work.
Thank you for your suggestion.
-
Set Account Level throughput on Cosmos DB Table API with ARM template
Make it possible to set "Account level throughput" on a Table API account through ARM template or Powershell.
According to the official Twitter handle of Azure Cosmos DB, it is only possible to set the "Account level throughput" on a Table API database account through the Azure Portal. You cannot do this with an ARM template.
https://twitter.com/AzureCosmosDB/status/117507143322931200145 votesThank you for your suggestion. We will add this to our backlog and review for our upcoming dev cycle.
Thanks.
-
PowerShell module for the management plane
Hi
It would be great if there was a supported PowerShell module for the CosmosDB management plane, in the same vein as the other Az modules. The Az PowerShell team have already done the vast majority of the work with their Autorest project so you'd just need to provide them with a Swagger/OpenAPI definition file and they can help you generate the majority of the code for it.
24 votesWork on PS cmdlets for Cosmos DB has now been started.
Will update as this progresses.
Thank you
-
Faster resource deletion
CosmosDB resources take a very long time to delete. Make this faster please!
13 votesThank you for your additional feedback. We will review this and provide more information soon.
Thank you.
-
Add support for the common Get-AzureRmMetricDefinition and Get-AzureRmMetricDefinition cmdlets
Our company is automating the monitoring of our Azure resources. We need CosmosDB to support retrieval of metrics via Get-AzureRmMetricDefinition and Get-AzureRmMetric. Right now these return nothing for CosmosDB
11 votes -
Cosmos DB Resource Governor
We need a way to implement something mimicking SQL resource governor on Cosmos DB. We wish to allow our service that pushes dats to cosmosDB and admin users full bandwith of the allocated RU\sec. But we wish to limit our customer queries to an RU/sec ceiling. Have we any offering of this type yet?
4 votesWork for this feature is now planned. Will update when work on this feature starts and when it becomes generally available.
Thank you.
-
Add feature to only support TLS 1.2 for PCI
When a PCI scan was run on our public cosmos end point it raised an exception since TLS 1.0 has not been decommissioned.
Can there be a button on the portal to only support TLS 1.2?
thanks
4 votesHi Nate. Thanks for your suggestion. We are currently evaluating TLS 1.2 enforcement.
In the interim if you are running a service within the Microsoft cloud all outbound connections are TLS 1.2. If you are running outside the Microsoft cloud the recommendation is to use .Net 4.6 which is TLS 1.2 by default. If you are running a VM the recommendation is to disable all transport protocols except TLS 1.2.
Registry Example:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\tls 1.0\client]
“disabledbydefault”=dword:00000001
“enabled”=dword:00000000[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\tls 1.0\server]
“disabledbydefault”=dword:00000001
“enabled”=dword:00000000As mentioned this is currently being reviewed for planning. We will update this item as this progresses.
Thanks again.
-
Take collection / container offline
It would be useful to be able to take a collection / container 'offline'. For example, if we wish to delete a large collection, our policy is to make it inaccessible for 6 months prior to deletion.
Whilst we can do this at the client level, it would bring greater assurance a given collection is unused at the point of deletion if it had been offline for a few months beforehand.
3 votesHello Kris and thank you for your suggestion. This is not on our road map at this time.
There are some alternatives you could explore.
You could file a support ticket and ask the container be restored from the latest backup. This is done into a new Cosmos account which would have it’s own keys, essentially making this unavailable to users.
You could also use the Cosmos Data Migration Tool to export the container into json files in blob storage.
Both of these would fit your retention needs as well as make the data essentially offline for access. If this is a rather large set of data and there is a very low or zero chance of it being brought online again, blob storage may make more sense to use as the storage costs are lower.
Will mark this as unplanned as we may offer this ability in the future…
-
2 votes
Work for this feature is planned. Will update when work on this feature starts and when it becomes generally available.
Thank you.
- Don't see your idea?