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. Add Application Initialization Support for Scale Up/Down

    The application initialization/warmup feature works great when scaling out/in, but when scaling up/down requests are immediately routed to the new instances before the application is warmed up. It would be great if the new instances could be warmed up before rerouting requests to them.

    399 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  2. Associating Hybrid Connections to Azure App Services cannot be automated

    There is no way to associate a Hybrid Connection to an Azure App Service via ARM Template or PowerShell.

    This is a significant gap since we cannot automate this at all when that is the driving factor for DevOps and PaaS services.

    146 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    18 comments  ·  Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  3. Allow Custom URL Rewrite Handler for Database

    Allow installation of a GAC custom rewrite handler for doing URL rewrites on Web Apps using a database backend.

    87 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 →
  4. FTP accounts tied to subscription, not user. Not enough auditing

    In the current model, FTP credentials are tied to a user's azure login. Thus, we have no visibility into credentials that are set, as we cannot see other people's FTP credentials they've set. Furthermore, when an FTP account is created or deleted, nothing is logged. This makes it difficult to audit who has access. With the logins being tied to the user, when the user leaves, there is no way for us to reclaim that username unless they delete their ftp credentials first. This doesn't always work, as a user may depart abruptly or not on good terms. Although the…

    50 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  5. Copy the application log settings when cloning deployment slots

    It would be better if the log settings are copied into a newly created slot, when we clone a slot, just like the app settings does.
    For example, currently when we turn the blob logging enabled and then clone the slot, the logging get disabled in a new slot.
    On the contrary, the blob container settings remains.

    This is because the blob container setting is saved as an environment variable in app settings.
    Here is the result in ResourceExplorer, when I cloned a slot.

    "applicationLogs": {
    
    "fileSystem": {
    "level": "Off"
    },
    "azureTableStorage": {
    "level": "Off",
    &quot;sasUrl&quot;: &quot;<a rel="nofollow noreferrer" href="https://strageaccountsample.table.core.windows.net/xxxxxxx&quot">https://strageaccountsample.table.core.windows.net/xxxxxxx&quot</a>;
    6 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 →
  6. App services should show the max supported version of ASP.NET core

    If you deploy an app with a version of .NET Core that isn't deployed on Azure yet, you get horrible to debug errors that you have to enable stdout logging on to get to the bottom of.

    (Ultimatly editing csproj with PublishWithAspNetCoreTargetManifest set to false)

    Confusing and time consuming. It would be great if Azure showed you some where on the app, a max supported version of .NET core and some kind of publishing warning if you try to push something higher.

    1 vote
    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 →
  7. php/laravel, Django and NodeJS Deployment

    I would like to see support for PHP/Laravel, DJango and seamless and possible just like i can do in heroku cli or how we do in asp.net core. It will be great if I don't need to worry about composer or pip or virtual environment. I push my app using git or from my repository, Azure App Service should auto detect my language and all the packages and install them on the fly, including root directories and environment variables. Also, web.config should be scrapped out entirely or auto-configured. {Heroku detects my php / Laravel and do all the configurations for…

    1 vote
    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 →

    Have you tried looking into App Service hosted on Linux:
    https://docs.microsoft.com/en-us/azure/app-service/containers/app-service-linux-intro

    While the deployment won’t pull all your dependencies, you can still used a blessed image for your stack and even containerize your solution and host them on Linux.

    One more item to look at is the new CLI “up” command we have for creating apps. You can check the quick session we had at Microsoft Ignite about this feature:
    https://myignite.techcommunity.microsoft.com/sessions/66652

    We’ll leave this under review to see if there are any improvements to our deployment that will happen as part of Linux hosting.

    Thanks,
    Oded

  • Don't see your idea?

Feedback and Knowledge Base