| Type | Windows & Linux Sizes | Description |
|---|---|---|
| General purpose | B, Dsv3, Dv3, DSv2, Dv2, Av2 | Balanced CPU-to-memory ratio. Ideal for testing and development, small to medium databases, and low to medium traffic web servers. |
| Compute optimized | Fsv2, Fs, F | High CPU-to-memory ratio. Good for medium traffic web servers, network appliances, batch processes, and application servers. |
| Memory optimized | Esv3, Ev3, M, GS, G, DSv2, Dv2 | High memory-to-CPU ratio. Great for relational database servers, medium to large caches, and in-memory analytics. |
| Storage optimized | Ls | High disk throughput and IO. Ideal for Big Data, SQL, and NoSQL databases. |
| GPU | NV, NC, NCv2, NCv3, ND | Specialized virtual machines targeted for heavy graphic rendering and video editing, as well as model training and inferencing (ND) with deep learning. Available with single or multiple GPUs. |
| High performance compute | H | Our fastest and most powerful CPU virtual machines with optional high-throughput network interfaces (RDMA). |
Azure ensures that the VMs you place within an Availability Set run across multiple physical servers, compute racks, storage units, and network switches.
- Fault Domains (2 default) – across compute racks, separate power
- Update Domains (5 default) – Within an availability set, individual VMs are spread across up to 20 update domains (UDs). During scheduled maintenance, only a single update domain is impacted at any given time.
- Managed Disks (default) – auto creation and scaling
| Uptime % | Downtime min/month | Downtime hr/yr | |
|---|---|---|---|
| VM | 99.9 (three nines) | 43 | 8 |
| Availability Set | 99.95 (three and one half nines) 21 | 4 | |
| Availability Zone | 99.99 (four nines) | 4.3 | 52 min |
VM SLA Wikipedia High Availability
A virtual machine scale set allows the deployment and management a set of identical, auto-scaling virtual machines. You can scale the number of VMs in the scale set manually or define rules to auto-scale based on resource usage such as CPU, memory demand, or network traffic. The scale set is automatically deployed across update domains, like VMs in an availability set. Just like with availability sets, with scale sets only a single update domain is impacted at any given time during scheduled maintenance.
powershell / arm / custom images windows / linux backup / restore monitoring & health
Create and configure a Virtual Machine (VM) for Windows and Linux May include but not limited to: Configure high availability; configure monitoring, networking, storage, and virtual machine size; deploy and configure scale sets Automate deployment of Virtual Machines (VMs) May include but not limited to: Modify Azure Resource Manager (ARM) template; configure location of new VMs; configure VHD template; deploy from template; save a deployment as an ARM template; deploy Windows and Linux VMs
A network interface enables an Azure virtual machine to communicate with internet, Azure, and on-premises resources. A VM can have one or more network interfaces.
The VM size determines the number of NICS that you can create for a VM.
The address for each NIC on each VM must be in a subnet and multiple NICs on a single VM can each be assigned addresses that are in the same subnet.
You can assign IP addresses to Azure resources to communicate with other Azure resources, your on-premises network, and the Internet.
Used for communication with the Internet, including Azure public-facing services.
IP addresses can also be statically assigned or dynamically assigned. Static IP addresses do not change and are best for certain situations such as:
- DNS name resolution, where a change in the IP address would require updating host records.
- IP address-based security models which require apps or services to have a static IP address.
- SSL certificates linked to an IP address.
- Firewall rules that allow or deny traffic using IP address ranges.
- Role-based VMs such as Domain Controllers and DNS servers.
| Public IP addresses | IP address association | Dynamic | Static |
|---|---|---|---|
| Virtual Machine | NIC | Yes | Yes |
| Load Balancer Front-end configuration | Yes | Yes | |
| VPN Gateway | Gateway IP configuration | Yes | No |
| Application Gateway | Front-end configuration | Yes | No |
Create a VM with a static public IP address using the Azure portal
Create a VM with a static public IP address using PowerShell
Create a VM with a static public IP address using the Azure CLI
Deploy an Azure Virtual Machine using C# and a Resource Manager template
Used for communication within an Azure virtual network (VNet), and your on-premises network, when you use a VPN gateway or ExpressRoute circuit to extend your network to Azure.
| Public IP addresses | IP address association | Dynamic | Static |
|---|---|---|---|
| Virtual Machine | NIC | Yes | Yes |
| Load Balancer Front-end configuration | Yes | Yes | |
| Application Gateway | Front-end configuration | Yes | Yes |
Configure private IP addresses for a virtual machine using the Azure portal
Configure private IP addresses for a virtual machine using PowerShell
Configure private IP addresses for a virtual machine using the Azure CLI