2.  This session details common scenarios for deploying Office 365 services. Office 365 provides a breadth of capability, but often there is a key scenario that is the priority. In this session learn about optimal paths for customers moving from Domino Notes, or customers looking to incorporate Yammer with Office 365. Future topics will include optimal paths for: customers with Multiple Forests or multiple tenant requirements, as well as customers who wish to add additional Office 365 services to existing Office 365 Pro Plus or stand alone service deployments. Understand the implications of these deployment approaches and the steps required to expand the service offerings.

3.  Quick Review of the Optimal paths for Exchange  Optimal Path for Domino Notes  Optimal Path for Yammer  Future Paths

5. Enhance Optimized Path for Exchange 2007

6. Enhance Optimized Path for Exchange 2010

8. Pilot the service quickly User signs into Office 365 with a Cloud ID (jane@contoso.onmicrosoft.com) Pilot the new Exchange mailbox New mailbox in the cloud Inbox content populated via Connected Account User sends/receives email as Jane@contoso.comJane@contoso.com Pilot the new collaboration tools Run online meetings with any user with computer PC-to-PC calling, video conferencing, and app sharing. Collaborate using SharePoint Online team site and newsfeeds Easily store files in the cloud with SkyDrive Pro and share file with external users Office across multiple devices Access the service via a browser - Office Web Apps across devices and platforms (no client required) User self-install of Office 365 ProPlus side-by-side with existing Office client installations Experience Office anywhere Mobile connectivity options are built into the service – just start connecting devices Connect to Office 365 via mobile devices with Exchange Active Sync for mail Platform specific mobile apps bring best experience where it makes sense - i.e. OneNote, Lync Control & manage your pilot Centralized administration from the Office 365 admin center in the service Online management centers for Exchange, SharePoint, and Lync Service health dashboard to monitor service maintenance and incidents Service use reporting available in the service admin center including service activity Setup on day 1 Full use of the service User driven pilot Pilot setup continues to step 2 deploy Limited on-premises requirements Sign-on Mail Collaboration Clients Mobile Administration

9. Network What you need to connect Network access to service from client end points over ports 80 and 443 Network bandwidth capacity Mail Connect to existing mail for the pilot POP3 or IMAP4 protocol support for pilot users to use Connected Accounts Clients Pilot user access Web client – minimum browser Office 365 Pro Plus – clients running Windows 7 + Simple requirements Easy to start or stop

10. Setup in days Adds on-premises integration Pilot user and info is sustained IT driven migration Mail migration that best fits environment Sign-on Shared namespace Sign-on with the same user name as on premises Mail Integrated mail flow Shared SMTP domain and connectors facilitate mail flow between Office 365 and on-premises org Global address list (imported) Additional users’ email content migrated via Connected Accounts Collaboration Sharing and working with others Lync business partner federation Site governance and provisioning support Setup of Apps for Office corporate app catalog Clients IT managed client productivity Office 365 ProPlus deployed to user desktop via IT process Mobile Managed mobile connectivity Send and receive mail from mobile device as on-prem email Administration Control & monitor Data loss prevention configuration (limited) Exchange Online Protection mail protection configuration (limited) 2. Deploy Experience – what’s added

11. Dedicated customer IT team Change management readiness Identity What’s Required Populate online directory Set Identity equal to on-prem user name Network What you need to connect Network access to service from client end points Network bandwidth availability Access to maintain DNS entries for shared domain(s) Clients Required to connect and deploy Web client – minimum browser Office 365 Pro Plus – clients running Windows 7 + Mail Required to setup and migrate Admin access, managed by customer IT team 2. Deploy – what’s required

12. Advanced integration Single sign-on / ADFS 3 rd party identity providers – “Works with program” Advance migration scenarios Notes mail, calendar, and contacts data migrations Advanced integration and solution building Richer coexistence with on-prem Notes org, incl. Free/Busy information sharing via 3rd party tools Lync or SharePoint hybrid SharePoint solutions – including BCS, Duet, etc. Advanced client management capabilities Virtual desktop and virtual application scenarios Connect to the service Blackberry Enterprise Sever integration Leverage advanced service controls Data loss prevention configuration Exchange Online Protection mail protection configuration Adds scenarios Extended durations Customer specific implementation Ability to add to deployed clients at point in the future Sign-on Mail Collaboration Clients Mobile Administration Directory integration Sync Domino Directory to on-prem AD via 3rd party tools Sync on-prem AD to MSOnline Directory Services Management

13. Enhance Optimized Path for Notes Migrations

14. Decision points Identity type Namespace Coexistence Migration approach Authentication requirements

16. Pilot the service quickly Enroll O365 tenant for a free Yammer Basic network with a Cloud ID (jane@contoso.com)jane@contoso.com Pilot the Yammer collaboration tools Replace the SharePoint Online Newsfeed in the Office 365 header with Yammer OR Incorporate Yammer web parts into Team and My Sites in SharePoint Online Yammer across multiple devices Web browser, Yammer desktop app Experience Yammer anywhere Mobile clients for Windows Phone, Android, Blackberry, iPad, iPhone Self -service Users navigate to sign-up URL and enter an email address to join Enroll on day 1 User-driven pilot Create internal and external networks Limited on-premises requirements Sign-on Collaboration Clients Mobile Administration

17. Network What you need to connect Network access to service from client end points over ports 80 and 443 Firewall/Proxy/Filtering/E-mail Whitelists Browser Clients Requirements Windows Phone 7 and higher Android v2.2 and higher iOS v5.0 and higher Windows XP and higher Mac OS 10.5 and higher Adobe Air (desktop only) Simple requirements Single Namespace Browser requirements Internet Explorer 8 or later Firefox (latest version) Chrome (latest version) Safari (latest version) Java-script enabled Flash 9 or higher

18. Setup in days Yammer Enterprise Customer Success Manager Administrative Control Pilot users and info are sustained Provisioning tools for creating users Administration Control & monitor Yammer Enterprise enrollment Yammer Enterprise Admin Tools Network Level Apps & Integrations Support & Services Content Sharing (P1 & E1) Team Sites, notebooks and mailboxes (P1 & E1) Search (P1 & E1) SharePoint Store (P1 & E1) Content Management (P1 & E1) Office Web Apps (E2) Hosted E-mail (E2) Simple File Sharing (E2) 2. Deploy Experience – what’s added

19. Dedicated customer IT team Change management readiness Identity What’s Required Must designate a Verified Admin when working with Yammer Customer Support Manager to upgrade to Enterprise Create users in bulk using a CSV Create users in bulk by implementing Yammer Dsync for directory synchronization Network What you need to connect Network access to service from client end points Clients Required to connect and deploy Network access to service from client end points 2. Deploy – what’s required

20. Custom integration Single Sign-On SharePoint 2010 integration Yammer Embed Yammer for Salesforce Data Export & API Adds scenarios Extended durations Customer specific implementation Integration

21. Enhance Optimized Path for Yammer

22. Decision points Identity type Single Namespace Convert to Paid Authentication requirements