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.

We welcome user feedback and feature requests!

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Describe effect of deleting same BlobReceipt multiple times

    Effect of deleting BlobReceipt is already described @ https://docs.microsoft.com/en-us/azure/azure-functions/functions-bindings-storage-blob#trigger---blob-receipts,
    where is described: "To force reprocessing of a blob, delete the blob receipt for that blob from the azure-webjobs-hosts container manually."

    It is only partially valid information - described method (deleting the blob) doesn't work if you remove the reproduced (by reprocessing) BlobReceipt. It simply doesn't start second reprocessing.

    MS support investigated " it is a known functionality in function. we keep a last scan timestamp in the Azure-Webjobs-hosts\blobscaninfo folder, and if the last modified timestamp of the blob is earlier than that, then we don’t go back and rescan.…

    3 votes
    Vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      0 comments  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
    • minWorkerThreads : But it was difficult to determine this value

      We managed to resolve the “Poor Performance”, but we had to do a lot of reading, it was good that the profiler pointed us in the right direction suggesting to set this value MinWorkerThread
      • This request is spending time waiting in the CLR Thread pool queue. This has happen if there is a burst load of requests coming to the process or if there is HIGH CPU on the overall instance.
      • Recommendations : Increase minWorkerThreads setting if your application is getting burst load of requests.

      But it was difficult to determine this value.

      The following Very old link…

      3 votes
      Vote
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        Signed in as (Sign out)
        You have left! (?) (thinking…)
        0 comments  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
      • App service high disk queue length

        We have observed high app service disk queue length while testing an application hosted on App service plan . As per investigation along with the microsoft support engineer, it has been identified that the disk queue length metric has always been aggregated as a sum (Total) for the samples captured from a worker. So any small change in this metric on the worker will cause this to spike rapidly. Also multiple workers will additionally cause this counter to grow even faster. In short, this is not an actual reflection of the actual disk queue length at any point in time…

        1 vote
        Vote
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          Signed in as (Sign out)
          You have left! (?) (thinking…)
          0 comments  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
        • Don't see your idea?

        Web Apps

        Feedback and Knowledge Base