1. #SPSSAN June 30, 2012 San Diego Convention Center ENTERPRISE COLLABORATION AND THE CLOUD How to integrate cloud-based SharePoint into enterprise collaboration strategies

2. #SPSSAN INTRODUCTION Section 1 | Slide 2 |

3. #SPSSAN Speaker Introduction Saguenay ( Sag ) Baruss Based in Calgary, Alberta TSP Manager with AvePoint Canada** Introduction | Slide 3 | This presentation was developed independently of AvePoint. For additional information on AvePoint products and services please visit www.avepoint.com. **

4. #SPSSAN Session Overview This is a 200-level session intended for the architects and technical leads responsible for the design and implementation of SharePoint and the corporate cloud strategy. Introduction | Slide 4 |

5. #SPSSAN Session Objectives To discuss the key differences between on- premises and off-premises SharePoint, the limitations of each, and the key factors to consider when developing an enterprise cloud strategy for collaboration. Introduction | Slide 5 |

6. #SPSSAN Agenda Introduction5 min The Cloud and SharePoint10 min Developing a Collaboration Strategy25 min SharePoint Cloud Scenarios15 min Closing Thoughts5 min Introduction | Slide 6 |

7. #SPSSAN THE CLOUD AND SHAREPOINT Section 2 | Slide 7 |

8. #SPSSAN What Is Meant By ‘Cloud’? Informal definition: ‘Cloud’ lets us use a service without worrying about how it’s delivered. The Cloud and SharePoint | Slide 8 |

9. #SPSSAN A Typical SharePoint Adoption The Cloud and SharePoint | Slide 9 | Multi-farm environment Single-server farm Two-tier farm with dedicated database server Three-tier farm with dedicated application server Three-tier farm with hardware dedicated databases

10. #SPSSAN Adding ‘Cloud’ to the Mix Considering cloud in addition to the traditional adoption trajectory provides a completely different set of options for enterprise collaboration. The Cloud and SharePoint | Slide 10 |

11. #SPSSAN Staying Focused The key to SharePoint success is the services provided, not the implementation. The Cloud and SharePoint | Slide 11 |

12. #SPSSAN DEVELOPING A COLLABORATION STRATEGY Section 3 | Slide 12 |

13. #SPSSAN Prerequisites SharePoint vision and direction: What SharePoint will be used for. How SharePoint fits into the overall services landscape. Business commitment: The resources and support to take on this project. Leadership: Technical Strategic Operational Developing a Collaboration Strategy | Slide 13 |

14. #SPSSAN Approaching the Problem Most organizations will tend to approach cloud- based collaboration the same way they approach the delivery of other line-of-business services. Developing a Collaboration Strategy | Slide 14 |

15. #SPSSAN Available Options Private cloud: Self-owned. Office 365: Self-administered. Amazon / Azure-hosted SharePoint: Self-managed. Third-party hosted SharePoint: Partially managed, partially administered. Developing a Collaboration Strategy | Slide 15 |

16. #SPSSAN Indicators The best indicators of an organization’s cloud strategy are: (a) The complexity of SharePoint, in particular the level of customization, and (b) The maturity of SharePoint within the organization. Developing a Collaboration Strategy | Slide 16 |

17. #SPSSAN Evaluating the Options In all cases, a corporate collaboration strategy should be developed through a systematic analysis of alternatives against a set of criteria. Some of the key criteria to consider are: Developing a Collaboration Strategy | Slide 17 |

18. #SPSSAN C1 - Business Requirements Business requirements should be used to determine feasibility. Not all business requirements can be met through cloud-based SharePoint. Developing a Collaboration Strategy | Slide 18 |

19. #SPSSAN C2 - Required Service Levels Service levels ( in particular RPO, RTO, and recovery catalog ) should be used to determine both the design of SharePoint and what is required in the event of a failure. Developing a Collaboration Strategy | Slide 19 |

20. #SPSSAN C3 - Available Resources Many organizations don’t have the skills and / or capacity required to manage an enterprise SharePoint implementation. Developing a Collaboration Strategy | Slide 20 |

