Work is ongoing to enable VNet support for container instances. Thanks for your patience and feedback, expect to hear from us on this in the next few months!
We have made some great progress on this idea and most of our services today do support move resources across groups.
We are still working towards 100% support and while we do that it would be great if you can help us prioritize the missing services.
Please file individual asks on each service category present in uservoice and vote for it.
Azure Portal Team
"We have made some great progress on this idea and most of our services today do support move resources across groups."
Yes you have and thank you for that!
We are looking into this.
This is a good idea. We’ll look at this later when we’re ready to start adding more bindings (likely after we GA).
"Under Review" woot!!
Actively working on it. Soon will update this thread with dates.
Please add support!
Please note it is possible to implement rich programming logic like batch import/batch delete/etc. using stored procedures. See https://github.com/arramac/azure-documentdb-dotnet/blob/master/samples/code-samples/ServerSideScripts/JS/BulkImport.js for an example of bulk import.
For use cases that need only CRUD and batch operations, the Table API for Azure Cosmos DB might be a good alternative (and supports a native batch REST API): https://docs.microsoft.com/en-us/azure/cosmos-db/tutorial-develop-table-dotnet
We are also investigating supporting a native bulk import method for all APIs (Documents, Tables, and Graph).
If you have a list of URIs (selflinks or UriFactory.CreateDocumentLink()) I think you should be able to Delete or Get them.
Still in works, meanwhile, we recommend using the Spark connector: docs.microsoft.com/en-us/azure/cosmos-db/sp.. or docs.microsoft.com/en-us/azure/cosmos-db/ch.. to perform aggregates like Group By.
or Use Azure Stream Analytics (ASA).
We will be adding support for triggering Azure Function executions from changes in Azure Cosmos DB. Please email firstname.lastname@example.org for details.
That's great to hear Govind! My use case for this is to trigger eventually consistent updates to related documents. (i.e. add a post to all friends' timelines or update content in denormalized documents).
Thanks for the feedback, we have a plan to add this feature.
Adam from the Azure Billing team here at Microsoft.
Our team is entirely committed to doing exactly what you suggest, which is to make all of the customer signup and billing experiences straightforward, comprehensible, and informative.
If you have more specific feedback on how we can make billing easy for you to understand, Please do not hesitate to expand upon your post in the comments.
Adam – Azure Customer Acquisitions & Billing
Renaming resource groups is treated like a resource move behind the scenes. We will address this feature request once resource move is broadly supported across the various services. We would not want to release a rename feature where some resources ended up in the “renamed” resource group, while others were left behind.