Sync content from a cloud folder to Azure App Service
This article shows you how to sync your content to Azure App Service from Dropbox and OneDrive.
With the content sync approach, your work with your app code and content in a designated cloud folder to make sure it's in a ready-to-deploy state, and then sync to App Service with the click of a button.
Because of underlying differences in the APIs, OneDrive for Business is not supported at this time.
Note
The Development Center (Classic) page in the Azure portal, which is the old deployment experience, will be deprecated in March, 2021. This change will not affect any existing deployment settings in your app, and you can continue to manage app deployment in the Deployment Center page.
Enable content sync deployment
In the Azure portal, navigate to the management page for your App Service app.
From the left menu, click Deployment Center > Settings.
In Source, select OneDrive or Dropbox.
Click Authorize and follow the authorization prompts.
You only need to authorize with OneDrive or Dropbox once for your Azure account. To authorize a different OneDrive or Dropbox account for an app, click Change account.
In Folder, select the folder to synchronize. This folder is created under the following designated content path in OneDrive or Dropbox.
- OneDrive:
Apps\Azure Web Apps - Dropbox:
Apps\Azure
- OneDrive:
Click Save.
Synchronize content
In the Azure portal, navigate to the management page for your App Service app.
From the left menu, click Deployment Center > Redeploy/Sync.
Click OK to confirm the sync.
Disable content sync deployment
In the Azure portal, navigate to the management page for your App Service app.
From the left menu, click Deployment Center > Settings > Disconnect.
What happens to my app during deployment?
All the officially supported deployment methods make changes to the files in the /home/site/wwwroot folder of your app. These files are used to run your app. So the deployment can fail because of locked files. The app might also behave unpredictably during deployment because the files aren't all updated at the same time. This behavior is undesirable for a customer-facing app. There are a few ways to avoid these issues:
- Run your app directly from the ZIP package, without unpacking it.
- Stop your app or enable offline mode for it during deployment. For more information, see Deal with locked files during deployment.
- Deploy to a staging slot with auto swap turned on.