Thanks for the input – please keep the details on use cases coming! We hear your feedback and are looking into supporting more diverse workload types.Joe commented
There are scenarios where using a full blown orchestrator is ideal and ACI is great for burst BUT similar to the other comments, I feel there are scenarios were I just want to run a container. The simplicity of ACI plus a reasonable SLA is very appetizing. I hope you reconsider this as a use case to put some cycles against.
It seems that a number of feature requests fall under this use case and would not be requested if people were only hoping to use ACI as serverless burst capacity or batch.
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 TeamJoe commented
"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 under review but we have no ETA at this point. Will update here when that changes.
Thank you for your suggestion.
We’re pleased to announce a public preview of our Key Vault references feature, which you can learn more about here: https://azure.microsoft.com/en-us/blog/simplifying-security-for-serverless-and-web-apps-with-azure-functions-and-app-service/
There are some limitations to the initial preview, but we’re hoping to address those very soon. We’re looking forward to your feedback!
Matthew, Azure Functions team
Azure Cosmos DB now provides the ability to access the change feed (https://docs.microsoft.com/en-us/azure/cosmos-db/change-feed). A common pattern to implement eventing patterns is
1. Store every version/change as a separate item
2. Read the change feed to merge/consolidate changes and trigger appropriate actions downstream.
You can also expire old versions using TTL: https://docs.microsoft.com/en-us/azure/cosmos-db/time-to-live
This feature is currently in active development. We will update this item to complete once it has shipped so those voting/commenting will be notified.
Thank you for your patience.
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.