Designing Network Infrastructures for Hybrid Cloud Joe Davies

DCIM-B352

The What and the Why: Building blocks

Azure building blocks for hybrid cloudAffinity groupPlacing services near each other in an Azure datacenter

Cloud serviceContainer for virtual machinesSecurity boundary for endpoints and ACLs

Storage accountVirtual machineAvailability setGroup of VMs within a datacenter that are located on different racks

Virtual Network

Azure Virtual NetworkContainer for VMs similar to an internal datacenterAssign a specific private IP address spaceCan have a subnetted structure

Virtual Network

Subnet 1 Subnet 2 Subnet 3

SubnetsWith no subnets-just address spaceSubnets for virtual machinesGateway subnet

Types of Azure Virtual NetworksCloud-onlyInternet facing-onlyPoint-to-site VPN connections

VPNconnection

On-premises network

Virtual Network

Subnet

Virtual Network

Subnet

ExpressRoute

Cross-premisesConnected to on-premises network

Can also be Internet-facingPoint-to-site VPN connectionsSite-to-site VPN connectionExpressRoute

Azure Infrastructure Services hierarchyVMs are hosted in a cloud service

Virtual Network

Subnet

Affinity Group

Subnets are part of a virtual network

VMs can be a member of an availability setVMs can be located on subnets

A virtual network is part of an affinity group

Azure networking building blocksAddress spacesAddressingConfigurationRoutingName resolutionTraffic flows

Address spacesShared Address Space for cloud providers100.64.0.0/10 defined in RFC 6598Used for virtual machines that are not in a virtual network

Virtual network address spaceYou define based on the private network address space

Subnet address spaceYou define based on the virtual network address space

Local Network address spaceSummary of the entire address space or the reachable locations on your on-premises network (but not including the virtual network address space)

Organization address space

Addressing on virtual machinesVirtual IP (VIP)Public IP address assigned to the cloud service container

Direct IP (DIP)Shared Address Space or private IP address assigned to the virtual machineYou can assign a static DIP for special-purpose virtual machines (DNS servers)

Mapping VIPs to DIPsEndpoints for unsolicited inbound Internet traffic

168.63.89.122

10.0.99.4 10.0.99.5

Virtual machine IP configurationDHCP for DIPsLong-lived leases

Virtual Network

Subnet

DHCP

DHCP optionsAddress with a subnet mask (Subnet Mask option)Default gateway (Router option)DNS server IP addresses (DNS Servers option)

LimitationsYou cannot configure the “DHCP server” on the subnet to specify the address range, DNS domain name, NetBIOS settings, Router Discovery, static routes

You cannot override existing options or specify additional ones

DHCP configuration for virtual machinesIn a cloud serviceAddress from the Shared Address Space (100.64.0.0/10) (example: 100.80.74.62)Subnet mask assigned by Azure (example: 255.255.254.0)Default gateway assigned by Azure (example: 100.80.74.1)DNS server IP assigned by Azure (example 100.80.74.70)

In a virtual networkAddress from the subnet address space (private address)Subnet mask from the subnet address spaceDefault gateway of the first address in the subnet address space (Azure VPN gateway)Azure DNS servers or those assigned to the virtual network

Assigning a reserved or static DIPFor VMs in the virtual network that should not change IP addressesA stop/deallocate could assign a different IP addressDNS server VMs that are used by VMs within the virtual network

Windows PowerShell configurationSpecify a static DIP when creating the VM (Set-AzureStaticIP)Specify a static DIP for an existing VM (Set-AzureStaticIP)Remove a static DIP for an existing VM (Remove-AzureStaticIP)

For the details, search on “Configure static DIP”

Routing for virtual networks

10.0.99.4

Virtual network address space: 10.0.99.0/24

Virtual Network

Subnet address space: 10.0.99.0/27

10.0.99.1

On-premises network

Routing for virtual networksRoutes within the Azure virtual network to send or forward trafficRoutes on the host

10.0.99.4

10.0.99.0/27

0.0.0.0/0 to 10.0.99.1

Virtual Network

Local subnet route (10.0.99.0/27)Default route to the Azure VPN gateway (0.0.0.0/0)

On-premises network

Routing for virtual networksRoutes within the Azure virtual network to send or forward trafficRoutes on the Azure VPN gateway

10.0.99.0/27

0.0.0.0/0Local Network routes

Virtual Network

Local subnet route (10.0.99.0/27)Default route to the Azure load balancer (0.0.0.0/0)Local Network routes to the on-premises network

On-premises network

Routing for virtual networksRoutes within your on-premises network

10.0.99.0/24

Virtual Network

Routes to on-premises network locations (summarized or specific)

Route on your VPN device to the virtual network

10.0.99.0/24

Route for the virtual network address space (10.0.99.0/24) that points to your VPN device

On-premises network

Name resolutionAzure assigns DNS servers you specify to virtual machinesName resolution for on-premises and Internet connectivityName registration

Unassigned DNS serversAzure DNS servers provide local name registration and local and Internet name resolution

Cross-premises virtual networkUse your own DNS server, either on the on-premises network or the virtual network

Provides on-premises network name registration and name resolutionInternet name “resolution” handled via Web Proxy Autodiscovery Protocol (WPAD)

Network traffic flowsTo and from the InternetDirect via the Azure Load BalancerIndirect via the on-premises network proxy server

To and from the on-premises networkAcross the VPN or ExpressRoute connection

To and from other virtual machinesIn the same cloud service or virtual networkBetween cloud services not in the same virtual network

Internet traffic flowsInitiated by an Internet hostUnsolicited inbound traffic to virtual machine (endpoints and ACLs)Response traffic from virtual machine

168.63.89.122, TCP 8010.0.99.4, TCP 80

Internet traffic flowsInitiated by an Azure virtual machineDirect to and from the Internet

168.63.89.12210.0.99.4

Internet traffic flowsInitiated by an Azure virtual machineDirect to and from the InternetIndirect to and from the Internet via an on-premises proxy server

Virtual Network

10.0.99.4

On-premises network traffic flowsInitiated by an Azure virtual machine

Virtual Network

10.0.99.4

DNS

Name resolution via DNSTraffic to VPN gateway across VPN or ExpressRoute connection

On-premises network traffic flowsInitiated by an on-premises computer

Virtual Network

10.0.99.4

DNS

Name resolution via DNSTraffic to on-premises router across VPN or ExpressRoute connection

Inter-VM traffic flowsVirtual machines in the same virtual network

Virtual Network

Subnet Subnet Subnet

Direct

Inter-VM traffic flowsVirtual machines in different cloud servicesDifferent virtual networks or outside a virtual network

10.0.99.4

23.99.17.111

10.0.99.4

Over the InternetDirect

Inter-VM traffic flowsVirtual machines in different cloud servicesDifferent virtual networks or outside a virtual networkOver the Internet

10.0.99.4

23.99.17.111

10.0.99.4

Indirect using on-premises network proxy

The How: Planning and design

Primary configuration scenariosInternet-facing with on-premises administrationCross-premises virtual network with endpoints for Internet-accessible resourcesReplaces an extranet

10.0.99.4

Virtual Network

TCP 80

Endpoints allow inbound unsolicited traffic for Internet client accessAdministration occurs over the Internet or across the VPN/ExpressRoute connection

Primary configuration scenariosOn-premises-onlyCross-premises virtual networkExtension of private datacenter or a new datacenter

10.0.99.4

Virtual Network

No endpoints for Internet client access (intranet access only)You can remove the default endpoints for remote administration

Number of virtual networksEach virtual network is an island of compute resourcesA separate datacenter or group of servers with a defined purposeDisaster recovery, spin up as-needed resources, seasonal workloads, regional workloadsAzure virtual networks now support multiple connections

Decision: One or multiple virtual networks?What set of VMs within each one?Common set of Local Networks and DNS servers for all virtual networks of a subscription

Name resolution within the virtual networkAzure assigns a set of DNS servers you specify to VMs via DHCPManual configuration is reset when the VM is stopped/deallocatedAzure DNS servers (Internet) or private DNS servers (recommended)

Azure limitationsNo support for broadcast or multicast traffic (NetBIOS or LLMNR)Only unicast DNS name resolution of FQDNs

Decision: Where are the private DNS servers?In the on-premises networkIn the virtual network

DNS servers on the on-premises networkPros and consPro: No DNS replication or forwarders to configure and manage (VMs and on-premises resources are using the same set of DNS servers)Con: Outbound traffic adds to ongoing costs

Virtual Network

10.0.99.4

DNS

DNS trafficAll name registration and resolution traffic is sent across the VPN connectionIncluding virtual network name resolution for other VMs in the same virtual network

DNS servers in the virtual networkPros and consPro: Name registration and resolution is local to Azure VMs in the virtual networkCon: Need to configure zone replication and DNS forwarders

Virtual Network

