I suggest do some googling for "azure blob storage mount as drive on vm image"

you can create a web role vm image that has a mounted drive that is blob storage but works like any hard drive, if you save the vm as an image then when it gets re-created or re-provisioned it will already have the drive mapped on each instance, then you can install the web site as in virtual directory or at least the /Data folder which is the writable portion could be a virtual directory in IIS that uses the blob drive so all nodes of the web role vm will use the same blob storage drive.

The advantage of this approach is that it is just like any hard drive so nothing special has to be done, files can be uploaded the normal way.

If you use Azure Websites (as opposed to setting up your own web role vms), I believe they already work this way, you get scalability but you don't have to worry about doing anything special for file uploads because under the hood Azure Websites uses azure drives that map to blob storage but work just like a normal file system.

Hope that helps,

Joe

the sync framework was one way to keep the local storage of the vms in sync by syncing the local drive from blob storage, but using a blob storage mounted as a drive is a better solution. the sync solution was created before it became possible to mount blob storage as a drive, now that it is possible I do not recommend using the sync framework.

I suggest do some research, do not expect me to give you step by step advice

the easier solution is to use Azure Websites, if you want to use web role vms (which is a more complex approach) then do some research as I suggested about how to make a vm image with the blob storage already mounted as a drive.