Cannot deploy to web app: Not enough space on the disk

Question

Cannot deploy to web app: Not enough space on the disk

Krishna Moniz 5

Issue

When trying to deploy to my azure app service, I get a not enough space on the disk error.

Initiating deployment
Deploying from local path: C:\KBs\OffshoreTreatment_Development\ot-azv-test-origin\Deploy\AZURE\azv_deploy_20260218092653.zip
An error occurred during deployment. Status Code: 500, Details: {"Message":"An error has occurred.","ExceptionMessage":"There is not enough space on the disk.\r\n","ExceptionType":"System.IO.IOException","StackTrace":"   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)\r\n   at System.IO.FileStream.WriteCore(Byte[] buffer, Int32 offset, Int32 count)\r\n   at System.IO.FileStream.Write(Byte[] array, Int32 offset, Int32 count)\r\n   at System.IO.Stream.<>c.<BeginWriteInternal>b__46_0(Object <p0>)\r\n   at System.Threading.Tasks.Task`1.InnerInvoke()\r\n   at System.Threading.Tasks.Task.Execute()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.IO.Stream.EndWrite(IAsyncResult asyncResult)\r\n   at System.IO.FileStream.EndWrite(IAsyncResult asyncResult)\r\n   at System.IO.Stream.<>c.<BeginEndWriteAsync>b__53_1(Stream stream, IAsyncResult asyncResult)\r\n   at System.Threading.Tasks.TaskFactory`1.FromAsyncTrimPromise`1.Complete(TInstance thisRef, Func`3 endMethod, IAsyncResult asyncResult, Boolean requiresSynchronization)\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Kudu.Services.ByteRanges.HttpRequestMessageExtensions.<CopyToAsync>d__1.MoveNext() in C:\\__w\\1\\s\\Kudu.Services\\ByteRanges\\HttpRequestMessageExtensions.cs:line 67\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Kudu.Services.Deployment.PushDeploymentController.<>c__DisplayClass16_0.<<PushDeployAsync>b__0>d.MoveNext() in C:\\__w\\1\\s\\Kudu.Services\\Deployment\\PushDeploymentController.cs:line 519\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Kudu.Contracts.Infrastructure.LockExtensions.<LockOperationAsync>d__6.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Kudu.Services.Infrastructure.LockExtensions.<LockHttpOperationAsync>d__1.MoveNext() in C:\\__w\\1\\s\\Kudu.Services\\Infrastructure\\LockExtensions.cs:line 30\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)\r\n   at Kudu.Services.Deployment.PushDeploymentController.<PushDeployAsync>d__16.MoveNext() in C:\\__w\\1\\s\\Kudu.Services\\Deployment\\PushDeploymentController.cs:line 498\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)\r\n   at Kudu.Services.Deployment.PushDeploymentController.<OneDeploy>d__14.MoveNext() in C:\\__w\\1\\s\\Kudu.Services\\Deployment\\PushDeploymentController.cs:line 434\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Threading.Tasks.TaskHelpersExtensions.<CastToObject>d__1`1.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Web.Http.Controllers.ApiControllerActionInvoker.<InvokeActionAsyncCore>d__1.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Web.Http.Filters.ActionFilterAttribute.<CallOnActionExecutedAsync>d__6.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Web.Http.Filters.ActionFilterAttribute.<CallOnActionExecutedAsync>d__6.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Web.Http.Filters.ActionFilterAttribute.<ExecuteActionFilterAsyncCore>d__5.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Web.Http.Filters.ActionFilterAttribute.<CallOnActionExecutedAsync>d__6.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Web.Http.Filters.ActionFilterAttribute.<CallOnActionExecutedAsync>d__6.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Web.Http.Filters.ActionFilterAttribute.<ExecuteActionFilterAsyncCore>d__5.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Web.Http.Controllers.ActionFilterResult.<ExecuteAsync>d__5.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Web.Http.Controllers.ExceptionFilterResult.<ExecuteAsync>d__6.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Web.Http.Controllers.ExceptionFilterResult.<ExecuteAsync>d__6.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Web.Http.Dispatcher.HttpControllerDispatcher.<SendAsync>d__15.MoveNext()"}, Please visit https://ot-azv-test.scm.azurewebsites.net/api/deployments/latest to get more information about your deployment

When I check File system storage in my service plan it clearly shows that I have enough space.

I have made previous deployments to the web app. This is my 5th deployment to the web app (in the last ~6months)

What is wrong here and how can I resolve it?

Attempt to resolve

Clean up files

I tried restarting the web app. I tried deleting all temporary files. I took all the steps described in How to troubleshoot temporary storage on Azure App Service Nothing helped.

Upgrade to different tier (D1)

The web app is in F1 (free) service plan. I upgraded to D1, the problem persisted (note: both F1 and D1 have 1Gb of remote storage)

Upgrade to different tier (B1)

I upgraded to B1 and could deploy (B1 has 10Gb of remote storage). Next tried to downgrade back to either D1 or F1 and could not.

I get the following error:

