An Azure backup service that provides built-in management at scale.
Hello James, unfortunately Azure App Service doesn’t keep automatic point-in-time backups unless you’ve explicitly configured them. If you didn’t enable backups before that publish, there isn’t a built-in “undo” for the overwritten folder. Here are a few things you can try and tips for next time:
- Check your deployment artifacts in Kudu
- Go to https://<your-app>.scm.azurewebsites.net → Debug Console → site → deployments
- You’ll often see the ZIP packages from recent deployments under “SitePackages” or numbered folders.
- If you find the previous package, download and extract it, then copy the folder you need back into wwwroot.
- Redeploy from your source control or CI/CD pipeline
- If your app code lives in GitHub, Azure Repos, or local source control, grab the last good commit and push it again.
- Use a staging slot next time
- Deploy to a non-production slot first, validate changes, then swap into production to avoid accidental overwrites.
- Enable App Service backups for future restores
- In the Azure Portal, browse to your Web App → “Backups” blade → configure a storage account and schedule.
- You can trigger on-demand backups or keep hourly/daily snapshots.
- Automate backup with CLI/PowerShell
- Azure CLI: az webapp config backup create --resource-group RG --webapp-name MyApp --container-url "<your-storage-SAS-URL>"
- PowerShell: New-AzWebAppBackup -ResourceGroupName RG -Name MyApp -StorageAccountUrl "<your-storage-SAS-URL>"
Hope that helps!
Reference list:
- Manage Back up
- Restore a backup with Azure CLI (az webapp config snapshot)
- Kudu deployment artifacts and Debug Console
- Deploy to and swap deployment slots
If the information was useful, please consider accepting the answer and upvoting. Feel free to reach out if you need any further assistance. Thank you.