Azure Cloud Services

Whether you are a developer or an IT Pro using Azure
then you have been through one of the Major Azure Services, the Cloud
Services.  Especially if you are a
developer and dealing with Azure WebRoles or WorkerRoles or an IT Pro dealing
with the Azure
Virtual machines, once you start the process of publishing the application
or starting the virtual machine, you are always required to run multiple
instances on Azure with for the same application or workload to have the SLA
agreement with Microsoft.  As you are
doing this, you will find that the Cloud Service is the way of grouping your application
or workload together under a DNS name.  To
keep in mind that this DNS name is not your application domain, you can for
sure choose your domain and assign it to your application or workload on your
Virtual Machine.

What I wanted to clarify is that the Azure Cloud Services however
you work with whether as a developer or as an IT pro, its main target to group the
same instances whatever their number was or the virtual machines with the same
workload for 2 main reasons, which are load balancing and scalability.  For the load balancing, the cloud service helps
distributing the incoming traffic along your number of instances or VMs.  For the scalability, this how Microsoft Azure
is helping you to always meet your demand based on the incoming traffic, so if
the traffic increase you can scale the number of instances or Virtual Machines
to always have your services available.