Deploying to Azure with two web role instances used to work like a charm since at least one of the instances would remain active while the other was updated .. that's the point of having multiple instances, right?
Well lately, Azure seems to be failing on this end. I have even increased my deployed instances from two medium instances to three medium instances, but Azure still takes them ALL down in the process of updating the production deployment! (They will be in some kind of 'updating' state, rather than 'running')
I have always set the Roles to update to 'All' with no issues. Has something changed?
This is disturbing to say the least.
