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.

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/portal

in Japanese.

日本語で。

診断ログでアプリケーションログ、サーバログを両方設定した状態でWebAppでデプロイメントスロットを複製して作ると、デプロイメントスロット側では、アプリケーションログの設定は複製されず、サーバログの設定は複製される。

その状態でProductionにスワップすると、Production側の診断ログの設定もスワップされるため、結果として、アプリケーションログの設定されていない状態になる。これはシナリオとしておかしい気がする。バグではないか？

診断ログの設定はスワップされないか、デプロイメントスロットを作成するときに完全に複製できるほうが正しいと思う。

改善をしてほしい。以上

Web App deployment does not support SFTP. Why not?

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.

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.

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 useful

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 header

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 WEBSITE_NODE_DEFAULT_VERSION variable.
Is this behavior by design?

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?