AdminAzure App Service team
(Product Owner, Microsoft Azure)
My feedback
-
100 votes
This remains unplanned, but is still very much of interest. Please keep the votes coming.
An error occurred while saving the comment -
742 votes
.NET Framework 4.8 support is coming to App Service.
Public Azure cloud deployment will begin in mid-late July 2020 completing by mid-September 2020. For our Sovereign clouds, deployment will begin by mid-late August 2020 and complete by early-October 2020.
We will update this item periodically to inform you of the deployment progress.
For more information, please see this blog post:
https://azure.github.io/AppService/2020/06/09/NET-Framework-4.8-is-coming-to-App-Service.html
An error occurred while saving the comment Regarding some of the comments/questions specifically about SameSite cookie handling. Although App Service is running on 4.7.2, it is rolling out a .NET Framework update that includes the functionality for handling the newer 2019 version of the SameSite spec.
Full details on the App Service update available here:
https://docs.microsoft.com/answers/questions/6842/announcement-samesite-cookie-handling-and-net-fram.html-Stefan
-
2 votes
This is great feedback.
We strive for platform upgrades to happen transparently to you, however, they will restart every worker for your function app while performing a platform upgrade.We do not currently have the infrastructure to make this publicly available, but keep the votes coming!
Thanks!
Alex
Azure Functions Team!An error occurred while saving the comment Hello! This is great feedback. I'm editing the wording of this post to make it a bit more clear to our team. Feel free to comment if we haven't matched your intent.
-
69 votes
Hi all,
This work is something we are planning on.
- Matthew
AdminAzure App Service team
(Product Owner, Microsoft Azure)
shared this idea
·
-
3 votes
Thanks for your feedback . We are looking into it.
AdminAzure App Service team
(Product Owner, Microsoft Azure)
shared this idea
·
-
87 votes
Moving this work item to unplanned, as it is clear that this request is no for a global throughput limit.
We do now offer the ability to limit your maximum instances in the Premium plan, which will allow you to avoid swamping downstream resources. https://docs.microsoft.com/en-us/azure/azure-functions/functions-premium-plan#plan-and-sku-settings
We prioritized that above a max call per X limit, because our only control to limit throughput is to outright deny some number of requests above a threshold.
Keep the feedback coming!
Alex
Azure Functions TeamAn error occurred while saving the comment Merging this with duplicate request for throttling.
An error occurred while saving the comment Merging this with a duplicate related to global throttling controls. We believe that an actual per-execution throttle will be more effective than a server limit.
-
346 votes
Hi there,
Given TLS 1.2 was just enabled on Web Apps, we don’t have a plan for when the work will be done to enable 1.3. We will definitely leave this on the backlog as we will come back to it when relevant
Thanks,
OdedAn error occurred while saving the comment The support for TLS 1.3 in Web Apps will be implemented once the underlying infrastructure supports it. We still don't have an ETA on that being added.
Thanks,
Oded -
77 votes
Hi Thomas,
Some feedback from our team:
We do not update the SSL binding on rare cases, and we do have the code working just that it happens on a different task. This is definitely a bug we will be fixing as soon as we can. Most likely will be dealt with in June.
Thanks,
OdedAn error occurred while saving the comment Just to update that we still have this work on our backlog but it has been delayed a bit. Our intention is to improve the UX to do a sync with the certificates after change.
An error occurred while saving the comment Thanks for the additional details in GH. I'll have the engineers on our team sync with the doc folks that answered here.
Oded
-
6 votes
Please check the feature we have to support multi-containers within App Service.
https://blogs.msdn.microsoft.com/appserviceteam/2018/05/07/multi-container/
https://blogs.msdn.microsoft.com/appserviceteam/2018/06/27/use-acr-for-multicontainer-web-app/Does this meet the needs?
Thanks,
OdedAn error occurred while saving the comment Understood. We still don't have the capability to scale each container separately.
Currently, scaling happens at the App Service Plan level and all containers in multi-containers are hosted in the same plan, therefore scale together.
We haven't decided yet if we will pursue this use case, but we will leave the request open here to gather potential customer support.
Thanks,
OdedAn error occurred while saving the comment Thanks again for feedback.
The specific use case as you stated in the comment is on our roadmap. We will update status once we have a timeline.
Thanks,
Yi -
21 votes
This is still on our backlog for review, this did not make it into update 2. We will continue to review this for Azure App Service on Azure Stack.
An error occurred while saving the comment This item is still on our backlog for review, but did not make it into update 3. We will continue to review this for Azure App Service on Azure Stack.
-
549 votes
Please tell us a bit more about scenarios you are trying to enable and how do you see this feature working.
AdminAzure App Service team
(Product Owner, Microsoft Azure)
supported this idea
·
-
35 votes
Python support is now available on App Service Linux. Follow the quickstart tutorial here – https://docs.microsoft.com/en-us/azure/app-service/containers/quickstart-python to get started.
An error occurred while saving the comment Thanks for your feedback. We will take this into consideration for our Python3.6 offering (currently in development).
Asavari
-
3 votes1 comment · Azure Monitor-Application Insights » Service monitoring and diagnostics · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment Moved feature request to App Insights.
-
11 votes
It is currently on our backlog, unfortunately I don’t have an ETA for it
Ahmed
Azure App Service TeamAn error occurred while saving the comment Moved to management in App Insights.
-
2 votes
An error occurred while saving the comment Moving item to Azure SQL uservoice
-
17 votes
This is a great idea!
I’ve linked it up to a github issue for the same feature. https://github.com/Azure/azure-functions-host/issues/1968
-Alex
Azure Functions TeamAn error occurred while saving the comment Merging this with a similar item
-
100 votes
Thank you for your feedback. It is the order of rules which determines how request is processed. Adding reordering and priority for rules is planned.
An error occurred while saving the comment Moved request to the Application Gateway forum.
-
15 votes
We didn’t see a reply on your specific AD setup. Please feel free to add more detail so we can understand the request more thoroughly.
An error occurred while saving the comment Moved to the networking forum for follow up.
-
24 votes
Hi Matt,
Thanks for the feedback. The status of this ask is a bit complicated – it’s partially working, but partially in progress:
1. For existing SSTP P2S VPN, there is no solution but to download the VPN client package again.
2. For IKEv2 P2S VPN, it works by P2S client reconnecting to the Azure VPN gateway. Once they connect again, they will get the new routes. This will apply to changes in VNet address spaces (including VNet peering), newly added S2S/VNet-to-VNet connections, or new routes learned via BGP.
3. The caveat for (2) is that it currently works on Mac and Linux, but Windows require a KB/Update that will be released shortly.
We will provide an update to this item once the Windows update is available.
Thanks,
Yushun [MSFT]An error occurred while saving the comment moved to the networking forum to solve routing between gateway types.
Thanks,
Oded -
2 votes
Can you elaborate a bit on what you’re looking for? We have site traffic metrics you can view in App Insights, but are you asking about a template for a fully coded site?
Thanks,
OdedAn error occurred while saving the comment Moved to the Azure Portal feature requests. This solution would come in the Portal UI, not specific to Web Apps.
Please note that the behavior captured in the post by Arturo was considered unintentional from the SDK team and removed in a later version update. We are working with them to make this formally supported, but right now the instructions in that post may no longer work.