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.
-
Enable users to create custom error pages for 403 and 503 service unavailable messages
Currently 503 errors (service unavailable) present a blank white page with "service unavailable" to the users which is far from professional for us. It would be far better if we could provide a custom 503 page which would include a logo etc., and some text along the lines of "We apologise for the inconvenience, we are working on it. These issues usually resolve in about five minutes. please contact support for further help if required." or something similar.... This error might be caused by Azure network issues, so away from the web app instance.
It would also be helpful if…
1,512 votesWe haven’t forgotten about this request! This is something we would like to bring in the future, but we cannot provide a timeline at this time.
Thank you for using UserVoice!
Jason -
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,382 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,075 votesThank you for the feedback. We are investigating this feature request and I will update this status as we make progress.
Best,
Jason -
Add button to copy Prod to Staging slot instead of swap
When we deploy by using 'swap' the deployment slot will have an old version of the website. Since we want to use the deployment slot as a staging website, it would be great if we could copy the primary website to a deployment slot, without performing a swap.
659 votesThanks for the feedback! We are working on enabling this feature.
Thanks,
Jason -
Upgrade App Service with .NET 4.8
Upgrade App Service with .NET Framework 4.8. Where is the date?
620 votesThank you for the feedback! We plan to update the .NET version, but we do not have an ETA at this time.
Thank you,
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…
562 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)
-
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.
413 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 -
Support App Service Managed Certificates on Free and Shared Tiers
Allow web apps on Free and Shared tiers to use App service Managed Certificates
397 votesThank you for the feedback. We are investigating this feature request and I will update this status as we progress.
Best,
Jason -
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.371 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 -
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...
345 votesHi there,
We are still waiting on a few internal dependencies before we can complete this request.
Thanks,
Oded -
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.
353 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 -
Allow App Service to Access Secret without version
Currently an App Service can access Secrets App Service Identity - but the secret version must be part of this configuration.
What would be helpful is to allow the App Service to get the latest version of the secret - that way a value can be centrally changed - without having to update the App Service configuration (to use the new version of the secret).
This will allow management of the data in the Key Vault - without requiring updates to the App Service to get the new value.
288 votesHi all,
This work is underway. Please keep the feedback coming.
- Matthew
-
Add a web hook to get notified of completed auto-swaps
Deployment slots with the auto-swap feature are useful to warm up the application before making it visible. Unfortunately, it is not possible to get feedback from the operation.
It would be nice to have a web hook that is invoked with the result of the operation (success/failure).
274 votesThank you for voting on this issue and bringing it to our attention. We are planning to add alerting for this and many other App Service operations. We will update this ticket when the feature is available.
-
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?
267 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…252 votesThanks for the suggestion, we are looking into the feature request
Ahmed
Azure App Service Team -
Make OData a first class citizen.
Apparently OData (Microsoft's flagship REST data protocol) isn't fully supported.
More info:
quote
"If you can manually create Swagger 2.0 metadata to describe your REST API, it will work perfectly."
/quoteAssuming it's true that swagger can't do OData, I would think that fact alone would've precluded swagger as an option.
Additionally, whatever the reason swagger cannot create metadata for a WebAPI OData project should have been addressed before launch.
Regardless, please fix this.
233 votesThank you for your feedback!
We would like to add more robust OData support. I am placing this item in “unplanned” to be used in future planning sessions.
Alex
Azure App Service Team -
Make certificate deployment idempotent
When including a Microsoft.Web/certificates resource in an ARM template, the deployment will fail with "Another certificate exists with same thumbprint XXXXXXXXXXXXXXXXXXXX at location xxxx in the Resource Group xxxxxx." if the certificate already exists.
The deployment should be idempotent like all of the other resource types and not fail if the resource already exists.
Otherwise, the certificate has to be deployed manually and cannot be included in an ARM template used for CI/CD deployments (ie: from VSTS)
223 votesThank you for the repro, we are investigating the issue. I will update this status as we get more information.
-
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.
219 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 -
Hybrid Connection Manager Support for Linux
We are an ISV leveraging Azure PaaS to provide an iPaaS service to customers. We have a requirement to connect to on premise servers to access line-of-business apps. Currently, we leverage Azure’s Hybrid Connection Manager --- but are limited to Windows servers only. Our customers have both Windows, Linux and mixed environments. This considerably limits our market.
Can we expect Linux support? If so, when? Any suggested work arounds?
Thank you for your consideration.
206 votesHello everyone,
Thank you for voting and commenting on this item. We are actively working on Hybrid Connection Manager support for Linux. I will update this item as information becomes available.
Thank you,
Jason
- Don't see your idea?