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.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. implement a graceful restart an Azure Web App with multiple instance

    We would like to have feature through which we can perform the configuration changes through portal without down time when there are multiple instances are available. The similar stuff is available in advanced restart where you can define the delay between restart of each instance.

    53 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment  ·  Flag idea as inappropriate…  ·  Admin →

    Hi everyone, we have some long-term plans to improve the restart speed and experience.

    For this scenario we suggest creating a new slot, applying your changes there, validating they work, and swapping your changes. This pattern will avoid downtime on your production site.

  2. Allow FrontDoor CNAME for App Service Managed Certificate validation

    When creating an App Service Managed Certificate, it should allow validation if the CNAME is pointing to a FrontDoor with the same domain (or the FrontDoor's backend is the same Web App).

    Currently it gives the error "Hostname not eligible for App Service Managed Certificates creation" since the CNAME is not directly pointing to the web app.

    51 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  App Service Environment  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  App Gallery  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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."

    46 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  App Service Environment  ·  Flag idea as inappropriate…  ·  Admin →
  7. WebApp custom DNS with private DNS Name

    Custom DNS HostName for a WebApp is working exactly in the same way in both Azure and Azure Stack, with both ownership and record check against a public Internet DNS server. That's pretty cool for public facing web applications, but represents a security issue for :
    1)Intranet applications.(hosted on Azure or AzureStack)
    - Custom Domain Names makes sence not only for Internet but Intranet too.
    - We don't want to expose intranet application names publicly to the wild...
    2)Multi-tenant AzureStack
    - Each customer would like to have it's own custom domain for its applications, and not use the *.appservice.local.azurestack.external or…

    46 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  App Service Environment  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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,…

    43 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Diagnostics  ·  Flag idea as inappropriate…  ·  Admin →
  10. 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
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Supportability  ·  Flag idea as inappropriate…  ·  Admin →
  11. Make WEBSITE_ADD_SITENAME_BINDINGS_IN_APPHOST_CONFIG to 1 by default or add warning

    We have been hit by hard restarts on web apps because we have not set the WEBSITEADDSITENAMEBINDINGSINAPPHOSTCONFIG to 1. It would be a more sane default to have it set to 1 by default, and then turned off by users that need WCF support OR have some sort of warning / checkbox or increased visbility in the portal.

    The simultaneous restart of all (in our case) 10 servers in a datasenter has caused outage of our services, and we would imagine others experience the same issue. I doubt many assume that all servers in…

    43 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  App Service Environment  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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 header

    42 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Supportability  ·  Flag idea as inappropriate…  ·  Admin →
  14. Add support for NetworkWatcher / NSG Flow logs for App Service with Regional Vnet Integration enabled

    At the moment, if one uses an App Service with Vnet Integration there is NO way to monitor the traffic that traverses this path. For organizations with requirements to monitor ALL network traffic for integrity / Security / Audit purposes - this presents a significant challenge as ALL traffic that traverses this integration is not able to be monitored. Since the App Service presents itself as on a given subnet within the Vnet - there should be NO reason that NetworkWatcher or NSG flow logs shouldn't be usable.

    42 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Supportability  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. 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 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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.

    41 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. 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
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  19. 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…

    40 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Notifications  ·  Flag idea as inappropriate…  ·  Admin →
  20. DNS resolution is not working in Azure Web App for Containers (linux)

    DNS resolution is not working in Web App for Containers (linux) when using custom docker image. The DHCP generated resolv.conf is broken. After using SSH to log in to the container trying nslookup google.com also fails with DNS resolution error.

    See my sample project for more details:

    https://github.com/henkosch/azure-webapp-dnstest

    The problem is also mentioned in the comments section on this page:

    https://docs.microsoft.com/en-us/azure/app-service/containers/app-service-linux-faq

    Does anyone have an idea how to fix this?

    40 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base