AdminAzure App Service Team
(Admin, Microsoft Azure)
My feedback
-
317 votes
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)
This is still under review and we will update when we have news.
-
6 votes
Prices are better at larger scale than you might think as compared to multi-tenant. There is the cost per ASE which is a pain but that covers the ASE infrastructure. The higher pricing per core covers the higher internal prices for the HW as well as the infrastructure needs as we scale out. With that said, in many regions the price per core matches Premium. On top of that the better VMs used for ASEv2 give you an over 100% improvement per core. That sorta means that the price is half of premium, at scale. When you think of it that way then the markup from Standard is actually only 1.5 times Standard, again at scale. So if you have a lot of stuff to host, then ASEv2 is pretty darn good for pricing and you have the network isolation which is so very useful.
With respect to putting an ASP into a VNet, it doesn't work like that. The traffic to your apps go through Front End roles that distribute the traffic to the roles hosting your apps. As the multi-tenant App Service is in a multi-tenant network, we cannot simply attach the networks.
With that said, this is an area we are actively working to improve both for ASEs so they are even better and also to enhance our network options for the multi-tenant App Service. -
1 vote
Moving over to the Active Directory team.
-
3 votes
Thanks for the feedback! We agree that fixing this is high priority – a rework of the Functions runtime which will allow for whichever node version you’d like to use is currently in the works. Check out our recent webcast where some of our team members discuss this in more detail here (second half of video): youtube.com/watch?v=4Y30jaWELDk
-
260 votes
Thanks Bart! We are looking at some new workflows in this area. Would you be open to discussing this with us? Please mail me at Nir.Mashkowski@microsoft.com
Hi there,
Just an update that we are still looking at how it is best to enable the feature. We definitely see the value in adding the option and we will update when we have more to share.
Thanks,
Oded -
29 votes
Hi there,
We are looking at the options to work on this item, depending on product roadmap. We will share a timeline once available.
Thanks,
OdedJust an update that we are still looking at options for support. We will update when we have more information.
Thanks,
Oded -
2,681 votes
Hi all,
I’m happy to share that work has officially started to enable HTTP/2 for App Service. We will share a more concrete timeline as it becomes available, but we are hoping for sometime later this year. We really appreciate your patience as we work through multiple dependencies that have to be met before we can fully support HTTP/2.
Thanks,
OdedAs a first step we intend to preview HTTP/2 for public App Service, then at a later point, move to App Service Environment. ASE presents some challenges and it's not as straightforward as ASE gets in for free once enabled for App Service.
Thanks,
OdedHi all,
Thank you for your patience on this work item. Enabling HTTP/2 is dependent on a few other internal engineering changes that have yet to be completed. We don't have a timeline yet since those items are still planned and have yet to be prioritized. We will update here once we have a clearer picture.
Thanks,
Oded -
279 votes
This is most likely not a possibility for the multi tenant structure, but perhaps for the App Service Environment (ASE). We will be reviewing it at the time of adding new features to ASE.
Thanks,
OdedAs said before, we may be able to implement this in ASE in the future, but currently we don't have a timeline to share to complete the feature.
Thanks,
OdedWe are still looking at options on how to complete this request. We will update once we have more details. Thanks for the patience!
Oded
-
34 votes
Thanks for the clarification. We’ll go back to the team and dig more into this.
Oded
Got it. Will get back to you after some research.
Thanks,
OdedHave you checked into the app settings in the portal?
Go to your app settings
Diagnose and solve problems
Metrics per Instance (Apps)
Metrics per Instance (App Service Plan) -
30 votes
Billing is definitely on the backlog
AdminAzure App Service Team
(Admin, Microsoft Azure)
supported this idea
·
-
95 votes
We are still working on this, we will share an update once we complete the work.
We still have this planned, most likely completing the work later this year. We will update once we have more information here.
Thanks,
Oded -
93 votes
We’re leaving this under review for now and we’ll update when we have news.
Thanks,
OdedHi all,
Thank you for your patience. We still have this planned though there is no timeline yet as there are a few items our engineering team needs to complete before this can be tackled. We will update here once there is more information to share.
Thanks,
Oded -
103 votes
Thank you for the feedback, we are looking into the option.
Thanks,
Oded, App ServiceThanks for your patience. We still don't have a timeline to share as supporting this is dependent on a few other items we need to complete first. We will update here once there is more information to share.
Thanks,
Oded -
313 votes
Thanks for the suggestion. The App Service is a multi tenant service which makes features like this more challenging. Because the App Service Environment is single tenant and runs in your VNet it makes having a static IP for outbound requests from your app possible.
Christina
Hi all,
Thanks for all the comments. We still don't have a solution here other than ASE right now, but we have this on the feature request list and we will look on ways to accommodate in the future. We will update the item once there is more information to share.
Thanks,
Oded -
165 votes
Thanks! This is a good ask. We are looking into whether it can be implemented.
Hi all,
We're checking back into this request. We are still planning to complete this though it will take some time due to external dependencies on our systems. We will update timeline and details once we have more information.
Thanks,
Oded -
615 votes
Hi all,
Our team is discussing how best to approach a solution to the request here and we’ve come up with a partial solutiuon which would be great to get feedback on.
The proposed solution to rename the App Service Plan is to:
1- Create a new App Service Plan with the desired new name, the new App Service Plan needs to be in the same Resource Group as the original App Service Plan.
2- Move the apps in the original ASP to the new ASP using the steps mentioned here: https://docs.microsoft.com/en-us/azure/app-service/azure-web-sites-web-hosting-plans-in-depth-overview#move-an-app-to-a-different-app-service-planAhmed
App Service TeamHi all,
Thank you for your patience on the completion of this item. The work to allow the renaming of hosting plans will be prioritized for our next development period. We will update once have a better picture of when it will be completed.
Thanks,
Oded -
1 vote
Thanks for updating. We will review this.
Could you please provide more detail? Are you looking for custom claims injection, or just a way of referencing existing claims from the identity provider? While the JWT issued by App Service Authentication / Authorization does not contain provider claims, these are always available by referencing the /.auth/me endpoint (requires authentication).
-
72 votes
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.
Thanks,
OdedHi there,
Again, this is a good feature request and we'll work to prioritize across the other items we have on our roadmap. A workaround right now is to do all time computations in UTC, and then convert to local time only when needed. I'm aware this is not ideal but this is what can be supported right now.
Thanks,
Oded -
1 vote
We're tracking this feature request here: https://github.com/Azure/azure-webjobs-sdk-script/issues/1323
-
1 vote
To clarify, for Azure Services, we plan to build first-party bindings that customers could then extend. However, we have no current plans to build a binding for Azure Search. This could change, based on customer demand.
Is this a request for a custom binding for Azure Search? We're working on making bindings extensible, so customers that customers can create their own implementation.
Is the core intention here to support the www.*.<custom domain>? That is different from asking for *.*.<custom domain>.
Christina