Scale operation failed: Storage usage quota exceeded. Cannot update or delete a server farm. Your current usage is 2383 Mb and quota after the operation will be 2048 Mb. Please make sure your file system storage of the remaining App Service Plans in this ResourceGroup and Region is below the combined limit of the target pricing tier's.

However, when I check the File system storage, it says that I'm only using 418.67 Mb.

Assumptions/findings

I get the impression that the web app is not properly cleaning up temporary files and not properly reporting disk usage, nor giving me the ability to clean up the temporary files myself.

How do I resolve the not enough space on the disk error?

Praneeth Maddali 12,670 Reputation points Microsoft External Staff Moderator

2026-02-20T15:52:54.8233333+00:00
Hi @Krishna Moniz

Thank you for sharing all the details it makes troubleshooting much easier. It appears you're encountering a common problem with Azure App Service's temporary storage limits. When deploying, actions like extracting ZIP files use up space in the temp directory (D:\local), which is separate from the persistent storage shown in the portal. This temp space is limited by your plan tier; for F1 and D1, it's usually about 500 MB and can fill up with caches, logs, or old deployment files. Upgrading to B1 increases this limit, which allowed your deployment, but downgrading can fail if the aggregate usage, including hidden temp files, exceeds the lower tier's cap.

Here are some steps you can try:

Clean up temp files via Kudu: Go to your app's Kudu site, use the Debug console (CMD) to check D:\local usage, and delete unnecessary files, especially in D:\local\Temp. Also, clear out large logs in D:\home\LogFiles. Restart the app afterward.

Use Run from Package: Set WEBSITE_RUN_FROM_PACKAGE=1 in your app's settings to avoid extracting ZIPs during deployment, which saves temp space.

Review aggregate usage: Check all apps in the same resource group/region from the App Service Plan's Quotas blade and clean up temp storage as needed. If usage still seems high, try the Disk Analysis tool under Diagnose and solve problems in the portal.

Clean old deployment artifacts (where possible): You can review and remove older ZIP deployment artifacts and logs using the Kudu console, as these may consume temporary local storage used during deployments. Please note that some temporary files are managed by the platform and may not be fully visible or removable.

Reference :

https://github.com/projectkudu/kudu/wiki/Understanding-the-Azure-App-Service-file-system

https://learn.microsoft.com/en-us/azure/app-service/deploy-run-package

https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits

https://learn.microsoft.com/en-us/troubleshoot/azure/devops/azure-web-app-services-related-issues

https://learn.microsoft.com/en-us/azure/app-service/deploy-zip?tabs=cli

Kindly let us know if the above helps or you need further assistance on this issue.

Please "upvote" if the information helped you. This will help us and others in the community as well
Krishna Moniz 5 Reputation points

2026-02-20T18:54:40.49+00:00
Hi Praneeth,

I can't access D:\
But, there is a C:\local. I've cleared C:\local\Temp, C:\home\LogFiles.
No help.

This allowed me to deploy, but it doesn't resolve the larger issue of there not being enough space.

There is only one app in the service plan. I can't find the "Disk Analysis tool" in Diagnose and solve problems. Can you specify which tool exactly? I would appreciate a screenshot.

Where exactly can I see old deployment artifacts? I think I removed everything I can using the Kudu console.

As for the temporary files are managed by the platform and may not be fully visible or removable. Is there a way i can force the platform to clean up temporary files?
Praneeth Maddali 12,670 Reputation points Microsoft External Staff Moderator

2026-02-23T01:08:45.47+00:00
Hi @Krishna Moniz

Thanks for the detailed follow‑up you’ve already done the right troubleshooting steps, which helps narrow this down.

Why cleanup didn’t fully resolve the issue

On Windows‑based Azure App Service, deployment uses temporary local storage (for example C:\local / %TEMP%) that’s separate from the persistent storage shown in the Azure portal (C:\home). Clearing C:\local\Temp and C:\home\LogFiles removes what’s your visible, but some temporary files are platform‑managed or locked by the deployment infrastructure and aren’t always visible or removable. There isn’t a supported way to force Azure App Service to fully reset this temp storage on an existing worker, especially on F1/D1 plans. Microsoft explains this behavior here:

Understanding the Azure App Service file system: https://github.com/projectkudu/kudu/wiki/Understanding-the-Azure-App-Service-file-system

Troubleshoot temporary storage on Azure App Service: https://learn.microsoft.com/en-us/troubleshoot/azure/app-service/temporary-storage-for-azure-app-service

About the Disk Analysis / diagnostics tool

In the portal, go to App Service > Diagnose and solve problems, then search for “Temp” and open Temp File Usage on Workers under Availability and Performance. This detector shows temp‑storage usage and the quota enforced by your App Service Plan. Note that visibility is limited on Free/D1 tiers.

Reference: https://learn.microsoft.com/en-us/azure/app-service/overview-diagnostics

Where old deployment artifacts live

Older ZIP‑deploy artifacts and extraction folders can exist in platform‑managed temp locations used by Kudu/ZIP Deploy. You’ve already removed everything that’s you‑accessible via Kudu; any remaining usage is managed by the platform and can’t be manually cleaned.

