Overview of Running a Windows Azure Application with Local Storage

http://msdn.microsoft.com/en-us/library/gg432983.aspx

Plan the storage configuration

Windows Azure storage services provide storage for binary and text data, messages, and structured data. The following storage options are provided for you to use with your application:

• The Blob service, for storing binary and text data. For more information see, Understanding Block Blobs and Page Blobs
  
  
• The Queue service, for storing messages that may be accessed by a client. For more information see, Addressing Queue Service Resources.
  
  
• The Table service, for structured storage for non-relational data. For more information, see Understanding the Table Service Data Model.
  
  
• Windows Azure drives, for mounting an NTFS volume accessible to code running in your Windows Azure service. For more information see, Using the Windows Azure Storage Services

Account name: devstoreaccount1
Account key: Eby8vdM02xNOcqFlqUwJPLlmEtlCDXJ1OUzFT50uSRZ6IFsuFq2UVErCz4I6tq/K1SZFPTOtr/KBHBeksoGMGw==

Using storage service URIs

How you address a resource in the Windows Azure storage services differs depending on whether the resource resides in Windows Azure or in the storage emulator services. One URI scheme is used to address a storage resource in Windows Azure, and another URI scheme is used to address a storage resource in the storage emulator. The difference is due to the fact that the local computer does not perform domain name resolution. Both URI schemes always include the account name and the address of the resource being requested.

Addressing cloud storage resources

<http|https>://<account-name>.<service-name>.core.windows.net/<resource-path>

The <account-name> is the name of your storage account. The <service-name> is the name of the service being accessed, and the <resource-path> is the path to the resource being requested. The following list shows the URI scheme for each of the storage services:

• Blob Service: <http|https>://<account-name>.blob.core.windows.net/<resource-path>
  
  
• Queue Service: <http|https>://<account-name>.queue.core.windows.net/<resource-path>
  
  
• Table Service: <http|https>://<account-name>.table.core.windows.net/<resource-path>
  
  

For example, the following address might be used for accessing a blob in the cloud:

http://myaccount.blob.core.windows.net/mycontainer/myblob.txt

Addressing local storage resources

http://<local-machine-address>:<port>/<account-name>/<resource-path>

The following format is used for addressing resources running in the storage emulator:

• Blob Service: http://127.0.0.1:10000/<account-name>/<resource-path>
  
  
• Queue Service: http://127.0.0.1:10001/<account-name>/<resource-path>
  
  
• Table Service: http://127.0.0.1:10002/<account-name>/<resource-path>
  
  

For example, the following address might be used for accessing a blob in the storage emulator:

http://127.0.0.1:10000/myaccount/mycontainer/myblob.txt