1 / 24

Office 365 Deployment Patterns and Practices

Office 365 Deployment Patterns and Practices. October 2013. Session Overview.

nansen
Download Presentation

Office 365 Deployment Patterns and Practices

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Office 365 Deployment Patterns and Practices October 2013

  2. Session Overview • 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. Agenda Quick Review of the Optimal paths for Exchange Optimal Path for Domino Notes Optimal Path for Yammer Future Paths

  4. Review Optimal Path for Exchange

  5. Optimized Path for Exchange 2007 Enhance Pilot Deploy Self service PST Cloud ID PST Migration Shared namespace Self service PST import tool Admin driven Hybrid migration Connected account Admin driven IMAP migration Migration Hybrid servers Change ID Type Migration Migration PST import tool Sync’d ID and password Self service Admin Driven Hybrid migration Migration IMAP migration Admin driven Staged Migration Admin driven Change ID Type Federated ID Staged migration

  6. Optimized Path for Exchange 2010 Pilot Deploy Enhance Self service PST Cloud ID PST Migration Shared namespace Self service PST import tool Connected account Admin driven IMAP migration Change ID Type Migration Migration PST import tool Sync’d ID and password Self service Admin Driven Migration IMAP migration Admin driven Hybrid Migration Admin driven Change ID Type Federated ID Hybrid migration

  7. Optimal Path for Domino Notes

  8. 1. Pilot Experience Setup on day 1 Full use of the service User driven pilot Pilot setup continues to step 2 deploy Limited on-premises requirements • Pilot the service quickly • User signs into Office 365 with a Cloud ID (jane@contoso.onmicrosoft.com) Sign-on Mail • Pilot the new Exchange mailbox • New mailbox in the cloud • Inbox content populated via Connected Account • User sends/receives email as Jane@contoso.com Collaboration • 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 Clients • 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 Mobile • 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 Administration • 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

  9. 1. Pilot – What is required Simple requirements Easy to start or stop • What you need to connect • Network access to service from client end points over ports 80 and 443 • Network bandwidth capacity Network 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 +

  10. 2. Deploy Experience – what’s added Setup in days Adds on-premises integration Pilot user and info is sustained IT driven migration Mail migration that best fits environment • Shared namespace • Sign-on with the same user name as on premises Sign-on 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)

  11. 2. Deploy – what’s required 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) Mail • Required to setup and migrate • Admin access, managed by customer IT team Clients • Required to connect and deploy • Web client – minimum browser • Office 365 Pro Plus – clients running Windows 7 +

  12. 3. Enhance- What’s added Adds scenarios Extended durations Customer specific implementation Ability to add to deployed clients at point in the future • Advanced integration • Single sign-on / ADFS • 3rd party identity providers – “Works with program” Sign-on Mail • Advance migration scenarios • Notes mail, calendar, and contacts data migrations Management • Directory integration • Sync Domino Directory to on-prem AD via 3rd party tools • Sync on-prem AD to MSOnline Directory Services Collaboration • 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. Clients • Advanced client management capabilities • Virtual desktop and virtual application scenarios Mobile • Connect to the service • Blackberry Enterprise Sever integration Administration • Leverage advanced service controls • Data loss prevention configuration • Exchange Online Protection mail protection configuration

  13. Optimized Path for Notes Migrations Deploy Enhance Pilot Cloud ID Shared namespace Directory Prep (Domino & AD) Sync’d ID and password Admin Driven IMAP Migration (Email only) Change ID Type Sign-on using customer domain Directory Sync (AD to Office 365) Self service via connected accounts Federated ID (ADFS) Simple Coexistence (mail routing) Self service Office Pro Plus for additional users Enhanced Coex Free/Busy (3rd party tools) Enhanced data migration (3rd party tools) Import Remaining Users (unified GAL, no DirSync) Office Pro Plus Admin Driven IMAP Migration for additional users Admin Driven Self service

  14. Optimized path Domino NotesRecap Pilot service in about an hour Deployment options to meet your requirements Leverage 3rd Party tools for IT led migration in Step 3 Decision points Identity type Namespace Coexistence Migration approach Authentication requirements

  15. Optimal Path for Yammer

  16. 1. Pilot Experience Enroll on day 1 User-driven pilot Create internal and external networks Limited on-premises requirements • Pilot the service quickly • Enroll O365 tenant for a free Yammer Basic network with a Cloud ID (jane@contoso.com) Sign-on Collaboration • 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 Clients • Yammer across multiple devices • Web browser, Yammer desktop app Mobile • Experience Yammer anywhere • Mobile clients for Windows Phone, Android, Blackberry, iPad, iPhone Administration • Self -service • Users navigate to sign-up URL and enter an email address to join

  17. 1. Pilot – What is required Simple requirements Single Namespace • What you need to connect • Network access to service from client end points over ports 80 and 443Firewall/Proxy/Filtering/E-mail Whitelists Network Browser • Browser requirements • Internet Explorer 8 or later • Firefox (latest version) • Chrome (latest version) • Safari (latest version) • Java-script enabled • Flash 9 or higher 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)

  18. 2. Deploy Experience – what’s added Setup in days Yammer Enterprise Customer Success Manager Administrative Control Pilot users and info are sustained Provisioning tools for creating users • 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) Administration

  19. 2. Deploy – what’s required 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

  20. 3. Enhance- What’s added Adds scenarios Extended durations Customer specific implementation • Custom integration • Single Sign-On • SharePoint 2010 integration • Yammer Embed • Yammer for Salesforce • Data Export & API Integration

  21. Optimized Path for Yammer Enhance Pilot Deploy Cloud ID Basic Network Integration with SharePoint Online Convert to Paid Network SharePoint Newsfeed replacement Change ID Type Federated ID Sync’d ID Yammer Web Parts

  22. Optimized path for YammerRecap Pilot free service in about an hour Deployment options to meet your requirements Leverage bulk provisioning or Synchronized IDs after conversion to paid service Optionally enhance service over time for Federated login Decision points Identity type Single Namespace Convert to Paid Authentication requirements

  23. Future Paths

  24. Paths we are working on • Multi Forests with single tenant* • Single Forest with multiple tenants • Multiple Forests with multiple tenants • Yammer with multiple namespaces • Single network with multiple namespaces • Multiple networks • Adding services • Start with O365 Pro Plus and add O365 Suite • Start with O365 Pro Plus and add O365 Stand alone services (EXO, SPO, LYO) • Start with SPO and add O365 Suite • Start with SPO and add other stand alone services (O365 Pro Plus, EXO, LYO) Note: Scenarios in Red next optimal paths to be added. (* This scenario will be Multiple Accounts Forest w/Exchange in Resource Forest model moving to Single Office 365 Tenant)

More Related