![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(163.2, 30%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJM%3C/text%3E%3C/svg%3E)
Azure Cloud Services
An Azure platform as a service offer that is used to deploy web and cloud applications.
749 questions
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(54.400000000000006, 73%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
The drives shown in the image:
C: - Temporary Storage - This is ephemeral storage. This is actually the least reliable location despite appearing to retain data. Its content is lost during VM reboots, restarts, or re-deployments.
D: - Windows - This is your system/OS drive in Cloud Services. This is typically the temporary drive in Azure VMs It's also unreliable for persistent storage. Do not use this drive for your own app data
E: - Local Disk - This appears to be an additional attached disk and is a persistent drive backed by your uploaded service package or attached data disk. This is the safest location to use for storing application data that needs to persist across reboots and re-deployments.
For reliable local storage that your application can depend on use the E: Drive. Since it's labeled "Local Disk" and isn't marked as temporary, this is your best one for persistent storage among the shown options.
For critical data consider using Azure Blob Storage or Azure Files for data that must never be lost, as these are cloud-backed storage solutions.
If you have any further queries, let me know. If the information is helpful, please click on Upvote and Accept Answer on it.