How to setup availability sets on Windows Azure and deploy an MVP that will be….available….

cpard's Blog

A few weeks ago we wrote a post about “How to launch your MVP in a budget with BizSpark” at the Apirise blog. The post briefly explains how someone can build an early MVP with BizSpark and Azure without binding to the Microsoft technologies stack! This post is a sequel of the original post but a bit more technical this time.

What we’ll try to do in this post, is to demonstrate how we can deal with the “availability” of our application (or MVP in the current context) when we build it on a cloud platform like Azure. For this reason we’ll discuss concepts like the “Availability Sets” of the Azure cloud platform and what technologies we can use in order to utilize the availability that the cloud service offers to us. We’ll mess a bit with replication but having the availability in mind and not the scalability of…

View original post 845 more words

Deployment credentials for Windows Azure Web services

When it comes to Windows Azure I always comment their UI and the simplicity of some of the operations provided by Microsoft.

When deploying a website though there is something that although seems simple enough it may not be what everyone thinks when uses it for the first time. That is the Deployment Credentials.

I found an excellent wiki from which I will replicate here.

A quick idea…

There are the User-level credentials and Site-level credentials. What you see on the right corner is User-level! These are chosen by us and are tied to OUR Live ID < the one connected at Azure portal at that time> and not not! NOT! <yes 3 times> to a particular web site. The UI here is a bit confusing. These are not credentials that you need to change each time… Did it 2-3 times… wrong! finally found out why…

Continue reading