Thank you for the additional details. This is a great feature request! We have entered an item for this on our product backlog and will wait to see if it gathers more support from our customers.
Thank you for your feedback!
We would like to add API Key support to App Service authentication/authorization. I am placing this item in “unplanned” to be used in future planning sessions.
Azure App Service Team
This ask is currently on our backlog and will be prioritized accordingly. We will update when the status changes.
My most painful point is the 32Kb limit of property size. If I use it as a key - value store (and why not, actually it is), then I can't use the 1mb row limit, if I have only one key and one value in a row and value must be maximum 32Kb what is very tiny :(
Work is ongoing to provide POPs in additional Geographical regions. In November POP’s were added in India and South America. Additional POP’s in South America and in Oman will be added in the next few months. We also announced last year a partnership with Akamai which will allow us later this year to provide access to the entire Akamai network. Akamai has POP’s in over 110 countries. The following link from Akamai will help us see the level of coverage that they have today: http://wwwnui.akamai.com/gnet/globe/index.html
This feature is currently under review and we will get back to you as soon as we have an update on this.
In the interim, a design approach to consider would be to break your JSON document down into smaller pieces, for example one document for the data that rarely changes and smaller document that is regularly updated. This in combination with upsert would allow you to quickly modify the attributes that needed modifying.
this feature has been postponed as it wouldn’t be complete and might be revisited later if standards/supported features by CAs and browsers change (double wildcard certificates are not supported standard, resulting in no way to secure double wildcard domain)
Hi all. As everyone had noticed, we have upgraded App Service resources to Server 2016. As mentioned in our updates, this is indeed paving the way to HTTP/2 support across the board. As we are settling in with stability of the new OS version, we will begin work to open up HTTP/2. When I have a concrete timeline to share, I will do so. We should expect that in the next few months.
4 votesLajos Marton shared this idea ·
Support is planned for this later this year.
Thanks for your feedback here. We are working to bring ColumnStore to the Standard service tier.
I think this is a simple business decision from M$. They want to push everybody to premium tiers.
Thanks for your feedback, we have heard this request from a few customers.
We are planning to provide DISTINCT capabilities in a future release. Once we have released aggregates, we will be working on providing DISTINCT. Will update you once we have a firm timeline for this.
Azure Cosmos DB supports the CONTAINS, STARTSWITH, and ENDSWITH built-in functions which are equivalent to LIKE.
We are planning to add support for LIKE since this is a top requested item, but meanwhile, please use the other equivalent keywords.
Support for SKIP is under review; we will provide an update once we have a confirmed schedule. As previously announced, TOP is supported, and the LINQ provider supports TAKE.
Thanks for the feedback. We’re working on this. We started with the top bar, then added favorites, and continued by shrinking the list of resources after opening the resource blade. Much more is in the works — all based on your feedback. Keep it coming and, in the meantime, we’ll keep working on this to streamline the experience for you.
Please at least try the new portal on 1366X768.
I don't have issues with tiles on the new portal, but the horizontal scrolling is a curse. On the other side the whole page is not responsive, I can't work on it with my 1366X768.
We have enabled “Open in new tab” and "open in new window’ in our January update (http://azure.microsoft.com/blog/2015/01/29/announcing-azure-preview-portal-improvements/)
We working now to enable “update url in the
browser as you navigate” soon – this will complete this, as when you open a blade in a new tab you will also have a url that you can bookmark,
If you have any comments or feedback or want to learn more, feel free to write me directly to email@example.com
Thanks a lot for your feedback!
96 votesunder review · 2 comments · Azure portal » Resource management · Flag idea as inappropriate… · Admin →
We’d love to do this!
Each service will enable this independently over time. Most services already have this available today from their resource blade.