21. #SPSSAN C4 - Integration with Other Systems Integrated systems are often not cloud-based. If the method of integration is a customization, it may not be supported in a cloud-based implementation of SharePoint. Changes to integration points need to be tested in a non-production environment. Developing a Collaboration Strategy | Slide 21 |

22. #SPSSAN C5 - Business Continuity In this context, ‘business continuity’ refers to both high availability and disaster recovery. Developing a Collaboration Strategy | Slide 22 |

23. #SPSSAN C6 - Data Ownership and Security Storing data in the cloud delegates access and responsibility to someone else. Developing a Collaboration Strategy | Slide 23 |

24. #SPSSAN C7 - Governance Strategy Both on-premises and cloud based SharePoint solutions require governance. Governance pertaining to storage and retention may be reduced by selecting a cloud solution which includes storage management. Governance can be more difficult to automate in the cloud. Developing a Collaboration Strategy | Slide 24 |

25. #SPSSAN C8 - Cost Cost should be assessed in terms of up-front cost, operational ( run ) costs, and future costs anticipating growth. Watch out for large quantities of data and / or large numbers of users. Developing a Collaboration Strategy | Slide 25 |

26. #SPSSAN SHAREPOINT CLOUD SCENARIOS Section 4 | Slide 26 |

27. #SPSSAN S1 - Private Cloud SharePoint Cloud Scenarios | Slide 27 | Data Centre Office Users Remote User

28. #SPSSAN S2 - Office 365 SharePoint Cloud Scenarios | Slide 28 | Office Users Remote User

29. #SPSSAN S3 - Amazon / Azure Hosted SharePoint Cloud Scenarios | Slide 29 | Office Users Remote User

30. #SPSSAN S4 - Third-party Hosted SharePoint Cloud Scenarios | Slide 30 | Office Users Remote User

31. #SPSSAN S5 - On-premises + Office 365 Hybrid SharePoint Cloud Scenarios | Slide 31 | Data Centre Remote User Office Users

32. #SPSSAN S6 - On-premises + Amazon / Azure Hybrid SharePoint Cloud Scenarios | Slide 32 | Data Centre Remote User Office Users

33. #SPSSAN S7 - On-premises + Third-party Hosted Hybrid SharePoint Cloud Scenarios | Slide 33 | Data Centre Remote User Office Users

34. #SPSSAN S8 - Off-premises Hybrid SharePoint Cloud Scenarios | Slide 34 | Remote User Office Users

35. #SPSSAN CLOSING THOUGHTS Section 5 | Slide 35 |

36. #SPSSAN Common Pitfalls Unclear business requirements. Unclear SharePoint vision. Undocumented service levels. Underestimating governance. Committing too soon. Complacency. Closing Thoughts | Slide 36 |

37. #SPSSAN Keys to Success Understanding where SharePoint fits within the global service landscape. Understanding key integration points with other systems. Finding a balance between building for today and planning for the future. Data classification. Effective governance. Closing Thoughts | Slide 37 |

38. #SPSSAN Recommended Next Steps Continue to educate yourself on the available cloud options for SharePoint. Review and update your documentation for SharePoint and all dependent systems. Firmly establish governance. Engage an enterprise architect. Closing Thoughts | Slide 38 |

39. #SPSSAN Additional Reading http://www.nist.gov/itl/cloud/index.cfm http://csrc.nist.gov/publications/nistpubs/800-145/SP800-145.pdf http://technet.microsoft.com/en-us/cloud/hh147293 Closing Thoughts | Slide 39 | [ Icons from dryicons.com used in this presentation ]

40. #SPSSAN The After-Party : SharePint Karl Strauss Brewing Company 1157 Columbia Street San Diego, CA 92101 Phone: 619-234-2739 Immediately following event closing & prize drawings (@6:30 pm) Directions (.9 miles): 1. Head northeast on 1st Ave 2. Turn left onto W B St 3. Turn left onto Columbia St Karl Strauss will be on the left

41. #SPSSAN June 30, 2012 San Diego Convention Center THANK OUR SPONSORS Please be sure to fill out your session evaluation!

42. #SPSSAN Questions? Closing Thoughts | Slide 42 |