How to fix this going forward (supported options)

At this point, there are only a few reliable, Microsoft‑supported ways to prevent the issue:

Use Run‑From‑Package Set WEBSITE_RUN_FROM_PACKAGE=1. This runs the app directly from the ZIP package and avoids extracting files into temp storage during deployment.

Reference: https://learn.microsoft.com/en-us/azure/app-service/deploy-run-package

Stay on a higher tier (B1 or above) Higher tiers provide more temporary storage, which is why deployment succeeded there.

Create a new App Service Plan (if you must stay on F1/D1) A new plan starts with clean temp storage.

You’ve already cleaned everything that can be cleaned manually. The remaining space usage is expected platform behavior on F1/D1 and can’t be force‑reset. The most stable fix is Run‑From‑Package, a higher SKU, or a new App Service Plan.

Kindly let us know if the above helps or you need further assistance on this issue.

Please "upvote" if the information helped you. This will help us and others in the community as well.
Praneeth Maddali 12,670 Reputation points Microsoft External Staff Moderator

2026-02-24T05:44:54.73+00:00

Hi @Krishna Moniz

Just following up to see if your issue has been resolved or if you had a chance to review my earlier comment?
Krishna Moniz 5 Reputation points

2026-02-24T16:37:13.2533333+00:00

Hi Praneeth,

The remaining space usage is expected platform behavior on F1/D1 and can’t be force‑reset. The most stable fix is Run‑From‑Package, a higher SKU, or a new App Service Plan.

I guess that there is nothing else that you can do. Thank you for your effort.

However, let me be clear. This is unacceptable expected platform behavior from Azure. Microsoft should not leave customers with lingering space usage issues that cannot be reset, especially on entry-level SKUs. Forcing users into higher tiers or workarounds undermines trust in the platform’s reliability and fairness.

1 answer

Your answer

Krishna Moniz 5 Reputation points

2026-02-20T18:54:40.49+00:00

Hi Praneeth,

I can't access D:\
But, there is a C:\local. I've cleared C:\local\Temp, C:\home\LogFiles.
No help.

This allowed me to deploy, but it doesn't resolve the larger issue of there not being enough space.

There is only one app in the service plan. I can't find the "Disk Analysis tool" in Diagnose and solve problems. Can you specify which tool exactly? I would appreciate a screenshot.

Where exactly can I see old deployment artifacts? I think I removed everything I can using the Kudu console.

As for the temporary files are managed by the platform and may not be fully visible or removable. Is there a way i can force the platform to clean up temporary files?
Praneeth Maddali 12,670 Reputation points Microsoft External Staff Moderator

2026-02-24T05:44:54.73+00:00

Hi @Krishna Moniz

Just following up to see if your issue has been resolved or if you had a chance to review my earlier comment?
Krishna Moniz 5 Reputation points

2026-02-24T16:37:13.2533333+00:00

Hi Praneeth,

The remaining space usage is expected platform behavior on F1/D1 and can’t be force‑reset. The most stable fix is Run‑From‑Package, a higher SKU, or a new App Service Plan.

I guess that there is nothing else that you can do. Thank you for your effort.

However, let me be clear. This is unacceptable expected platform behavior from Azure. Microsoft should not leave customers with lingering space usage issues that cannot be reset, especially on entry-level SKUs. Forcing users into higher tiers or workarounds undermines trust in the platform’s reliability and fairness.

Answer 1

The error message you're encountering, not enough space on the disk, typically indicates that your Azure App Service is hitting its storage quota limits. Here are some steps and considerations to help resolve this issue:

Check Disk Quota: Even though the File system storage shows you are using 418.67 Mb, the actual quota can be affected by temporary files and other hidden storage usage. Ensure that you are not exceeding the limits set for your current pricing tier.
Temporary Storage: Azure App Service uses temporary storage that can fill up quickly. If your application is generating a lot of temporary files, this can lead to the error you are seeing. You may want to investigate the usage of temporary storage and clean it up. Follow the guidance in the article on how to troubleshoot temporary storage to ensure you are managing this effectively.
Upgrade Plan: You mentioned that upgrading to B1 allowed you to deploy successfully. This suggests that your application may require more storage than what is available in the F1 or D1 plans. If you need to downgrade back to a lower tier, ensure that your total storage usage is below the limits of that tier. You may need to clean up additional files or reduce the overall size of your application.
Deployment Artifacts: Ensure that previous deployment artifacts are not consuming space. Sometimes, old deployments can leave residual files that take up space. You can check the Kudu console to see if there are any old files that can be deleted.
Monitoring Disk Usage: Continuously monitor your disk usage through the Azure portal to ensure that you are aware of how much space is being used and what is consuming it. This can help prevent future issues.
Contact Support: If you continue to encounter issues despite following these steps, consider reaching out to Azure support for assistance, as they can provide more detailed insights into your specific environment and usage.

By following these steps, you should be able to address the not enough space on the disk error and manage your Azure App Service storage more effectively.