3. VM Role (PaaS)Virtual Machine (IaaS) StorageNon-Persistent StoragePersistent Storage Easily add additional storage DeploymentBuild VHD offsite and upload to storage.Build VHD directly in the cloud or build the VHD offsite and upload NetworkingInternal and Input Endpoints configured through service model. Internal Endpoints are open by default. Access control with firewall on guest OS. Input endpoints controlled through portal, service model or API/Script. Primary UseDeploying applications with long or complex installation requirements into stateless PaaS applications Applications that require persistent storage to easily run in Windows Azure.

4. IT Pro experience Support for key server applications Easy storage manageability High availability features Advanced networking Integration with compute PaaS

5. Windows Server 2008 R2 Windows Server 2008 R2 with SQL Server 2012 Evaluation Windows Server 2008 R2 with BizTalk Server 2010 R2 CTP Windows Server 2012 OpenSUSE 12.1 CentOS 6.2 Ubuntu 12.04 SUSE Linux Enterprise Server SP2

8. INSTANCES ROLES

12. Base OS image for new Virtual Machines Sys-Prepped/Generalized/Read Only Created by uploading or by capture Writable Disks for Virtual Machines Created during VM creation or during upload of existing VHDs. Images and Disks

13. Each Persistent Data Disk Can be up to 1 TB

14. Modify using Set-AzureOSDisk or Set-AzureDataDisk

15. Windows Azure Storage Disk Storage

17. 99.9% for single role instances 8.75 hours of downtime per year What’s included Compute Hardware failure (disk, cpu, memory) Datacenter failures - Network failure, power failure Hardware upgrades, Software maintenance – Host OS Updates What is not included VM Container crashes, Guest OS Updates 99.95% for multiple role instances 4.38 hours of downtime per year

18. SQL Server No SLA SLA 99.95 SQL Server Primary SQL Server Secondary

19. Fault Domains Represent groups of resources anticipated to fail together i.e. Same rack, same server Fabric spreads instances across fault at least 2 fault domains Update Domains Represents groups of resources that will be updated together Host OS updates honour service update domains Specified in service definition Default of 5 (up to 20) Fabric spreads role instances across Update Domains and Fault Domains

23. Bring your own DNS server Use your on-premise DNS servers Deploy a DNS server in Windows Azure Use public DNS services Windows Azure provided DNS Resolves VMs by name within the same cloud service Machine names are modeled explicitly and registered in the DNS service Full control over machine names

24. Port Forwarded Endpoints Direct communication to multiple VMs in the same cloud app Support for All IP-Based Protocols (VM to VM) Instance-to-instance communication TCP, UDP and ICMP, dynamic ports UDP Traffic Supported in WA Load-balanced incoming traffic and allows outbound traffic Custom Load Balancer Health Probes Health check with probe timeouts HTTP based probing, allowing granular control of health checks

25. Endpoint Public Port Local Port Protocol (TCP/UDP) Name Cloud App/Hosted Service

26. Endpoint Set Public Port Local Port Protocol (TCP/UDP) Name Cloud App

27. Load Balancer Probe Set Name Protocol (TCP) Probe Port Probe Path (/healthcheck.aspx) Looks for HTTP 200 Cloud App

28. Cross-premise Connectivity ENTERPRISE Data Synchronization SQL Azure Data Sync Application-layer Connectivity & Messaging Service Bus Secure Machine-to-Machine Network Connectivity Windows Azure Connect Secure Site-to-Site Network Connectivity Windows Azure Virtual Network

29. Your “virtual” branch office/ datacenter in the cloud Enables customers to extend their Enterprise Networks into Azure Networking on-ramp for migrating existing apps and services to Windows Azure Enables “hybrid” apps that span cloud and their premises A protected private virtual network in the cloud Enables customers to setup secure private IPv4 networks fully contained within Windows Azure IP address persistence Inter-service DIP-to-DIP communication

30. Protect virtual machines from the open Internet Note: Windows Azure provided DNS does not span cloud services Direct Access via VNET SQLSubnet (10.1.0.0/16) Load Balancer 80 IIS Virtual Machines Cloud Service1 Cloud Service 2 SQL Mirror ContosoVNet (10.0.0.0/8) FrontEndSubnet (10.0.0.0/16)

31. VNET Provides Direct Network Access FrontEndSubnet (10.3.1.0/24) BackEndSubnet (10.3.3.0/24) IIS Servers Fabrikam-CloudSvc Fabrikam-CloudApps SQL Mirror DNSSubnet (10.3.2.0/24) APPVNET – Virtual Network (10.3.0.0/16) Corp-OnPrem (192.168.1.0/24) 192.168.1.6 (Local AD) Fabrikam-CloudDC AD Data Access Auth

32. PhysicalVirtualSaaS IaaSPaaS

33. Paas is cheaper Reason: There’s less admin and management work to do Benefit: Organizations spend less supporting applications PaaS is faster Reason: There’s less work for developers to do Benefit: Applications can go from idea to availability more quickly PaaS is lower risk Reason: The platform does more, leaving fewer opportunities for error Benefit: Creating and running applications gets more reliable

34. Mixed Mode: VM and PaaS Roles in the Same Cloud Service Simple, secure and highly efficient method of using IaaS and PaaS side-by-side Direct Connectivity Using Virtual Networking For advanced connectivity scenarios such as Active Directory or DCOM Connect Cloud Apps via VIPs Easily compose services by connecting public endpoints

35. Strengths Simplicity Tenant Autonomy VIP Swap (stateless roles) Easy Local Dev/Test Persistent Service is Easily Accessible (even from other services!) SQL Data Access Traffic Through Public Endpoint Weaknesses Higher Latency Less Secure Management/ Deployment Overhead WA Web Role Cloud Service 1 Cloud Service 2 SQL Server Load Balancer Secure Endpoints with Firewall Load Balancer

36. Strengths More Secure Low Latency Cloud Service Autonomy VIP Swap (stateless roles) Advanced Connectivity Requirements Weaknesses VNET Complexity No Windows Azure provided DNS Direct Access via VNET FrontEndSubnet (10.0.0.0/16) SQLSubnet (10.1.0.0/16) Load Balancer WA Web Role Cloud Service1 Cloud Service 2 AD SQL Mirror AD Subnet (10.2.0.0/16) ContosoVNet (10.0.0.0/8)

37. VNET Provides Direct Network Access FrontEndSubnet (10.3.1.0/24) BackEndSubnet (10.3.3.0/24) Fabrikam-CloudSvc Fabrikam-CloudApps SQL Mirror DNSSubnet (10.3.2.0/24) APPVNET – Virtual Network (10.3.0.0/16) Corp-OnPrem (192.168.1.0/24) 192.168.1.6 (Local AD) Fabrikam-CloudDC AD WA Web Roles Auth Data Access

38. Strengths Windows Azure Provided DNS Low latency connectivity Single deployment, update and management unit Weaknesses No VIP Swap (coming in the future WA Web Role Virtual Machine Load Balancer 80 Cloud Service

39. VNET Provides Direct Network Access FrontEndSubnet (10.3.1.0/24) Fabrikam-CloudSvc DNSSubnet (10.3.2.0/24) APPVNET – Virtual Network (10.3.0.0/16) Corp-OnPrem (192.168.1.0/24) 192.168.1.6 (Local AD) Fabrikam-CloudDC AD WA Web Roles Windows Azure SQL Database Data Access Auth

40. IT Pro experience Support for key server applications Easy storage manageability High availability features Advanced networking Integration with compute PaaS