When you create an application and run it in Azure, your code (and the way you configure it) is called a cloud service. This topic covers the basic concepts around cloud services.
Azure provides three compute models that you can use to host web applications: Web Sites, Cloud Services, and Virtual Machines. This topic provides an overview of the three models and information to help you decide which is right for your application.
Use Quick Create to create a new cloud service. When you’re done, you can upload and deploy a cloud service package in Azure.
To show your cloud service's dependencies on other resources, you can link an Azure SQL Database instance or a storage account to the cloud service.
To store files and data in the Blob, Table, and Queue services in Azure, you must create a storage account in the geographic region where you want to store the data. A storage account can contain up to 100 TB of blob, table, and queue data.
After you’ve created your cloud service, you can upload, test, and deploy your new service package using the Azure Management Portal.
Scale your cloud service by adding or removing role instances. If you link an Azure SQL Database instance to your cloud service, you can scale the database too.
You can configure the most commonly used settings for a cloud service in the Azure Management Portal. Or, if you like to update your configuration files directly, download a service configuration file to update, and then upload the updated file and update the cloud service with the configuration changes. Either way, the configuration updates are pushed out to all role instances.
If you need to update the code in an application for your cloud service, you’ll need to upload some content. This topic walks you through how to upload a new service package and service configuration file.
You can monitor key performance metrics for your cloud services in the Management Portal, and you can customize what you want to monitor to meet your needs.