10.0.99.4

DNS

DNS

DNS trafficName registration and local name resolution within the virtual networkAll non-local name resolution (forwarding) and DNS zone replication traffic sent across the VPN connection

IP address managementAzure assigns an IP address/subnet mask to VMs via DHCPManual configuration is reset when the VM is stopped/deallocatedUses a portion of your private address space

Azure limitationsDoes not support route summarization for defining the Local Network address space

Decision: What private address space for the virtual network?Large enough to accommodate the planned subnets and their virtual machinesSpecify the Local Network address space for the “hole” created by the virtual network

Non-overlapping address spacesOverlapping addressesYou can have the following overlapping address spaces as separate routes in a routing table:

10.0.0.0/8 (summarize the entire space)10.0.100.0/24 (subnet-specific route)

Closest matching route finds the right one

Azure does not allow overlapping address spacesYou cannot have the following overlapping address spaces

10.0.0.0/8 for the Local Network10.0.100.0/24 for the virtual network

You must explicitly define the Local Network address space so that it does not include the address space of your virtual network

Define the Local Network address spaceCan include private and public address spacesPrivate: 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16Public: IANA-allocated space that corresponds to on-premises network locations

Option 1: The list of prefixes for the address space currently in useYou must update the list of prefixes when you deploy new address space on your on-premises network

Option 2: Your entire on-premises address spaceOnly need to update the Local Network address space when you add new address space (a new public address space)

Decision: What is your Local Network address space?

Working around the address space “hole”Initial Local Network address spaceList the other address spaces from which the virtual network address space is not derived

Define the set of prefixes around the “hole”Depends on address space on which the virtual network is derived (the root space)Enumerate the non-overlapping prefixes for the previous octets, skipping the prefixes containing the virtual network address space (if needed)Based on the prefix length of the virtual network address space, enumerate the non-overlapping prefixes, skipping the virtual network address space

Local Network address space exampleOn-premises network address spacesPrivate address space: 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16A single public address space: 131.107.0.0/16

Virtual network address space of 10.0.100.0/24The virtual network root space is 10.0.0.0/8

Step 1: Define the address space that does not include the virtual network root space172.16.0.0/12, 192.168.0.0/16, and 131.107.0.0/16

Local Network address space exampleStep 2: Define the non-overlapping prefixes for the previous octets, skipping the prefix that contains the virtual network address space (10.0.100.0/24)

Prefixes in the previous octet

10.1.0.0/16

10.2.0.0/16

…

10.254.0.0/16

10.255.0.0/16

Total of 255 prefixes

Skipping 10.0.0.0/16

10.0.0.0/8

Local Network address space exampleStep 2: Define the non-overlapping prefixes for the previous octets, skipping the prefix that contains the virtual network address space (10.0.100.0/24)

10.1.0.0/1610.2.0.0/16

10.254.0.0/1610.255.0.0/16

10.0.0.0/16

…

Local Network address space exampleStep 3: Within the octet, enumerate the non-overlapping prefixes, skipping the virtual network address space (10.0.100.0/24)

Prefixes within the octet

10.0.0.0/24

10.0.1.0/24

…

10.0.99.0/24

10.0.101.0/24

…

10.0.255.0/24

Total of 255 prefixes

Skipping 10.0.100.0/24

10.0.0.0/16

Local Network address space exampleStep 3: Within the octet, enumerate the non-overlapping prefixes, skipping the virtual network address space (10.0.100.0/24)

10.0.0.0/24

10.0.1.0/24

… …

10.0.99.0/24

10.0.101.0/24 10.0.255.0/24

10.0.100.0/24

Local Network address space exampleStep 4: Compile the list of prefixes172.16.0.0/12, 192.168.0.0/16, 131.107.0.0/16 (3 prefixes that are not the root space)

10.1.0.0/1610.2.0.0/16

10.254.0.0/1610.255.0.0/16

…

… …

10.1.0.0/16, 10.2.0.0/16…10.254.0.0/16, 10.255.0.0/16 (255 prefixes, previous octet)10.0.0.0/24, 10.0.1.0/24…10.0.99.0/24, 10.0.101.0/24…10.0.255.0/24 (255 prefixes, within the octet)

Local Network address space exampleStep 4: Compile the list of prefixes172.16.0.0/12, 192.168.0.0/16, 131.107.0.0/16 (3 prefixes that are not the root space)10.1.0.0/16, 10.2.0.0/16…10.254.0.0/16, 10.255.0.0/16 (255 prefixes, previous octet)10.0.0.0/24, 10.0.1.0/24…10.0.99.0/24, 10.0.101.0/24…10.0.255.0/24 (255 prefixes, within the octet)

