We have just released integration with API management as there is a consumption plan. Please review https://docs.microsoft.com/en-us/azure/azure-functions/functions-openapi-definition to see if this meets your needs.
Quick update here – with the announcement of the premium plan we do support moving from consumption to a premium plan. Today this may not work for all consumption apps in a region only because some consumption apps may exist in a “webspace” that doesn’t yet have premium turned on. That said we have CLI commands rolling out in the next few weeks to make this seamless.
Moving to app service plan is a bit trickier as the actual code often lives in a different place on an app service plan (app service local storage) than where consumption needs them (azure storage files) – so moving may not work and currently don’t have any immediate plans to do like “code migration” in addition to changing plans.
You can see a sample of moving plans between apps in this sample here as well: https://github.com/Azure-Samples/functions-csharp-premium-scaler
Just since it’s been a while, I wanted to reconfirm that this is planned.
We are starting to look into the feasibility of this and the experience that people are looking for. If you are interested to provide feedback on how you’d like to see this implemented please comment here https://github.com/Azure/azure-functions-host/issues/4459
Still unplanned, but please keep the votes coming!
119 votes8 comments · Azure Kubernetes Service (AKS) » Support for Kubernetes features · Flag idea as inappropriate… · Admin →
233 votes7 comments · Azure Kubernetes Service (AKS) » Support for Kubernetes features · Flag idea as inappropriate… · Admin →
Thank you for your feedback. We are currently in public preview of static website hosting for Azure Storage to enable this scenario. Check out the blog post here for more details: https://azure.microsoft.com/en-us/blog/azure-storage-static-web-hosting-public-preview. The feature set includes support for default documents and custom error documents for HTTP status code 404.
For any further questions, or to discuss your specific scenario, send us an email at firstname.lastname@example.org.
We made some progress here with some meta-data attributes to store the readme contents. And, some portal work to display it.
Unfortunately, this got prioritized as we had more pressing/blocking work. We love this polish, and are working with the OCI Image and Distribution specs to define common APIs that all OCI Distribtuion implementations would support. This would enable the community to build tools around this scenario, and not limit to just us.
That said, we still want to enable this scenario, just had to move it back to the backlog.
For more info on how we prioritize:
We’ve started the Auto-Purge work, with this current design: https://github.com/AzureCR/specs/tree/master/auto-purge
Please provide feedback here: https://github.com/AzureCR/specs/issues/1
59 votes2 comments · Azure Kubernetes Service (AKS) » Support for Kubernetes features · Flag idea as inappropriate… · Admin →
23 votes1 comment · Azure Kubernetes Service (AKS) » Integration with Azure services · Flag idea as inappropriate… · Admin →
54 votesplanned · 1 comment · Azure Kubernetes Service (AKS) » Portal · Flag idea as inappropriate… · Admin →
This item was incorrectly marked as started. Actual work on this item has been deferred but is still planned.
Will update when this work is started.
Thank you for your feedback. We’re considering this for a future release of Azure Search.
Azure Search Product Team
Thank you for your feedback. While it is unlikely we’ll address this suggestion in the near future, we’ll reassess based on the number of votes it receives.
Azure Search Product Team
1 voteToshiyuki Hara shared this idea ·
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
The Azure Resource Manager team is actively investigating the scenarios around renaming resource groups. To help us better understand the use-cases and to determine which implementations may be viable to address the problem, we would appreciate if you could fill out this 3-minute survey: