https://github.com/MicrosoftDocs/azure-docs/pull/99454

Author: cephalin

articles/app-service/deploy-run-package.md

@@ -47,18 +47,6 @@ Because the `WEBSITE_RUN_FROM_PACKAGE` app setting is set, this command doesn't
 
 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.
 
-### Webjobs with WEBSITE_RUN_FROM_PACKAGE=1
-How does that affect WebJobs?
-There are two scenario for WebJobs,
-- Webjobs deployed with your App service
-- Webjobd deployed separately from your App Servicep
-The first kind is simple, as they will just be part of the zip file, along with the rest of the app. But for those that are deployed separately(e.g. Deploy webjobs after app service creation or create webjobs from portal after deployment) things are different because they can't just be uploaded to d:\home\site\wwwroot\app_data\jobs\..., which is read-only.
-
-To solve this, WebJobs is deployed to d:\home\site\jobs\... 
-Jobs from both locations can exist in the same app.
-
-Note: As this makes site\wwwroot read only this means that file operations will fail including the creation of the *disable.job*
-
 ## Run from external URL instead
 
 You can also run a 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 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](#fetch-a-package-from-azure-blob-storage-using-a-managed-identity) to enable the App Service runtime to access the package securely. 
@@ -71,10 +59,21 @@ az webapp config appsettings set --name <app-name> --resource-group <resource-gr
 
 If you publish an updated package with the same name to Blob storage, you need to restart your app so that the updated package is loaded into App Service.
 
-### Fetch a package from Azure Blob Storage using a managed identity
+### Access a package in Azure Blob Storage using a managed identity
 
 [!INCLUDE [Run from package via Identity](../../includes/app-service-run-from-package-via-identity.md)]
 
+## Deploy WebJob files when running from package
+
+There are two ways to deploy [WebJob](webjobs-create.md) files when you [enable running an app from package](#enable-running-from-package):
+
+
+- Deploy in the same ZIP package as your app: include them as you normally would in `<project-root>\app_data\jobs\...` (which maps to the deployment path `\site\wwwroot\app_data\jobs\...` as specified in the [WebJobs quickstart](webjobs-create.md#webjob-types)).
+- Deploy separately from the ZIP package of your app: Since the usual deployment path `\site\wwwroot\app_data\jobs\...` is now read-only, you can't deploy WebJob files there. Instead, deploy WebJob files to `\site\jobs\...`, which is not read only. WebJobs deployed to `\site\wwwroot\app_data\jobs\...` and `\site\jobs\...` both run.
+
+> [Note]
+> When `\site\wwwroot` becomes read-only, operations like the creation of the *disable.job* will fail.
+
 ## Troubleshooting
 
 - Running directly from a package makes `wwwroot` read-only. Your app will receive an error if it tries to write files to this directory.