Az900 p3.2

Learning objectives
After completing this module, you’ll be able to:
 Compare compute types, including container instances, virtual machines, and functions.
 Describe virtual machine options, including virtual machines (VMs), virtual machine scale
sets, virtual machine availability sets, and Azure Virtual Desktop.
 Describe resources required for virtual machines.
 Describe application hosting options, including Azure Web Apps, containers, and virtual
machines.
 Describe virtual networking, including the purpose of Azure Virtual Networks, Azure virtual
subnets, peering, Azure DNS, VPN Gateway, and ExpressRoute.
 Define public and private endpoints.
Describe Azure Virtual Machines
With Azure Virtual Machines (VMs), you can create and use VMs in the cloud. VMs provide
infrastructure as a service (IaaS) in the form of a virtualized server and can be used in many ways.
Just like a physical computer, you can customize all of the software running on your VM. VMs are an
ideal choice when you need:
 Total control over the operating system (OS).
 The ability to run custom software.
 To use custom hosting configurations.
An Azure VM gives you the flexibility of virtualization without having to buy and maintain the
physical hardware that runs the VM. However, as an IaaS offering, you still need to configure,
update, and maintain the software that runs on the VM.
You can even create or use an already created image to rapidly provision VMs. You can create and
provision a VM in minutes when you select a preconfigured VM image. An image is a template used
to create a VM and may already include an OS and other software, like development tools or web
hosting environments.
Scale VMs in Azure
You can run single VMs for testing, development, or minor tasks. Or you can group VMs together to
provide high availability, scalability, and redundancy. Azure can also manage the grouping of VMs for
you with features such as scale sets and availability sets.
Virtual machine scale sets
Virtual machine scale sets let you create and manage a group of identical, load-balanced VMs. If
you simply created multiple VMs with the same purpose, you’d need to ensure they were all
configured identically and then set up network routing parameters to ensure efficiency. You’d also
have to monitor the utilization to determine if you need to increase or decrease the number of
VMs.
Instead, with virtual machine scale sets, Azure automates most of that work. Scale sets allow you
to centrally manage, configure, and update a large number of VMs in minutes. The number of VM
instances can automatically increase or decrease in response to demand, or you can set it to scale
based on a defined schedule. Virtual machine scale sets also automatically deploy a load balancer
to make sure that your resources are being used efficiently. With virtual machine scale sets, you
can build large-scale services for areas such as compute, big data, and container workloads.
Virtual machine availability sets
Virtual machine availability sets are another tool to help you build a more resilient, highly
available environment. Availability sets are designed to ensure that VMs stagger updates and have
varied power and network connectivity, preventing you from losing all your VMs with a single
network or power failure.
Availability sets do this by grouping VMs in two ways: update domain and fault domain.
 Update domain: The update domain groups VMs that can be rebooted at the same time.
This allows you to apply updates while knowing that only one update domain grouping
will be offline at a time. All of the machines in one update domain will be updated. An
update group going through the update process is given a 30-minute time to recover
before maintenance on the next update domain starts.
 Fault domain: The fault domain groups your VMs by common power source and network
switch. By default, an availability set will split your VMs across up to three fault domains.
This helps protect against a physical power or networking failure by having VMs in
different fault domains (thus being connected to different power and networking
resources).
Best of all, there’s no additional cost for configuring an availability set. You only pay for the VM
instances you create.
Examples of when to use VMs
Some common examples or use cases for virtual machines include:
 During testing and development. VMs provide a quick and easy way to create different OS
and application configurations. Test and development personnel can then easily delete the
VMs when they no longer need them.
 When running applications in the cloud. The ability to run certain applications in the public
cloud as opposed to creating a traditional infrastructure to run them can provide
substantial economic benefits. For example, an application might need to handle
fluctuations in demand. Shutting down VMs when you don't need them or quickly starting
them up to meet a sudden increase in demand means you pay only for the resources you
use.
 When extending your datacenter to the cloud: An organization can extend the capabilities
of its own on-premises network by creating a virtual network in Azure and adding VMs to
that virtual network. Applications like SharePoint can then run on an Azure VM instead of
running locally. This arrangement makes it easier or less expensive to deploy than in an
on-premises environment.
 During disaster recovery: As with running certain types of applications in the cloud and
extending an on-premises network to the cloud, you can get significant cost savings by
using an IaaS-based approach to disaster recovery. If a primary datacenter fails, you can
create VMs running on Azure to run your critical applications and then shut them down
when the primary datacenter becomes operational again.
Move to the cloud with VMs
VMs are also an excellent choice when you move from a physical server to the cloud (also known
as lift and shift). You can create an image of the physical server and host it within a VM with little
or no changes. Just like a physical on-premises server, you must maintain the VM: you’re
responsible for maintaining the installed OS and software.
VM Resources
When you provision a VM, you’ll also have the chance to pick the resources that are associated
with that VM, including:
 Size (purpose, number of processor cores, and amount of RAM)
 Storage disks (hard disk drives, solid state drives, etc.)
 Networking (virtual network, public IP address, and port configuration)

Az900 p3.2

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Az900 p3.2

Uploaded by

Copyright:

Available Formats

Learning objectives

After completing this module, you’ll be able to:

 Describe resources required for virtual machines.

 Define public and private endpoints.

Describe Azure Virtual Machines

 Total control over the operating system (OS).

 The ability to run custom software.

 To use custom hosting configurations.

Scale VMs in Azure

Virtual machine scale sets

Virtual machine availability sets

Examples of when to use VMs

Some common examples or use cases for virtual machines include:

Move to the cloud with VMs

 Size (purpose, number of processor cores, and amount of RAM)

 Storage disks (hard disk drives, solid state drives, etc.)

 Networking (virtual network, public IP address, and port configuration)

You might also like