When an App Service is configured with an IP Restriction, only whitelisted IP's can access the App service URL/site. Other users cant access the URL. By default the blacklisted IP's or denied IP's will receive
Error 403 - This web app is stopped. Many SR's can been be seen with this requirement to divert or return custom error message instead of 403 error. It would be great if we have a feature in portal to divert with custom message when the IP restrictions are configured for a web app.16 votes
When the singleton lock is reset, the job may start in parallel, and I would like to detect, to able to distinguish whether the singleton lock has been reset.8 votes
We have webapps that is querying Hive on HDInsight which is working fine when hosted on on-prem IIS. We need Hive ODBC driver installed on the VM to get it works.
But when we deploy on Azure App Service it's failing due to missing driver.
Can Microsoft® Hive ODBC Driver installed on Azure App Service Environment & Azure Function please?9 votes
Currently ASE allows uploading of ILB certificates through script/portal.
Provision to autopick certificate from Azure KeyVault using thumbprint should be made possible through script/portal13 votes
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 header35 votes
Connecting to Azure DB for MySQL from Azure Web Apps (windows) fails when SSL is enabled on MySQL. mysql.exe --host=xxxxxxxx.mysql.database.
Connecting to Azure DB for MySQL from Azure Web Apps (windows) fails when SSL is enabled on MySQL.
mysql.exe --host=xxxxxxxx.mysql.database.azure.com --user=user@db --password="password" --ssl --ssl-ca=D:\home\data\BaltimoreCyberTrustRoot.crt.pem
results in an error: ERROR 2026 (HY000): SSL connection error: socket layer receive error
But Drupal config with SSL to MySQL works OK. MySQL CLI from desktop works OK. Issue appears to be specific with Azure Web Apps and MySQL client.1 vote
An alert should be raised when a .NET Core version upgrade is scheduled for the App Service platform. Ideally, the alert should occur well in advance of the actual upgrade to give application teams time to prepare.2 votes
My team initially created our API on a web-app service, it seems like we're not alone. When we started experimenting with the API mgmt service, it wouldn't accept it for import. I had to delete the web-app, provision a new API-app, migrate the code to it and only then would API mgmt import it.
For these cases, a conversion process to/from API-app would be very useful2 votes
Node Apps on App Service can specify version of Node runtime in "engines" section of package.json,
But Function Apps(Runtime v2) cannot specify version by description of package.json, so they has to specify version of node by setting of WEBSITENODEDEFAULT_VERSION variable.
Is this behavior by design?4 votes
We run more than one app per hosting plan. In dev we have 63 apps on one plan (I know this isn't advised but it saves money for dev and illustrates the point). If we have one app that is eating most of the CPU or memory there is no simple way to find this at the app plan level, I have to look at 63 different screens or add 63 different counters to the same screen. The app plan has a 'per instance' button that is great for seeing how each node in the plan is doing but we want to further break that down per app. Think of perfmon on an old iis server.
We run more than one app per hosting plan. In dev we have 63 apps on one plan (I know this isn't advised but it saves money for dev and illustrates the point). If we have one app that is eating most of the CPU or memory there is no simple way to find this at the app plan level, I have to look at 63 different screens or add 63 different counters to the same screen. The app plan has a 'per instance' button that is great for seeing how each node in the plan is doing but we…7 votes
Web App deployment does not support SFTP. Why not?1 vote
There doesn't seem to be a clear and defined way to manage HTTP headers with an Azure static website. I know this feature is still in preview but my team and I are attempting to make this into a production ready web application.
- Don't see your idea?