1. The storage is by default on 3 disks which are replicated (redundant) in another location. This redundancy could be disabled for a 30% discount.
2. Make sure to give a 45-minute head start to disk replication if doing a performance test to get realistic figures.
3. VM Status of ‘Stopped (DeAllocated)’ means not charged for compute but charged for storage.
4. The VM storage is in the form of VHDs hence making the VMs easily transportable between Azure and local hypervisor. These VHDs can be easily browsed as standard windows folders by tools like CloudXplorer.
5. Availability Set: 2 VMs which provide a common function i.e. a redundant machine
6. Load Balanced Set: Load balancing function across a availability set for balancing load.
7. $$ charging:
A) Charged by minute and not rounded up to an hour
B) MSDN server products have use rights within Azure
8. Connectivity to Azure Cloud:
A) Point to site connectivity: This uses the built-in Windows VPN client over SSTP protocol (like https). This works via a VPN gateway in Azure network.
B) Site to Site connec
C) To create this virtual network – Azure offers a click through wizard or can use XML
files to create .cfg files. This requires adding a roaming IP address range and a
subnet range/s for the virtual network. Also, required is adding a virtual gateway (/8
range). The virtual gateway is not created automatically and is required to be
manually created after the virtual network is created. This is because virtual network is not charged but virtual gateway is.
D) Need to create public-private certificates pair and upload public key of the certificate to Azure and then download the VPN client to connect.
E) Can create multiple child certificates from the root certificate to hand over to other VPN clients.
9. Azure Web applications can be deployed through Csdef (Service definition file) and ccfg files (Service configuration file) – number of instances, virtual network name etc can be specified.
10. Availability sets cannot be edited once created for a VM