Not sure what "3.3 times" means, but I don't think there should be any vote limits (on total votes cast, I do agree limiting the number of votes on each question). The restriction just means Microsoft will never have a clear picture of what's really important to their users who go to the trouble to review these suggestions. There are many thousands of suggestions here.
Same suggestion with more votes here: https://feedback.azure.com/forums/34192--general-feedback/suggestions/17508415-allow-more-than-10-votes
Looks like the community (more specifically Anthony Chu) has already taken a stab at this. Please see the following article (https://anthonychu.ca/post/cosmosdb-real-time-azure-functions-signalr-service/) and GitHub repo (https://github.com/Azure/azure-functions-signalrservice-extension) for details of his implementation.
Your feedback on whether this satisfies your scenarios would be appreciated.
Thanks for your feedback! As more further investigate, the DevTest Labs supports VSTS Git and GitHub today. I’ve added this into the backlog. Given different Git repo offers different client for Labs to use and connect to, it’d be helpful if you could share with us which one you want to support first, so that the Labs can support them one by one. Thanks!
No change in status, but moving this to unplanned to better reflect feature status.
@Amit, he specifically says "configuration repository" -- he isn't using it as a generic name/value database.
188 votesunder review · 16 comments · Azure Key Vault » Managing application secrets · Flag idea as inappropriate… · Admin →
We are looking at options to enable this.
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
This is definitely on our list!
In the meantime, please create a budget which will trigger a script (e.g. Automation, Functions, or Logic Apps) via action groups to shutdown or delete resources based on your specific needs.
This is currently on our road map and actively being worked on now in addition to other improvements. Stay tuned for an announcement on this coming soon.
Quick update: We reduced the entry point to partitioned collections by 75% to make it more cost effective for applications that need high storage but low throughput.
Please see https://azure.microsoft.com/en-us/blog/azure-documentdb-entry-point-for-partitioned-collections-now-75-cheaper/ for details, and email us at email@example.com for any questions.
75% cheaper is still unreasonably expensive for anything short of a well-funded project destined for production deployment.
This means you're completely screwing up one of Microsoft's traditional strong points: making it easy for developers to get and use your products. I have the VS Enterprise MSDN credit and even minor Cosmos experimentation chews through that allotment. It's made worse when Azure is spending my credit hour-by-hour while I search through the vast array of disorganized and outdated documentation. I'm getting the feeling things are changing so quickly not even your own people can stay on top of it. As an architect, it's getting harder and harder to justify putting up with this.