Thanks for your reply.
This means that the scale out part you guys are talking about are more for when you want geo located responses, such as having different datacenters in EU/US.
I tried to turn up the instance count on one of the sites, and the result was that the management site (site/composite/top.aspx) didnt load properly. Maybe I was to fast to load the site before it had configured it correctly. (will try again and monitor the log files properly).
Just to be 100% sure: When i turn up a instance count on one deployment. This starts up new virtual machines that starts by syncing stuff from the blob storage. But what happens when i hit my site and start editing the content -> i get the response from one of the instances and makes some changes, it will be stored back to the blob. Will the other instance automatic notice this and download new content? (I dont think that is the case and might need you to clarify this further).
"Instances are meant as 'azure instances' - number of servers running your package." -> when i scale up the instance count in azure, new servers are started running the package and as you also write. They will have the same name. Do that not mean that it is NOT SAFE to increase the count? It is the same as deploying the packaged to another server with the same blob names and hence it will fail as its not build for two sites using the same blob folders?
Hope you can see my problem and tell me where I am wrong. or tell me that i am right and should not turn up the azure instance count.