Training Course
Module 07:
Azure Virtual
Machines
1
Lesson 01: Configure Virtual Machines
Lesson 02: Configure Virtual Machine Availability
Lesson 03: Configure Virtual Machine Extensions
Lesson 04: Module 08 Lab
2
Lesson 01: Configure Virtual Machines
Review Cloud Services Responsibilities
Test and development, website hosting, storage, backup, recovery,
high-performance computing, big data analysis, and extended data center
4
Plan Virtual Machines
Start with the network
Name the virtual machine
Choose a location
• Each region has different hardware and service capabilities
• Locate Virtual Machines as close as possible to your users and to ensure
compliance and legal obligations
Consider pricing
• Compute costs 60+ Azure regions
Available in 140 countries
• Storage costs (consumption-based and reserved instances)
5
Determine Virtual Machine Sizing
A Series - Entry-level for dev/test G Series – Memory and storage optimized
B Series – Economical bursting H Series - High performance computing
D Series – General purpose compute L Series – Storage optimized
Dc Series – Protect data in use M Series – Memory optimized
E Series – In-memory hyper-threaded applications
Mv2 Series – Largest memory optimized
optimized
F Series – Compute optimized N Series – GPU enabled
6
Determine Virtual Machine Storage
Azure VM (Windows)
Each Azure VM has two or more disks:
• OS disk
• Temporary disk (contents can be lost)
• Data disks (optional)
C:\ D:\ F:\
OS and data disks reside in Azure Storage accounts: Temporary disk Data disk
OS disk
• Azure-based storage service
• Standard (HDD, SSD) or Premium (SSD), or Ultra
(SSD)
When creating an Azure VM, you can choose between:
• Managed disks (recommended)
• Unmanaged disks
Azure blob
7
Create Virtual Machines in the Portal
Basic (required) – Project details, Administrator
account, Inbound port rules
Disks – OS disk type, data disks
Networking – Virtual networks, load balancing
Management – Monitoring, Auto-shutdown,
Backup
Advanced – Add additional configuration,
agents, scripts or applications
8
Connect to Virtual Machines
Bastion Subnet for RDP/SSH Remote Desktop Protocol for Secure Shell Protocol for
through the Portal over SSL Windows-based Virtual Machines Linux based Virtual Machines
9
Connect to Windows Virtual Machines
Remote Desktop Protocol
(RDP) creates a GUI session and
accepts inbound traffic on TCP
port 3389
WinRM creates a command-line
session so can run scripts
10
Connect to Linux Virtual Machines
Authenticate with a SSH is an encrypted There are public and
SSH public key or connection protocol private keys
password that allows secure
logins over unsecured
connections
11
Lesson 02: Configure Virtual Machine
Availability
Plan for Maintenance and Downtime
Unplanned Hardware Unexpected Planned
Maintenance Downtime Maintenance
When the platform Unexpected Downtime Planned Maintenance
predicts a failure, it will is when a virtual events are periodic
issue an unplanned machine fails updates made to the
hardware maintenance unexpectedly Azure platform
event
Action: Automatically Action: No action
Action: Live migration migrate (heal)
13
Setup Availability Sets
Configure Configure each Combine a Load Use managed
multiple Virtual application tier Balancer with disks with the
Machines in an into separate Availability Sets Virtual Machine
Availability Set Availability Sets
14
Review Update and Fault Domains
Update domains allows Azure to
perform incremental or rolling
upgrades across a deployment.
During planned maintenance,
only one update domain is
rebooted at a time
Fault Domains are a group of
Virtual Machines that share a
common set of hardware, switches,
that share a single point of failure.
VMs in an availability set are placed
in at least two fault domains
15
Review Availability Zones
Unique physical locations in a region
Includes datacenters with independent
power, cooling, and networking
Protects from datacenter failures
Combines update and fault domains
Provides 99.99% SLA
16
Compare Vertical to Horizontal Scaling
Vertical scaling
Vertical scaling (scale up and scale down) is
the process of increasing or decreasing power
to a single instance of a workload; usually
manual
Horizontal scaling
Horizontal scaling (scale out and scale in) is
the process of increasing or decreasing the
number of instances of a workload; frequently
automated
17
Implement Scale Sets
Scale sets No pre- As demand As demand The process can
deploy a set provisioning of goes up goes down be manual,
of identical VMs is required VMs are VM are automated, or a
VMs added removed combination of
both
18
Create Scale Sets
Instance count. Number of VMs in the
scale set (0 to 1000)
Instance size. The size of each virtual
machine in the scale set
Azure Spot Instance. Unused capacity at a
discounted rate
Use managed disks
Enable scaling beyond 100 instances
19
Implement Autoscale
Define rules to Scale out Scale in (reduce) Schedule events Reduces
automatically (increase) the the number of to increase or monitoring
adjust capacity number of VMs in the set decrease at a and optimizes
VMs in the set fixed time performance
20
Configure Autoscale
Define a minimum, maximum, and
default number of VM instances
Create more advanced scale sets
with scale out and scale in
parameters
21
Thank you
22
