Web Apps
Web Apps in Azure App Service provides a scalable, reliable, and easy-to-use environment for hosting web applications. Select from a range of frameworks and templates to create a web site in seconds. Use any tool or OS to develop your site with .NET, PHP, Node.js, Python and more. Choose from a variety of source control options including TFS, GitHub, BitBucket and others to set up continuous integration and develop as a team.
More details about the services are available in the App Service documentation. If you have a technical issue, please open a post on the developer forums through Stack Overflow or MSDN.
Products that we listen to in this space include: App Service, Web Apps, API Apps and Web App for Containers.
-
Application Security Groups (ASG) support for App Service Environments (ASE)
As stated in the comments section of this page https://azure.microsoft.com/en-us/blog/applicationsecuritygroups/
"It's on the roadmap, all services integrated with VNet like ASE and SQL MI will be part of ASGs groups, as of today the scope doesn't cover subnets for those services, we are exploring options in the near future."52 votesThank you for the feedback. Our team will evaluate this request and consider it for the future. Please continue to provide feedback/vote on this issue if it is pertinent to your Azure deployment.
Best,
Jason -
Vapor Support
Add support for Vapor under the App Services / Starter Web Apps section. This brings support to the Swift server side developer and will be one of the providers of the Vapor Red project (https://vapor.red/)
Thanks.
49 votesThank you for the feedback. At this time we do not have plans to implement this. We’ll keep the item open.
Thanks,
Jason -
Better inform users of when their App Service Certificates are about to expire or have not auto renewed (7 days?)
This week another of our customer's sites went down due to an Azure App Service certificate expiring without us being notified of its pending expiry - we mark all App Service Certificates to Auto Renew and some of them do infact renew and rebind without our intervention, others certificates have got stuck on the domain validation phase (which we validated 1st time we bought the certificate ofcourse) and the latest certificate is now expired and the Manual Renew button is disabled as it seems to think its outside the 60 day renewal window.
A simple email to us (we receive…
49 votesWe are currently investigating options on improving renewal of certs and notifying customers.
-
Support Availability Zones for App Service Environment
With Azure SQL and Storage having zone redundant capabilities and Application Gateway in preview, App Service Environment is soon to be the only thing keeping us from fully PaaS, zone redundant web applications.
49 votesThank you for the suggestion. This feature is in preview! See this blog post for more information:
Thanks,
Jason -
App Service Certificate does not issue cert when web app is deployed on linux app service plan
App Service Certificate does not issue cert when web app is deployed on linux app service plan
48 votesThank you for the feedback, this is a known issue and something we plan to address in the future. In the meantime, you will need to manually verify the domain by adding the TXT record.
-
Ensure Autoscale allows for new instances to get in rotation only if an App is ready
Currently autoscale puts instances into rotation without checking if the actual application is warmed up. Please add a feature to autoscale that checks if an application is warmed up before its put into rotation. Noting that the new Health Check feature has capabilities to detect bad instances based on URL (this is different than adding new instances with autoscale) this may be start as you could queue off the URL to hit in the app to know if an instance is ready to be in rotation.
47 votes -
Enable 'Resource Health' Feature for Isolated App Service Plans
Enable 'Resource Health" feature for Isolated App Service Plans.
Currently, it shows error message "incorrect health status - not supported"
"
Resource health status is not available for Free, Shared or Isolated App Service plan. To enable health status, consider upgrading to a Basic, Standard, or Premium App Service plan.
Report incorrect health status "Instead, users of the most expensive plan, Isolated, in an ASE, are encouraged to change their plan?
Please add the feature or adjust the message. Thank you.
44 votes -
Health Check settings should be sticky to the deployment slot
I do not need Health Check enabled for my staging slot. I do for my production slot. After I performed a swap yesterday, the Health Check settings swapped as well. So now the staging slot has Health Check enabled, and the production slot is disabled.
44 votes -
Do not remove the Advanced Restart Feature
An info bar for App Services > Diagnose and Solve Problems > Diagnostic Tools > Advanced Application Restart now states "Advanced Application Restart will be replaced with Application Health Check". Please leave the advanced restart option in place. The Health check should be an additive change, not a replacement, and certainly not a hard feature swap.
We use advanced app restarts all the time. Health check restarts would solve those scenarios where an instance is in a fully degraded state, but it would miss other scenarios (like higher memory usage, but not yet critical; or a partially degraded instance). Also,…
44 votes -
Pipenv and Pipfile Support
Support for Pipenv and Pipfiles, the new recommended standard for environment management for Python.
43 votesPython 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.
-
Connecting WebApp Service and a DBaaS (MS SQL MySQL etc)PaaS through a VNet service
Connecting WebApp Service and a DBaaS (MS SQL MySQL etc)PaaS through a VNet service. We understand that there is a SNAT limitation when a webapp service is connected to a PaaS service that causes error in the application.
We need private endpoint for DB PaaS services for overcoming the SNAT limitation and also to reduce the latency while connected through private IP address.43 votes -
Support for deploying R Shiny App to Azure Web App Container
What I’m looking for is a guide/tutorial/dockerfile on how to accomplish deploying a shiny app to Azure Web Apps (a tutorial for Flask already exists https://docs.microsoft.com/en-us/azure/app-service/containers/quickstart-python). I think this would be a great addition to the App Service Linux lineup, since Shiny (https://shiny.rstudio.com/) is very popular. A somewhat similar solution exists here https://www.shinyproxy.io/.
43 votes -
A method to allow folks to access the FTP transfer logs when ftp is used to deploy code changes to their azure web apps.
Allow site admins to access the ftp transfer logs when ftp is the selected method used to make web site deployment updates. We use ftp to allow site updates, and we've had an incident where having access to those logs would be very helpful.
43 votesWe’re looking into to see what is currently supported here.
Thanks
Oded -
Allow AAD multi-tenant Apps using App Service Authentication and Authorization
Allow Azure Active Directory (AAD) multi-tenant Apps using App Service Authentication and Authorization.
After on-boarding a tenant with a multi tenant AAD App (Client), the tenant is not able to login to protected Web/Api Apps on App Services.
The ClientId used is the same in AAD Multitenant App.
The STS url is/can only be configured for the App/Client primary tenant GUID.There are no options to enable-multi tenant STS on App Service Authentication and authorization interface.
42 votesLeaving this under review for now to see if there is more user support for development.
Thanks,
Oded -
remove server header from the front end servers
Please remove the server header from the web app front end server and from API Management servers.
It does not matter if our web app removes the header, the front end server still has the header42 votes -
Provide an option to disable or hide App Service Editor in a specific subscription, resource group or web app
App Service Editor allows to make mistakes too easily. An option should be provided to disable or hide for a specific scope to reduce the risk of changes done by mistake.
42 votes -
Add alternate validation methods for App Services Managed Certificates
Please create an alternate method of validation for creating an App Services Managed Certificate. We use CloudFlare in front of our App Services, so the CNAME points to CloudFlare and not Azure. Consequently, validation fails. A preferable alternate solution would be to check if the domain the cert if being requested for is already a custom domain in the web app. If it is, since it you have already been validated as the owner of that domain, it should suffice for an app services managed cert. If you can't do that, then use a DNS TXT record for verification.
41 votes -
Enable AAD Authentication for Multi-container Apps
A common (if not best) practice is to compose applications of multiple containers for the sake of separation of concerns. However, Azure doesn't support authentication with Azure Active Directory for multi-container apps. Until this is in place, we can't deploy our applications to Azure in a clean way.
41 votes -
Disaster Recovery for Azure WebApp
Currently, we have to deploy the Azure WebApp twice, one in West Europe and other in North Europe to support Disaster Recovery.
It means that we need to update the both WebApps if we want to deploy new artifacts in WebApp.
It is very difficult to sync artifacts in both WebApps.
It would be great if Azure provides the RA-GRS(Read-access geo-redundant storage) feature for WebApp like Azure SQL Database.
With this feature the synching of artifacts between both WebApps done by RA-GRS feature.
So we will not deploy the new artifacts in both web app, when we deploy the artifacts…41 votesThanks fort the feature request! We have work on the backlog for disaster recovery, but we don’t have a timeline to share at the moment.
Thanks,
Oded -
App Service Public SSL Certificates persist When Swapping Slot
Currently, if a Web App slot (ex: "staging") is created from an existing Web App that has Public SSL Certificates configured, these are not present on the new slot.
In addition during a slot swap, the "production" slot does not persist the Public SSL Certificates. The configuration for the Public SSL Certificate moves to the "staging" slot.
This behavior does not appear for other configurations such as Private SSL Certificates or AppSettings and could lead to "production" issues if the Public SSL Certificate is expected on the Web App.
The consumer recourse currently is to re-apply the Public SSL Certificates…
40 votes
- Don't see your idea?