This document discusses Azure Virtual Machines, including their networking capabilities. It notes that Azure VMs support a wide range of operating systems and can be deployed from images in the Azure Gallery, built from on-premise or AWS images, or from marketplace images. Availability Sets and fault domains help improve uptime by distributing VMs across hardware. Virtual Networks enable secure communication between Azure resources using components like subnets, IP ranges, and network security groups. Connections can be made to on-premises networks using Point-to-Site VPN, Site-to-Site VPN, ExpressRoute, or VPN-to-VPN.

1. Azure Virtual Machine - Networking

2. Azure N-tier Architecture

3. Virtual Machine and Iaas

4. Why Azure Virtual Machine ?
• Support wide range of OS: Window & Linux
• Deploy from Images:
- From Azure Gallery
- Build your own image from on-Premise, AWS
- From marketplace image
• Availability:
- 99.9% available, 8.86 hour downtime per year (43.8 minutes per
month)
- 99.5% available with Availability Set 4.38 hour downtime per year
• Easy to scale up or scale out (with Scale Set up to 1000 VM
Instances)

5. Virtual Machine – Type

6. Azure Virtual Machine – Image Storage
• Storage architecture Build your own Image

7. Availability Set and SLA
• Fault Domain
• Logical group hardware share common power and network switch
• Create VM in across fault domain to reduce impact of hardware failures, network
issue, power interruptions
• To reduce effect of unplanned issue
• Update domain:
• Logical group hardware can be maintenance or reboot at the same time
• To reduce effect of planned issue such as upgrade azure software, IOS
• Availability Set
• By using fault domain and update domain to improve SLA up to 99.95%
• Create VM within AS, Azure distributes VM across fault domain

8. Availability Set and SLA

9. Azure Virtual Network

10. Virtual Network Overview - Component
• Why ?:
- To enable all Azure Resource to secure communicate to each other
• Virtual Network Component
- Subnet:
• To segment a virtual network
• All resource deploy to Virtual Network must deploy to a subnet
• 5 IP Reserve for each subnet( 4 first 1 last IP)
• Example: FrontEnd Subnet, BackEnd Subnet
- IP range:
• Classless Inter-Domain Routing (CIDR)
• Example: 10.0.0.0/16
• The smallest range is /29 => 8 IP, reserve 5 IP => available 3 IP
- Network Security Group
• To filter network traffic to and from for Subnet or Virtual Network
• Like a firewall

11. Sample Virtual Network

12. Virtual Network – Communicate with On-Premise
• Point 2 Site VPN:
- Connect Single Computer to Azure Virtual Network
- Via Internet with Secure Socket Tunneling Protocol(SSTP)
• Site 2 Site VPN and VPN 2 VPN:
- Connect to 2 VPN together
- Via Internet with IPSec Protocol
• ExpressRoute:
- Private connection
- Via dedicated network (do not over internet)
- More reliability with low latency with Increased reliability and speed

13. Communicate with On-Premise - Sample

14. Demo
• Create Virtual Network
• Add a computer into Virtual Network
• Config Security to Allow Remote Desktop
• Config to allow http access

15. Q&A

16. THANK YOU
www.nashtechglobal.com