3. Virtual Network Overview
• Virtual Networks allow you to extend your network
into Microsoft Azure
• You can use virtual networks to achieve the
following:
• Create a VPN in Azure
• Configure cross-premises connectivity over site-to-site
IPSec VPNs
• Configure custom DNS server for all services in a virtual
network
• Some of the key benefits of Virtual Networks:
• Extend trust and security boundary
• Persistent private IP addresses
• Enhanced security and isolation
4. Azure Name Resolution
Scenario Name Resolution
Cross-premises between Microsoft
Azure role instance or virtual
machine and on-premises servers
DNS provided outside of Microsoft
Azure
Cross-premises between on-premises
servers and role instance
or virtual machine in Microsoft Azure
DNS provided outside of Microsoft
Azure
Name resolution between role
instances in the same cloud service
Azure name resolution
Name resolution between virtual
machines located in same cloud
service
Azure name resolution
Between virtual machines and role
instances located in the same virtual
network but different cloud services
DNS provided outside of Microsoft
Azure
5. Configure a Virtual Network
• Can be created from the Management Portal or
using a network configuration file
• The following options are available:
• Name
• Affinity Group
• Network Preview
• DNS Servers
• Point-To-Site Connectivity
• Site-to-Site Connectivity
• Address Space
7. VPN Devices for Virtual Networks
• Used to create a connection between your on-premises
network and your virtual network
• Requires a Public IPv4 Address
• Can be created as static or dynamic
• Configuration template available from the
Management Portal
8. Affinity Groups and Monitoring for Virtual Networks
• Allows you to group services together for optimal
performance
• Runs the service at the same Azure data center
• Assigned at the subscription level
• Name has to be unique within the subscription
• Can be created when creating a virtual network
9. Network Configuration Files
• Can be used to create a virtual network
• Can create multiple virtual networks with more
than one subscription
• Can be used to make changes to network
configuration settings
• Can be exported from the Management Portal
• Below is some settings that can be changed:
• IP Addresses of DNS Servers
• IP Address space and IP subnet definitions
• VPN Gateway IP address
• Affinity group
11. Edit Virtual Network Properties and DNS Servers
• Dashboard view allows you to view virtual network
statistics
• Can be edited from the Configure page
• You can change the following settings:
• DNS Servers
• Point-to-Site connectivity
• Site-to-Site Connectivity
• Address Spaces
• Local Connectivity
12. Traffic Manager Overview
• Control distribution of user traffic to a cloud service
• Determine where to send traffic based on these
factors:
• Performance
• Price
• Compliance
• Legal Reasons
• Can direct users to the closest cloud service
• Allows for maintenance on a service without
downtime
13. Traffic Manager Configuration Tasks
• You can use these steps to implement traffic
manager:
• Deploy your cloud services to your production environment
• Determine the load balancing method required for your
cloud service
• Decide the monitoring configuration
• Decide on a name for the traffic manager domain
• Create your profile and configure settings
• Test the traffic manager profile
• Point your DNS to the profile
14. Traffic Manager Load Balancing Methods
• There are three load balancing methods for traffic
manager:
• Failover
• Round Robin
• Performance
• Each profile can only have one load balancing
method at a time
15. Traffic Manager Monitoring
• Used to ensure offline service are not sent traffic
• Must be configured for all cloud services
• Status can be viewed in the Management Portal