this session details common scenarios for deploying office 365 services. office 365 provides a...
TRANSCRIPT
Office 365 Deployment Patterns and PracticesOctober 2013
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.
Agenda Quick Review of the Optimal paths for Exchange
Optimal Path for Domino Notes Optimal Path for Yammer Future Paths
Review Optimal Path for Exchange
EnhanceDeployPilot
Optimized Path for Exchange 2007
Cloud ID
Self service
PST
Connected account
Admin Driven
PST import tool
IMAP migration
Migration
Shared namespace
Self service PST
Admin driven
PST import tool
IMAP migration
Migration
Sync’d ID and password
Admin driven Staged Migration
Change ID Type
Federated IDChange ID Type
Migration
Self service
Admin driven
Migration
Hybrid servers
Admin driven
Migration
Hybrid migration
Hybrid migration
Staged migration
EnhanceDeployPilotOptimized Path for Exchange 2010
Cloud ID
Self service
PST
Connected account
Admin Driven
PST import tool
IMAP migration
Migration
Shared namespace
Self service PST
Admin driven
PST import tool
IMAP migration
Migration
Sync’d ID and password
Admin driven Hybrid Migration
Change ID Type
Federated IDChange ID Type
Migration
Self service
Admin driven
Hybrid migration
Migration
Optimal Path for Domino Notes
Pilot the service quicklyUser signs into Office 365 with a Cloud ID ([email protected])
Pilot the new Exchange mailboxNew mailbox in the cloudInbox content populated via Connected AccountUser sends/receives email as [email protected]
Pilot the new collaboration toolsRun online meetings with any user with computer
PC-to-PC calling, video conferencing, and app sharing.Collaborate using SharePoint Online team site and newsfeedsEasily store files in the cloud with SkyDrive Pro and share file with external users
Office across multiple devicesAccess 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 anywhereMobile connectivity options are built into the service – just start connecting devicesConnect to Office 365 via mobile devices with Exchange Active Sync for mailPlatform specific mobile apps bring best experience where it makes sense - i.e. OneNote, Lync
Control & manage your pilotCentralized administration from the Office 365 admin center in the serviceOnline management centers for Exchange, SharePoint, and LyncService health dashboard to monitor service maintenance and incidentsService use reporting available in the service admin center including service activity
1. Pilot ExperienceSetup on day 1
Full use of the service
User driven pilot
Pilot setup continues to step 2 deploy
Limited on-premises requirements
Sign-on
Collaboration
Clients
Mobile
Administration
NetworkWhat you need to connectNetwork access to service from client end points over ports 80 and 443Network bandwidth capacity
MailConnect to existing mail for the pilotPOP3 or IMAP4 protocol support for pilot users to use Connected Accounts
ClientsPilot user accessWeb client – minimum browserOffice 365 Pro Plus – clients running Windows 7 +
1. Pilot – What is requiredSimple requirements
Easy to start or stop
Setup in days
Adds on-premises integration
Pilot user and info is sustained
IT driven migration
Mail migration that best fits environment
Sign-onShared namespaceSign-on with the same user name as on premises
MailIntegrated mail flowShared SMTP domain and connectors facilitate mail flow between Office 365 and on-premises orgGlobal address list (imported)Additional users’ email content migrated via Connected Accounts
Collaboration
Sharing and working with othersLync business partner federationSite governance and provisioning supportSetup of Apps for Office corporate app catalog
ClientsIT managed client productivityOffice 365 ProPlus deployed to user desktop via IT process
MobileManaged mobile connectivitySend and receive mail from mobile device as on-prem email
AdministrationControl & monitorData loss prevention configuration (limited)Exchange Online Protection mail protection configuration (limited)
2. Deploy Experience – what’s added
Dedicated customer IT team
Change management readiness
IdentityWhat’s RequiredPopulate online directorySet Identity equal to on-prem user name
Network
What you need to connectNetwork access to service from client end pointsNetwork bandwidth availabilityAccess to maintain DNS entries for shared domain(s)
ClientsRequired to connect and deployWeb client – minimum browserOffice 365 Pro Plus – clients running Windows 7 +
MailRequired to setup and migrateAdmin access, managed by customer IT team
2. Deploy – what’s required
Advanced integrationSingle sign-on / ADFS3rd party identity providers – “Works with program”
Advance migration scenariosNotes mail, calendar, and contacts data migrations
Advanced integration and solution buildingRicher coexistence with on-prem Notes org, incl. Free/Busy information sharing via 3rd party toolsLync or SharePoint hybridSharePoint solutions – including BCS, Duet, etc.
Advanced client management capabilitiesVirtual desktop and virtual application scenarios
Connect to the serviceBlackberry Enterprise Sever integration
Leverage advanced service controlsData loss prevention configuration Exchange Online Protection mail protection configuration
3. Enhance- What’s addedAdds scenarios
Extended durations
Customer specific implementation
Ability to add to deployed clients at point in the future
Sign-on
Collaboration
Clients
Mobile
Administration
Directory integrationSync Domino Directory to on-prem AD via 3rd party toolsSync on-prem AD to MSOnline Directory Services
Management
EnhanceDeployPilot
Optimized Path for Notes Migrations
Cloud ID
Self service via connected accounts
Shared namespace
Sync’d IDand
password
Change ID Type
Self service
Admin Driven
OfficePro Plus
Sign-on using customer domain
Simple Coexistence
(mail routing)
IMAP Migration for additional
users
Import Remaining Users (unified GAL,
no DirSync)
Directory Prep(Domino & AD)
Directory Sync(AD to Office
365)
Enhanced Coex Free/Busy
(3rd party tools)
Enhanced data migration
(3rd party tools)
Federated ID
(ADFS)Self service
Admin Driven
OfficePro Plus
for additional
users
IMAP Migration
(Email only)
Admin Driven
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 pointsIdentity type
Namespace
Coexistence
Migration approach
Authentication requirements
Optimal Path for Yammer
Pilot the service quicklyEnroll O365 tenant for a free Yammer Basic network with a Cloud ID ([email protected])
Pilot the Yammer collaboration toolsReplace the SharePoint Online Newsfeed in the Office 365 header with YammerORIncorporate Yammer web parts into Team and My Sites in SharePoint Online
Yammer across multiple devicesWeb browser, Yammer desktop app
Experience Yammer anywhereMobile clients for Windows Phone, Android, Blackberry, iPad, iPhone
Self -serviceUsers navigate to sign-up URL and enter an email address to join
1. Pilot ExperienceEnroll on day 1
User-driven pilot
Create internal and external networks
Limited on-premises requirements
Sign-on
Collaboration
Clients
Mobile
Administration
NetworkWhat you need to connectNetwork access to service from client end points over ports 80 and 443Firewall/Proxy/Filtering/E-mail Whitelists
Browser
Clients
RequirementsWindows Phone 7 and higherAndroid v2.2 and higheriOS v5.0 and higherWindows XP and higherMac OS 10.5 and higherAdobe Air (desktop only)
1. Pilot – What is requiredSimple requirements
Single NamespaceBrowser requirementsInternet Explorer 8 or laterFirefox (latest version)Chrome (latest version)Safari (latest version)Java-script enabledFlash 9 or higher
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 enrollmentYammer Enterprise Admin ToolsNetwork Level Apps & IntegrationsSupport & ServicesContent 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
Dedicated customer IT team
Change management readiness
Identity
What’s RequiredMust designate a Verified Admin when working with Yammer Customer Support Manager to upgrade to EnterpriseCreate users in bulk using a CSVCreate users in bulk by implementing Yammer Dsync for directory synchronization
NetworkWhat you need to connectNetwork access to service from client end points
ClientsRequired to connect and deployNetwork access to service from client end points
2. Deploy – what’s required
Custom integrationSingle Sign-OnSharePoint 2010 integrationYammer EmbedYammer for SalesforceData Export & API
3. Enhance- What’s addedAdds scenarios
Extended durations
Customer specific implementation
Integration
EnhanceDeployPilot
Optimized Path for Yammer
Basic Network
Integration with
SharePoint Online
Sync’d ID
Convert to Paid
Network
Federated IDChange ID Type
SharePoint Newsfeed
replacement
Yammer Web Parts
Cloud ID
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 pointsIdentity type
Single Namespace
Convert to Paid
Authentication requirements
Future Paths
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)
24