Terminology

DTU

DTU stands for Database Throughput Unit.

DTUs are based on a combination of CPU usage, memory, reads, and writes. It's a way to measure performance with a single number.
Resource Group

A resource group is a logical collection of assets. For instance, you'd have at least one resource group per application.

To create a resource group:
(as of Sept. 2019)
1) Open Azure console
2) In the left-hand menu > click Resource Groups > Create Resource Group
3) Fill in the form
4) Click Review + Create
Database

To create a SQL database hosted on Azure:

(as of Sept. 2019)
1) Open your Azure console
2) Click Create a Resource > SQL databases > Create SQL Database
3) Fill in the form
- During this, you have the option of loading the database from an Azure backup file
4) Create
5) Wait for the backend processes to set up your database
Web Service

.csdef

*.csdef is your Cloud Service Definition file.
Naming convention: ServiceDefinition.csdef.

It is an XML file.
It defines the service model and the number of roles.

The definition cannot be altered after you upload it.

Each ServiceDefinition must contain 1 to 25 roles (WebRole or WorkerRole).

Example:

    <?xml version="1.0" encoding="utf-8"?>
    <ServiceDefinition name="MyServiceName" xmlns="http://schemas.microsoft.com/ServiceHosting/2008/10/ServiceDefinition">
      <WebRole name="WebRole1" vmsize="Medium">
        <Sites>
          <Site name="Web">
            <Bindings>
              <Binding name="HttpIn" endpointName="HttpIn" />
            </Bindings>
          </Site>
        </Sites>
        <Endpoints>
          <InputEndpoint name="HttpIn" protocol="http" port="80" />
          <InternalEndpoint name="InternalHttpIn" protocol="http" />
        </Endpoints>
        <Certificates>
          <Certificate name="Certificate1" storeLocation="LocalMachine" storeName="My" />
        </Certificates>
        <Imports>
          <Import moduleName="Connect" />
          <Import moduleName="Diagnostics" />
          <Import moduleName="RemoteAccess" />
          <Import moduleName="RemoteForwarder" />
        </Imports>
        <LocalResources>
          <LocalStorage name="localStoreOne" sizeInMB="10" />
          <LocalStorage name="localStoreTwo" sizeInMB="10" cleanOnRoleRecycle="false" />
        </LocalResources>
        <Startup>
          <Task commandLine="Startup.cmd" executionContext="limited" taskType="simple" />
        </Startup>
      </WebRole>

      <WorkerRole name="WorkerRole1">
        <ConfigurationSettings>
          <Setting name="DiagnosticsConnectionString" />
        </ConfigurationSettings>
        <Imports>
          <Import moduleName="RemoteAccess" />
          <Import moduleName="RemoteForwarder" />
        </Imports>
        <Endpoints>
          <InputEndpoint name="Endpoint1" protocol="tcp" port="10000" />
          <InternalEndpoint name="Endpoint2" protocol="tcp" />
        </Endpoints>
      </WorkerRole>
    </ServiceDefinition>

Sites: websites or web applications hosted in IIS7

InputEndpoints: endpoints for contacting this service

InternapEndpoints: endpoints used by this service's role instances to communicate with each other

ConfigurationSettings: settings for a specific role

Certificates: certificates needed to a role

LocalResources: a local directory in which a role is running

Imports: imported modules

Startup: tasks to run when a role starts

.cscfg

*.cscfg is your Cloud Service Configuration file.
Naming convention: ServiceConfig.cscfg.

It is an XML file.
It provides settings to the service, individual roles, and the number of role instances.

The configuration can be altered after you upload it.

.cspkg

*.cspkg is your Service Package.

It is a zip file.
It contains the application code and model.
The model is made up of the *.csdef and *.cscfg files.

Quick Create

Create a new cloud service

Upload (deploy) a cloud service package

Custom Create

If you already have your service ready to upload, you can do all the Quick Create steps at once here.

From Visual Studio

1) Create a web service
2) In Visual Studio > right-click on project > Publish Web App (VS 2017) or Publish (VS 2015)
3) Select target Microsoft Azure App Service
4) (if not already) log into Microsoft Azure
5) Select an existing Web App (or create a new one)
6) Check the publish form is filled out correctly > Publish
7) Watch of the Success message in the output panel
Upload Database

To upload a SQL Server database to Azure:

(as of Sept. 2019)
1) You'll need an Azure Server setup to deploy to
2) Open your database in SSMS (SQL Server Management Studio)
3) Right-click database > Tasks > Deploy Database to Microsoft Azure SQL Database
4) Fill in the form
- You will need to allow access to Azure through your firewall
- You cannot deploy to a pre-existing Azure database, it must be a new one