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.
-
Add static IP address for outbound traffic without the use of App Service Environment
There are many reasons you may want to have a static IP address for outbound connections. For example, you may be accessing a system which requires you to whitelist IP address in a firewall, such as SQL Database or an external service.
Currently, the only way to get a static IP address for outbound connections is to use App Service Environment. App Service Environments are quite complex, and has a very high price tag. You need at least 4 instances, 2 of which must be P2, meaning you'll pay at least 1000 EUR/month. Paying 1000 EUR/month just because you want…
1,482 votesStill no news to share, just to add that we are investigating options on modifications for the App Service multi-tenant offering with enhanced capabilities.
Thanks,
Oded -
Add naked domain support to App Service Managed Certificates
Currently naked domains are not supported when creating App Service Managed Certificates. I want to be able to create a free SSL certificate on a naked/apex domain.
1,426 votesThank you for the feedback. We are investigating this feature request and I will update this status as we make progress.
Best,
Jason -
Support Double Wildcard Custom Domains
For multi-tenant applications, we require the ability for Azure to support double wildcard custom domains.
Single wildcard custom domains are currently well supported, i.e.
*.mydomain.com
catches all unmapped, single subdomain urls e.g. level1ex.mydomain.com, level2ex.mydomain.com etc
The issue (which isn't documented: see forum post below) is that secondary level wildcards are not supported at all by Azure:
e.g. www.level2.mydomain.com will result in a 404 error.
Why is this important? in a multi tenant environment, with lots of customers on different subdomains, it is best from an end-user perspective to support a www. subdomain prefix, as that's what 99% of non-technerati do…
669 votesthis 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)
-
Support App Service Managed Certificates on Free and Shared Tiers
Allow web apps on Free and Shared tiers to use App service Managed Certificates
551 votesThank you for the feedback. We are investigating this feature request and I will update this status as we progress.
Best,
Jason -
Scale Out wait for WarmUp complete before being added to LoadBalancer
When adding new instances to the LoadBalancer, scale out mechanism doesn't wait for those application instances to fully warm up.
Availability checker, via AppInsights, logs these responses, with the header:
'X-AppInit-WarmingUp: 1'Which means that IIS knows that the application is in it's WarmUp cycle, but the LoadBalancer is already trying to serve requests.
N.B. we can add a rewrite rule to redirect the user to the original request, and hope that the LoadBalancer sends the user to a ready instance - but this feels like a hack.
479 votesThanks for the feedback. We are thinking of ways to make the warmup model better and fully ready for the app’s traffic. Right now, we just see the instance is ready before directing traffic.
Please refer to this blog post for more information about slots and AppInit.
https://ruslany.net/2015/09/how-to-warm-up-azure-web-app-during-deployment-slots-swap/Thanks,
Oded -
Antimalware feature on Web Apps (App Service)
Cloud Services and Virtual Machines have an antimalware feature to protect themselves from viruses.
However, Web Apps only protects their platform, and there is no customer-facing antimalware service now.
If we develop an application which receives files from anonymous users with an upload form, we can't detect and get rid of the viruses.
We strongly request the antimalware feature like that Cloud Services and Virtual Machines do.392 votesThere are no near term plans to provide this functionality. However we will keep it under review for periodic re-evaluation in the future.
Thank you,
Azure App Service Team -
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.
386 votesPlacing under review per Ruslan’s comments. We don’t have a timeline to share, but we will update the item once there is more information available.
Thanks,
Oded -
Provide .NET language packs on Web Apps
I'm working on a website that uses System.ComponentModel.DataAnnotations
On my local machine, model validation messages are displayed in french but they are in english when I deploy the website to Azure.
Please install .NET language packs on Azure Web Apps so we don't have to create .resx files and messy code to override .NET built-in messages...
355 votesHi there,
We are still waiting on a few internal dependencies before we can complete this request.
Thanks,
Oded -
TLS 1.3 is now approved, this should be implemented with Web Apps
TLS 1.3 is now no longer a draft, when will Azure introduce the option to enable it?
295 votesHi there,
Given TLS 1.2 was just enabled on Web Apps, we don’t have a plan for when the work will be done to enable 1.3. We will definitely leave this on the backlog as we will come back to it when relevant
Thanks,
Oded -
Ability to incrementally create/update AppSettings & ConnectionStrings
Actual problem:
Today if we don't provide all of the existing AppSettings or ConnectionStrings, the ones we omit are removed.Feature:
A little bit like the ARM deployment mode, add the ability to specify an Incremental & Complete mode when pushing settings. To ensure compatibility, Complete would be the default, keeping the behavior we have today. If we set the mode to Incremental, only the provided settings would be created/updated, leaving existing settings untouched.Use cases:
This would be very useful in cases where we want to sync AppSettings or ConnectionStrings for resources directly in our ARM templates for only…284 votesThanks for the suggestion, we are looking into the feature request
Ahmed
Azure App Service Team -
Custom request headers in web server logs
This is generally useful, but my usecase if with Cloudflare:
When a web app is behind Cloudflare, all visitor IPs come Cloudflare's IPs. Cloudflare does forward the original visitor IP with a custom request header. I want to log this value in my web server logs. In IIS this is achieved with Advanced Logging, but this capability does not seem available in Azure web apps.
246 votesJust an update that we still have this feature on the backlog but with no concrete ETA. We will update when there is more to share.
Thanks,
Oded -
Allow Azure App Service IP Restriction configuration by PowerShell Script
At the moment an Azure App service has the ability to white list IP addresses through the Networking > IP Restriction blade. It would be useful if this could be configured through PowerShell.
219 votesThe option to manage your restrictions through PowerShell is on its way and the docs and being written to explain how to do this. We’ll update when the docs are out.
Thanks,
Oded -
Metric and alert for Web App file system used quota
We would like to setup an automatic alert that fires when the file storage of an app plan is reaching its limits.
Ideally it will be great to have a metric that tells the % of storage (quota) consumed so we can set an alert on top of that metric.
180 votesThis is a great idea and we would like to implement it though there are a few dependencies we need to meet first. We are leaving this on the roadmap for now to see if it gains more customer support which will help with prioritization.
Thanks,
Oded -
Enable 'Connect', 'Log Stream', 'Console' etc for App Service Environment
When you deploy an App Service into an App Service Environment behind an ILB, much of the UI is greyed out. Examples of this is the 'Connect' button, 'Log Stream', 'Console' etc.
I have to manually construct a URL to get to the kudu endpoint right now in order to use the console.
160 votesThanks for bringing this up! This is a known issue and we are working on it. We’ll update the item when complete.
Thanks,
Oded -
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 votesWe are looking at options here.
Thanks,
Oded -
The Always On setting should have an option to make it sticky to the slot when swapping
This is odd it isn't this way by default but should at the very least have an option to make it sticky so as to not break anyone's current practices (in fact, shouldn't more settings have the option to be sticky?).
The issue here is that an always on slot consumes resources. If for example each app consumes 200Megs of RAM, and I have 5 app services running on a service plan, each app service has 2 slots for swapping, then I need to have Always On turned on unnecessarily for 10 slots (2gigs of RAM consumed for nothing). The…
112 votesMoving the feature request to under review. When we have a clear timeline to share, we’ll update the status.
Thanks,
Oded -
App Service - Allow Named Pipe Activation to be enabled
We would like to use named pipes to communicate between services on the same app service, but this doesn't seem to be possible since named pipe activation isn't enabled in .Net on the app service.
89 votesThanks for the entry. We’re taking a look.
Oded
-
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 votesHi there,
Thanks for bringing this up once more. We will have an internal conversation again about implementing for App Service.
Thanks,
Oded -
Permission for accessing Performance counters
We would like create a custom monitoring solution for our Azure Web Site based projects. Unfortunately the web site and job processes do not have permission to read performance counters.
I understand that this is mandatory for a shared hosting environment. However I see nothing against having such functionality if the user has dedicated instances.
Would it be possible to remove this restriction?
87 votesThis isn’t available yet and we’re leaving the ask under review for now. We’ll come back to the idea when we have news.
Thanks,
Oded -
Provide acceptable scale out time for instances in ASE Isolated instance types
Scaling is a core feature of App Services. We used ASE for the additional features however it means we are stuck with 40 mins scale out time to add an instance. Per support this is by design, however this is not documented anywhere in public domain.
Scaling is supposed to help us get customers on to Azure, if it takes 40 mins to add an instance, it will not meet the business needs, we abandoned ASE only due to this issue. Kindly document current scale out time in public documentation so that user know this before hand.
Ultimate goal should…77 votesThanks for the feedback!
You’re right that ASE scaling operations take longer than the common plans on multi-tenant App Service. We are looking at ways to decrease the time so it will on par with multi-tenant but this means a new infrastructure is needed with managing a pool or pre-assigned VMs to the ASEs.
This is documented here, though without a time frame mentioned as it depends on a numbers of factors: https://docs.microsoft.com/en-us/azure/app-service/environment/using-an-ase#how-scale-works.
We will update when there is more information here.
Thanks,
Oded
- Don't see your idea?