Sharing of thoughts and information is what blogging is all about. This way we can learn from each other. Post A Comment!These postings are provided "AS IS" with no warranties, and confers no rights. You assume all risk for your use.
Chris Di LulloSr. IT Pro Marketing Manager Twitter | LinkedIn Pierre Roman Twitter | LinkedIn Mitch Garvis Twitter | LinkedIn Anthony Bartolo Twitter | LinkedIn
If you’ve started reading from this post, you’ll need to go through the previous parts of this series before starting this one: Introduction Part 1: Provisioning and Configuring SQL Azure
The architecture of the application also calls for Windows Azure storage to store some of the application’s configuration data, as well as data for the ASP.NET providers.
If you’d like to find out more about Windows Azure Storage, read through the Windows Azure Storage section in Introduction to Windows Azure Platform on the Microsoft Patterns and Practices site.
Let’s get started.
Storage accounts have unique URL prefixes under the cloudapp.net domain. You’ll need to choose a unique prefix as this is the address that allows HTTP based access to the application’s storage services and you wouldn’t want someone else accessing your storage services.
That’s it for the storage account. We’ll come back to here later on in order to grab the configuration information the application will need in order to securely connect to the storage services.
Let’s go back to our to do list and see what we have to do next.