Use this list to define your Local Network in the Azure Management PortalStep 1: Create the initial set of prefixes that are not the virtual network root space (3 prefixes that are not the root space)Step 2: Use the export/import feature to add the remaining ones in the root space through the Network Configuration file (XML) (510 prefixes for the root space)

Virtual network and its subnetsOne subnet for each logical division of the virtual network address spaceUse similar reasons for creating subnets as you do in your existing datacenters (security, defining host ACLs based on IP address prefixes, etc.)Azure endpoints are not defined per subnetYou can create subnets to define traffic flow based on Azure ACLs

Gateway subnetFacilitates routing over the VPN connection by the Azure VPN gateway

Fault-tolerant routing

Virtual network and its subnetsAzure behaviors/limitationsAzure by default configures subnet address space based on a 3-bit subnetting of the virtual network address space (up to 8 subnets)You cannot define the range of IP addresses for a subnet in terms of a start/stop address (unlike DHCP)Azure uses the first 3 addresses

Number of possible addresses on an Azure subnet is 2n – 5, where n is the number of host bits5 is the normal 2 (the all 1s and all 0s) with an additional 3 (reserved by Azure)

Decision: What is the set of subnets?

ScalabilityScale-out vs. scale-upScale-out is using a higher number of smaller-capacity VMsScale-up is using a lower number of higher-capacity VMsScale-out is better option to add servers for peak loadsSave costs by not having high-capacity machines sitting idle

Scalability within your virtual networkEnough address space and subnets to accommodate growth and peak demands

Decision: How to build scale-out capacity into your virtual network and subnet address spaces?Estimate the number of VMs you might need at a maximum for each subnetIf you do not provide enough capacity, you are forced to do scale-up (fewer machines), rather than scale-out to handle peak loads

Address space recapDecision: What is your virtual network address space?Decision: How many subnets and what is the address space for each?Virtual machine subnetsGateway subnet

Decision: How will you define the Local Network address space?Non-root spacesSet of prefixes in the root space around the virtual network address space “hole”

Decision: Use reserved IP addresses for static DIPs?

Routing From virtual network to on-premises networkLocal Network address prefixes

From on-premises network to virtual networkRoutes for the virtual network address space forward traffic to your VPN device/ExpressRoute routerConfigure your VPN device for the VPN connection

Decision: How to advertise the virtual network address space within your on-premises network?Decision: Which VPN device (static vs. dynamic)?Templates available, search on “About VPN Devices for Virtual Network”

Computer management infrastructureVirtual machines in the virtual networkDirectly name-resolvable and reachable via their private IP addressMembers of the appropriate AD DS domain

Add them to your computer management infrastructure just like your on-premises computersSimilar to branch office computers

Decision: How to add your Azure computers to your computer management infrastructure?

Load balancing in a virtual networkFrom the Internet to the VMsEndpoints and Azure load balancing using a load-balanced set (random distribution)

168.63.89.122, TCP 80

WEB1

WEB2

Load balancing in a virtual networkFrom your on-premises network to the VMsSeparate load balancer on your on-premises network or the virtual network

Virtual Network

WEB1

WEB2

Load balancing in a virtual networkFrom your on-premises network to the VMsAzure internal load balancing

Virtual Network

WEB1

WEB2

Load balancing in a virtual networkBetween VMs in the virtual networkAzure internal load balancing

Virtual Network

BE2

BE1

FE1

Load balancing in a virtual networkDecision: What load balancing do you need?Between application tiersBetween clients and servers

Virtual Network

BE2

BE1

FE1

Step-by-step planning processStep 1: Determine the number of virtual networks and their purpose

Step-by-step planning processStep 1: Determine the number of virtual networks and their purposeStep 2: Determine the name registration and resolution behavior for the VMs in the virtual network

Step-by-step planning processStep 1: Determine the number of virtual networks and their purposeStep 2: Determine the name registration and resolution behavior for the VMs in the virtual networkStep 3: Determine the address space for the virtual network and its subnets

Step-by-step planning processStep 1: Determine the number of virtual networks and their purposeStep 2: Determine the name registration and resolution behavior for the VMs in the virtual networkStep 3: Determine the address space for the virtual network and its subnetsStep 4: Determine the IP routing to the virtual network address space

Step-by-step planning processStep 1: Determine the number of virtual networks and their purposeStep 2: Determine the name registration and resolution behavior for the VMs in the virtual networkStep 3: Determine the address space for the virtual network and its subnetsStep 4: Determine the IP routing to the virtual network address spaceStep 5: Determine your load balancing requirements

Recap: What do I need to know?Names and settingsA name to assign to the Azure Virtual NetworkA name to assign to your Local NetworkThe name of a previously-configured or new Azure affinity groupThe public IPv4 address of your VPN device's interface on the Internet (not needed for ExpressRoute)The set of DNS servers to assign to VMs in the virtual network

NameIP address

Recap: What do I need to know?Addresses and address spacesVirtual network

The address space for the virtual network (a single address prefix)Local Network

The non-overlapping private and public IP address space assigned to your on-premises networkMultiple address prefixes that summarize your organization network but do not include your virtual network address space

For each subnetThe name of the subnetThe address space of the subnet, based on the overall address space for the virtual network (a single address prefix)

The set of addresses to be reserved for static DIPs (DNS servers)Typically fourth, fifth, sixth, etc. possible IP addresses for the subnet address space

Completing your configurationSite-to-site VPN connectionAzure configuration

Create a gateway (static or dynamic) for your virtual networkVPN device configuration

Public IPv4 address of the Azure VPN gateway for your virtual network (not needed for ExpressRoute)Internet Protocol security (IPsec) pre-shared key for the site-to-site connection

Azure Management Portal: Networks > name of your virtual network > Dashboard

To host VMsOne or more cloud services to contain the virtual machinesA storage account for the VHDs and extra disks

You are now ready to start creating or migrating VMs

Putting it into practice

SharePoint 3-tier farm with domain controllersSetting up a new SharePoint 2013 farmAvailable only to on-premises usersMinimal configuration for fault toleranceTwo servers for each server role

Step-by-step planning processStep 1: Determine the number of virtual networks and their purpose

VPNconnection

Virtual Network

A single, cross-premises virtual network to host the VMs of an on-premises-only SharePoint 2013 farmThree-tier design: web servers, app servers, database servers

Step-by-step planning processStep 2: Determine the name registration and resolution behavior for the VMs in the virtual network

VPNconnection

Virtual Network

Two domain controllers in the virtual network providing local SharePoint authenticationThese domain controllers also provide local DNS name registration and resolution

Step-by-step planning processStep 2: Determine the name registration and resolution behavior for the VMs in the virtual network

VPNconnection

Virtual Network

DNS

Virtual network DNS servers use on-premises network DNS servers as forwarders (VMs get org-wide name resolution)Virtual network DNS servers perform DNS domain replication with on-premises network DNS servers (on-premises network computers can resolve VM DNS names)

Step-by-step planning processStep 3: Determine the address space for the virtual network and its subnets

VPNconnection

Virtual Network

Subnet

Use 192.168.100.0/24 for the virtual networkUse /27s for subnets within the virtual network, need a single subnet 192.168.100.0/27

Step-by-step planning processStep 4: Determine the IP routing to the virtual network address space

VPNconnection

Virtual Network

Subnet

192.168.100.0/24

Add the 192.168.100.0/24 route to the VPN device and advertise it within the routing infrastructure of the on-premises network

Step-by-step planning processStep 5: Determine your load balancing requirementsNot Internet-facing: No endpoints or ACLs for SharePoint traffic

VPNconnection

Virtual Network

Subnet

Use Azure internal load balancing to spread the load across the two web servers

Virtual network configurationNames and settingsA name to assign to the Azure Virtual Network: SPFarmNetA name to assign to your Local Network: CorpnetThe name of a previously-configured or new Azure affinity group: USAGroupThe public IPv4 address of your VPN device's interface on the Internet: 131.107.89.32The set of on-premises network DNS servers to assign to the first VMs in the virtual network

CorpDNS1, 10.9.47.56CorpDNS2, 172.31.17.211

Virtual network configurationAddress spacesVirtual network: 192.168.100.0/24Local Network:

10.0.0.0/8, 172.16.0.0/12192.168.0.0/24, 192.168.1.0/24…192.168.99.0/24, 192.168.101.0/24…192.168.255.0/24A total of 257 prefixes

Skipping 192.168.100.0/2

4

One subnet for nowName: SPFarmSubnetAddress prefix: 192.168.100.0/27First 2 VMs will be domain controllers/DNS servers: 192.168.100.4, 192.168.100.5

The set of addresses to be reserved for static DIPs (DNS servers)192.168.100.4 and 192.168.100.5

The set of eventual DNS servers for the VMs in the virtual networkVNetDNS1, 192.168.100.4VNetDNS2, 192.168.100.5

SharePoint 3-tier farm with domain controllers

VPNconnection

SPFarmNet

SPFa

rmSubnet

192.168.100.0/24

192.168.100.0/27131.107.89.32

DNS

Static DIP: 192.168.100.4

Static DIP:192.168.100.5

10.9.47.56

172.31.17.211

Create and configure SPFarmNet1. Create the virtual networkUse Custom Create in the Azure Management PortalUse 10.9.47.56 and 172.31.17.211 DNS servers (on-premises) Add the 10.0.0.0/8 and 172.16.0.0/12 prefixes to the Local Network named Corpnet

2. Add the remaining prefixes for the Local Network address spaceExport the network configuration file for the SPFarmNet virtual networkAdd the remaining prefixes (192.168.0.0/24…192.168.99.0/24, 192.168.101.0/24…192.168.255.0/24)Import the network configuration file

Demo

Demo: Creating a cross-premises virtual network to host a SharePoint 2013 farm

Routing, VPN connection, then first VM3. Set up your routing infrastructure to forward packets to the virtual networkAdd the virtual network address space route to your VPN device, advertise it (OSPF, RIP)

4. Set up the VPN connection with your on-premises VPN deviceCreate a gateway for your virtual networkConfigure IPsec settings for a site-to-site VPN connection

5. Create the first VM, add a data diskTest connectivity to the on-premises network (ping an on-premises IP address)Use NSLookup to test DNS name resolution on the VM

Completing the DNS configuration6. Create the second VM, add a data disk7. Configure the first and second VMs with static DIPsFirst VM: 192.168.100.4, second VM: 192.168.100.5

8. Join the first and second VMs to the domain and make them domain controllers9. Reconfigure the SPFarmNet virtual network to use 192.168.100.4 and 192.168.100.5 for DNS serversStop, then restart the first two VMs

10. Configure the two VMs to perform DNS zone replication

Completing the farm configuration11. Create the additional VMsThe four SharePoint VMs use the SharePoint Server 2013 (Trial) imageThe two SQL Server VMs use the SQL Server 2014 image

12. Create the SharePoint farm13. Create an internal load balancing set for the two front-end web servers (creates a new VIP)14. Create DNS entries to send farm traffic to the internal load balancer VIP

Breakout SessionsDCIM-B210: How to Develop a Successful Hybrid Cloud Strategy

DCIM-B388: Extending Your Premises to Microsoft Azure with Virtual Networks and ExpressRoute, Thursday, May 15 8:30 AM - 9:45 AM Room: 370A

Related content

Hands-On LabsIntroduction to Azure Virtual Machines

Introduction to Cloud Services

Find Me Later At. . . CSI booth

Solutions Advisory Board (SAB)Let’s talk solutions

Microsoft provides lab-tested, cross-product, end-to-end solutionsSAB members hear about Microsoft’s solution ideas and influence future solutions by providing feedback

SAB Session• Presenters from Microsoft Azure,

Office, Cloud and Datacenter, and Microsoft Consulting Services will talk about their latest work

SAB Table @ Ask the ExpertsTues 6:30 – 8:30pm

Ask the Experts• Meet the SAB team and ask us

questions • Experts from Microsoft Azure, Office,

and Cloud and Datacenter teams will be there

Hilton Americas, Room 335AWed 4:00 – 5:30pm

Come Visit Us in the Microsoft Solutions Experience!

Look for Datacenter and Infrastructure ManagementTechExpo Level 1 Hall CD

For More InformationWindows Server 2012 R2http://technet.microsoft.com/en-US/evalcenter/dn205286

Windows Server

Microsoft Azure

Microsoft Azurehttp://azure.microsoft.com/en-us/

System Center

System Center 2012 R2http://technet.microsoft.com/en-US/evalcenter/dn205295

Azure PackAzure Packhttp://www.microsoft.com/en-us/server-cloud/products/windows-azure-pack

Resources

Learning

Microsoft Certification & Training Resources

www.microsoft.com/learning

msdn

Resources for Developers

http://microsoft.com/msdn

TechNet

Resources for IT Professionals

http://microsoft.com/technet

Sessions on Demand

http://channel9.msdn.com/Events/TechEd

Complete an evaluation and enter to win!

Evaluate this session

Scan this QR code to evaluate this session.

© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.