Skip to content

Commit 96794af

Browse files
authored
https://github.com/MicrosoftDocs/azure-docs/issues/105407
1 parent 8558c9a commit 96794af

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/app-service/deploy-zip.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
---
1+
cea h---
22
title: Deploy files to App Service
33
description: Learn to deploy various app packages or discrete libraries, static files, or startup scripts to Azure App Service
44
ms.topic: article
@@ -116,7 +116,7 @@ For more information, see [Kudu documentation](https://github.com/projectkudu/ku
116116

117117
You can deploy your [WAR](https://wikipedia.org/wiki/WAR_(file_format)), [JAR](https://wikipedia.org/wiki/JAR_(file_format)), or [EAR](https://wikipedia.org/wiki/EAR_(file_format)) package to App Service to run your Java web app using the Azure CLI, PowerShell, or the Kudu publish API.
118118

119-
The deployment process places the package on the shared file drive correctly (see [Kudu publish API reference](#kudu-publish-api-reference)). For that reason, deploying WAR/JAR/EAR packages using [FTP](deploy-ftp.md) or WebDeploy is not recommended.
119+
The deployment process used by the steps here places the package on the app's content share with the right naming convention and directory structure (see [Kudu publish API reference](#kudu-publish-api-reference)), and it's the recommended approach. If you deploy WAR/JAR/EAR packages using [FTP](deploy-ftp.md) or WebDeploy instead, you may see unkown failures due to mistakes in the naming or structure.
120120

121121
# [Azure CLI](#tab/cli)
122122

0 commit comments

Comments
 (0)