Why? (or … am I really in the right track?)

1. Why?(or … am I really in the right track?) Mark Quirk Azure Product Manager Developer & Platform Group, Microsoft @markqu markqu@microsoft.com

2. PUBLIC SAS 70 & ISO 27001 compliant ▪ 30,000 engineers ▪ $2B+ in cloud infrastructure COMMON Identity ▪ Virtualization ▪ Management ▪ Development PRIVATE MICROSOFT CLOUD

3. Why Cloud…? • More specifically… • Why move from (or combine) regular hosting to Azure? • Why move from (or combine) on-premise to Azure? • Will my users benefit from SaaS?

4. Application, Data PaaS App Services / middleware - cdn, cache, service bus, q’s, traffic routing Platform as a Service Runtimes Security & Integration Database Mgmt System Auto restart Operating System Virtualization Redundancy Load balancing Server HW Live upgrade Storage SLA Load balancing Networking

5. Types of Cloud Services AaaH(On-Premise / Private) IaaS (Infrastructureas a Service) PaaS (Platform asa Service) SaaS (Software asa Service) You manage Applications Applications Applications Applications You manage Data Data Data Data You manage Runtime Runtime Runtime Runtime Middleware Middleware Middleware Middleware Others Manage Others Manage O/S O/S O/S O/S Virtualization Virtualization Virtualization Virtualization Others Manage Servers Servers Servers Servers Storage Storage Storage Storage Networking Networking Networking Networking

6. Usage View “Growing Fast“ “On and Off “ Compute Compute Inactivity Period Average Usage Usage Average Time Time • On and off workloads • Disaster Recovery scenarios • Testing, marketing campaigns, batch jobs • Successful services needs to grow/scale • Keeping up with growth is big IT challenge • Complex lead time for deployment

8. Usage View “Growing Fast“ “On and Off “ Compute Compute Inactivity Period Average Usage Usage Average Time Time • On and off workloads (e.g. batch job) • Disaster Recovery scenarios • Time to market can be cumbersome • Successful services needs to grow/scale • Keeping up with growth is big IT challenge • Complex lead time for deployment “Unpredictable Bursting“ “Predictable Bursting“ Compute Compute Average Usage Average Usage Time Time • Unexpected/unplanned peak in demand • Sudden spike impacts performance • Can’t over provision for extreme cases • Services with micro seasonality trends • Peaks due to periodic increased demand • IT complexity and wasted capacity

9. Or is it also about this? “Departmental“ “I want to try something now!“ Machines Machines Time Time • Need to quickly provision new machines for a departmental solution • Need to quickly provision new machines for a temporary period of time “Extend to the Cloud“ “Just store data(or code) in the Cloud“ • Extend existing applications • With all processing elsewhere “Migrate existing applications“ “New hybrid services“ • Benefits of reduced operational costs • On-premise and Cloud aka S+S

10. Above the Cloud(s)

11. Apps, apps, everywhere

12. Where isn’t Azure applicable? • Very large relational datasets (for now) • Already paid for what we’re using! • You’re data MUST remain in UK • Need Payment Card Industry (PCI) compliance

13. Benefits Super-Summary

14. © 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista 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.