Document Details
Deploy Run Package
❌
This page contains Windows bias
About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
Bias Analysis
Bias Types:
⚠️
windows_first
⚠️
windows_tools
⚠️
missing_linux_example
Summary:
The documentation page demonstrates a Windows bias by referencing Windows file paths (e.g., D:\home\site\wwwroot) before Linux equivalents, using Windows-style path separators in examples, and omitting explicit Linux/Bash command examples or Linux-specific instructions. The focus is on Windows deployment patterns and tools, with minimal mention of Linux environments beyond brief parenthetical notes.
Recommendations:
- Provide Linux-specific examples alongside Windows ones, including file paths (e.g., /home/site/wwwroot) and deployment instructions.
- Use platform-agnostic path notation or show both Windows and Linux paths in all relevant sections.
- Include Bash or Linux shell command examples where Azure CLI is used, and clarify any differences in behavior or requirements between Windows and Linux App Service environments.
- Explicitly mention Linux deployment nuances, such as directory permissions or differences in mounting ZIP packages.
- Ensure troubleshooting and WebJob deployment sections address both Windows and Linux scenarios equally.
Create pull request
Scan History
| Date | Scan ID | Status | Bias Status |
|---|---|---|---|
| 2025-09-14 00:00 | #111 | completed | ✅ Clean |
| 2025-09-13 00:00 | #110 | completed | ✅ Clean |
| 2025-09-12 00:00 | #109 | completed | ✅ Clean |
| 2025-09-11 00:00 | #108 | completed | ✅ Clean |
| 2025-09-10 00:00 | #107 | completed | ✅ Clean |
| 2025-09-09 00:00 | #106 | completed | ✅ Clean |
| 2025-09-08 00:00 | #105 | completed | ❌ Biased |
| 2025-09-07 00:00 | #104 | completed | ❌ Biased |
| 2025-09-06 00:00 | #103 | completed | ❌ Biased |
| 2025-09-05 00:00 | #102 | completed | ❌ Biased |
| 2025-09-04 00:00 | #101 | completed | ❌ Biased |
| 2025-09-03 00:00 | #100 | completed | ✅ Clean |
| 2025-09-02 00:00 | #99 | in_progress | ❌ Biased |
| 2025-09-01 00:00 | #98 | in_progress | ❌ Biased |
| 2025-08-31 00:01 | #97 | in_progress | ❌ Biased |
| 2025-08-30 00:01 | #96 | in_progress | ❌ Biased |
| 2025-08-29 00:01 | #95 | completed | ❌ Biased |
| 2025-08-28 00:01 | #94 | in_progress | ❌ Biased |
| 2025-08-27 00:01 | #93 | in_progress | ❌ Biased |
| 2025-08-26 00:00 | #92 | in_progress | ❌ Biased |
| 2025-08-25 00:01 | #91 | in_progress | ❌ Biased |
| 2025-08-24 00:00 | #90 | in_progress | ❌ Biased |
| 2025-08-23 00:00 | #89 | in_progress | ❌ Biased |
| 2025-08-22 00:01 | #88 | completed | ❌ Biased |
| 2025-08-21 00:01 | #87 | in_progress | ❌ Biased |
| 2025-08-20 00:01 | #86 | completed | ❌ Biased |
| 2025-08-19 00:01 | #85 | completed | ❌ Biased |
| 2025-08-18 00:00 | #84 | in_progress | ❌ Biased |
| 2025-08-17 00:01 | #83 | in_progress | ❌ Biased |
| 2025-08-16 00:00 | #82 | in_progress | ❌ Biased |
| 2025-08-15 00:01 | #81 | in_progress | ❌ Biased |
| 2025-07-13 21:25 | #47 | cancelled | ✅ Clean |
| 2025-07-13 20:48 | #44 | cancelled | ❌ Biased |
| 2025-07-09 13:09 | #3 | cancelled | ✅ Clean |
| 2025-07-08 04:23 | #2 | cancelled | ❌ Biased |
Flagged Code Snippets
Because the `WEBSITE_RUN_FROM_PACKAGE` app setting is set, this command doesn't extract the ZIP package content to the *D:\home\site\wwwroot* directory of your app. Instead, it uploads the ZIP file as-is to *D:\home\data\SitePackages*, and creates a *packagename.txt* in the same directory, that contains the name of the ZIP package to load at runtime. If you upload your ZIP package in a different way (such as [FTP](deploy-ftp.md)), you need to create the *D:\home\data\SitePackages* directory and the *packagename.txt* file manually.
The command also restarts the app. Because `WEBSITE_RUN_FROM_PACKAGE` is set, App Service mounts the uploaded package as the read-only *wwwroot* directory and runs the app directly from that mounted directory.
## Run from external URL instead
You can also run a ZIP package from an external URL, such as Azure Blob Storage. You can use the [Azure Storage Explorer](../vs-azure-tools-storage-manage-with-storage-explorer.md) to upload ZIP package files to your Blob storage account. You should use a private storage container with a [Shared Access Signature (SAS)](../vs-azure-tools-storage-manage-with-storage-explorer.md#generate-a-sas-in-storage-explorer) or [use a managed identity](#access-a-package-in-azure-blob-storage-using-a-managed-identity) to enable the App Service runtime to access the ZIP package securely.
> [!NOTE]
> Currently, an existing App Service resource that runs a local ZIP package cannot be migrated to run from a remote ZIP package. You will have to create a new App Service resource configured to run from an external URL.
Once you upload your file to Blob storage and have an SAS URL for the file, set the `WEBSITE_RUN_FROM_PACKAGE` app setting to the URL. Make sure the URL ends with `.zip`. The following example does it by using Azure CLI: