8. Pilot the service quicklySign-on
User signs into Office 365 with a Cloud ID (jane@contoso.onmicrosoft.com)
Pilot the new Exchange mailboxMail
New mailbox in the cloud
Inbox content populated via Connected account
User sends/receives email as Jane@contoso.com
User PST import option for additional content migration (mail/calendar/contacts)
Pilot the new collaboration toolsCollaboration
Run online meetings with any user with computer & app sharing, video conferencing, and PC-to-PC calling
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 devicesClients
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 anywhereMobile
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 pilotAdministration
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. What you need to connectNetwork
Network access to service from client end points over ports 80 and 443
Network bandwidth capacity
Pilot user accessClients
Web client – minimum browser
Office 365 Pro Plus – clients running Windows 7 +
Connect to existing mail for the pilotMail
POP3 or IMAP4 protocol support for pilot users to use Connected Accounts
10. Integrated identity managementSign-on
Sign-on with the same user and password as on premises
Integrated mail flow and migrationMail
Global address list
Full mail content migration – mail, calendar, contacts
Sharing and working with othersCollaboration
Lync business partner federation
Site governance and provisioning support
Setup of Apps for Office corporate app catalog
IT managed client productivityClients
Office 365 ProPlus deployed to user desktop via IT process
Managed mobile connectivityMobile
Send and receive mail from mobile device as on-prem email
Control & monitorAdministration
Data loss prevention configuration (limited)
Exchange Online Protection mail protection configuration (limited)
11. What‟s RequiredIdentity
Directory Sync server/s
AD meets service requirements for hygiene
Same password on-prem and in cloud via password sync
What you need to connectNetwork
Network access to service from client end points
Network bandwidth availability
Access to maintain DNS entries for share domains
Required to connect and deployClients
Web client – minimum browser
Office 365 Pro Plus – clients running Windows 7 +
Required to setup and migrateMail
Admin access
12. Advanced integrationSign-on
Single sign-on / ADFS
3rd Party identity providers – “Works with program”
Advance migration scenariosMail
Notes migrations
Hybrid Exchange for 2007 or 2003
Advanced integration and solution buildingCollaboration
Lync or SharePoint hybrid
SharePoint solutions – including BCS, Duet, etc.
Advanced client management capabilitiesClients
Virtual desktop and virtual application scenarios
Connect to the serviceMobile
Blackberry Enterprise Sever integration
Leverage advanced service controlsAdministration
Data loss prevention configuration
Exchange Online Protection mail protection configuration
28. Key Capabilities Step 1 – Pilot Step 2 – Deploy Step 3 - Extend
Identity
Identity Sign On Cloud IDs Corporate AD user
account with same
password via Password
Sync
Corporate AD user account
and password via ADFS
Option for Integration with
“Works with O365” Identity
Providers
Option for Shibboleth
Integration
Active Directory
Remediation
Not applicable IdFix Dirsync Error
Remediation Tool
IdFix Dirsync Error
Remediation Tool
Custom Engagement
29. Key Capabilities Step 1 – Pilot Step 2 – Deploy Step 3 - Extend
Exchange
Global Address List Cloud Users Dirsync Users Dirsync users
FIM 2010 via O365
connector
Calendar Free/Busy
sharing
Cloud Users Dirsync Users (req. Ex 2010 SP3) Dirsync Users
Exchange Federation to
other O365 or Exchange
Corporate Email Yes via “connected accounts” Yes via Corporate Domain add a
Data Migration Options User driven migrations via
connected accounts (mail
only)
User driven PST import
(mail/calendar/contacts)
User Driven
IT Driven via Staged Migration
or Hybrid Exchange (req. Ex
2010 SP3)
Hybrid Exchange for 2010,
2007 or 2003 on-premises
IBM Notes Migration
Option
OWA / Full Outlook a a a
Mobile via Active Sync Cloud Email Address (Send
From)
Corporate Email Address
Option for BlackBerry BCS
Corporate Email Address
Option for BlackBerry BCS
30. Key Capabilities Step 1 – Pilot Step 2 – Deploy Step 3 - Extend
Lync
IM & P a a a
Online Meetings a a a
Video Conferencing a a a
PC and Application Sharing a a a
Mobile Lync Clients a a a
Skype Federation (Summer
„13)
a a a
Lync External Federation a a
Lync Hybrid Option a
Lync Hybrid Voice Option a
31. Key Capabilities Step 1 – Pilot Step 2 – Deploy Step 3 - Extend
SharePoint
Team Sites a a a
Sky Drive Pro a a a
External Sharing a a a
Office Web Apps a a a
Public Site with
Corporate DNS
a a
SharePoint
Solutions (BCS,
Duet)
a
Click-to-Run Office
2013 Prof Plus
Self-Serve for Pilot Users Self-Serve for Dirsync
Users
IT Managed Deployment
Self-Serve for Dirsync
Users
IT Managed Deployment
32. Effort Step 1 – Pilot Step 2 – Deploy Step 3 - Extend
Number of Users 25 to 250 Up to Office 365 Licenses Up to Office 365 Licenses
Level of Effort Low Medium High
No on-premises components
SMTP/POP needed for
connected accounts
experience
Dirsync Appliance
Dirsync scoping optional
AD Remediation (IdFix
Dirsync Error Remediation
Tool available)
Option for Exchange Hybrid
configuration if Ex 2013 SP3
On-Prem via Configuration
Wizard
Dirsync Appliance – or-
O365 Connector for FIM
ADFS Infrastructure and
Capacity Planning
Exchange Hybrid
configurations via HCW and
Manual steps as required per
Exchange version
Lync Hybrid Option
Lync Hybrid Voice Option
This is what a traditional on-premises deployment project looks like –You are used to building the environment before you can begin moving data and starting any experienceThis approach results in the outcome of users getting first access weeks into a deploymentWith a cloud deployment the approach needs to be different – don’t treat it the same way In a cloud deployment you have the option to start moving into a environment which is already built
The result is a new way of approaching onboading the service – We begin with a pilot – with structure to help a customer quickly begin using the service in a meaningful way – this enables us to have a conversation about the service features and truly understand the customer needs as they work with the service
Rich user experience and productivity solution can be delivered with minimal on-premises requirementsCustomer choice in deployment models considering investment required vs. time to valueContinuing deployment path builds upon the previous steps, no throw away or restart effortsOffice 365 deployment options with well defined capabilities grouped into 3 stepsAbility to extend and deliver new capabilities to your users as your needs changeMultiple data migration methods including user self-service and IT driven approachesThree user identity models to fit your needs: Cloud IDs, Synchronized IDs and Federated IDsDeployment Portal with prescriptive step-by-step guidance and video instructions
An ApproachCustomers experience Service Value early!Customers Evolve into Features when and if needed!Customers determine how far down The Path to go!Highlight time to realize each phase PilotUse service earlyAllow customer to use service and see how it fits needsShow option for simple and quick deploymentDeployBroad production use quicklyOption to meet time to service use with deployment optionsExtendAdded as required to meet needsNot required – use where requried
Land key point that experience is delivered day 1.Dwell on what it means to use the full service – users meet real scenario needs, across workloads – begin using the workload that brings value to them day 1Data migration is drive by users in the pilot.What IT implements and what users add to the service (data) continue on to step 2 deploy – no reset or restartRequirements to enable this experience is very limited (detailed in next step)Explain the experience users get in the pilot – (don’t spend time describing how they get here)Sign-onUnique Office 365 sign-on – users sign-in with new *.onmicrosoft.com id and passwordNo local AD integration –new namespaceMailAccess to existing mail – including send and receive as current address via connected accountsNo on-prem GAL, no contact or calendar migration with connected accountsFull Exchange online feature capabilities for mail, calendar, and contacts. Rich Outlook web access browser capabilities including offline OWA capability.User driven mail migration via connected accounts (mail only) or user PST import (mail/calendar/contacts)CollaborationUse online capabilitiesClientLead is web apps – means they can start without disruption to current desktopUsers have ability to add ProPlus via 365 portalMobileMobile connectivity options are built into Office 365 – no additional configuration – just start connecting mobile devicesMobile app clients available to bring best experience to the devices where it makes sense – i.e. OneNote, Lync, etc.Admin features starting in the pilotShow sample pilot setup or leverage appendix slides to show pilot experience aspects
Sign-inSame sign-in – on-prem and in cloud via sync’d accountsSame password on-prem and in cloud via password sync
Use technology drill down slides to lead detailed discussion on key service items that enable a quick and predictable step 2 deployment
Guidance tailored to selected flowSystem validation to verify task are completed correctlyOnRamp guides many of the step 2 activities to setup the deployment It provides a guided deployment plan that meets customer deployment and starting pointIt carries out system checks to validate deployment tasks are completed correctly to help expedite the deployment and improve the experience.
Technical Notes:Does not have dependency on any other toolsTool has the capability for export to CVS and LDF file formatsAvailable for download from TechNet.
Technical Notes:Configuration account cannot be MSOL_AD_Sync accountMust provide Enterprise Admin account to access forestConfiguration changes not persistent through upgrades
Technical Notes:Configuration account cannot be MSOL_AD_Sync accountMust provide Enterprise Admin account to access forestConfiguration changes not persistent through upgrades
Technical Notes:Scenarios:Single Active Directory forests only, using DirSync.Non-AD solutions can use PowerShell to set/sync passwords through custom.Multi-forest scenarios are currently out of scope.One-way synchronization only: Active Directory to Office 365No capability to reset or change on-premises passwords initiated from Office 365Password Sync will apply at the tenant level.All users that are in the scope of DirSync will have their passwords synchronized.Deployment:Password Sync is integrated in the DirSync toolNo requirement for additional hardware or software, beyond DirSync requirementsNo requirement for any per-Domain Controller componentNo requirement to enable reversible password encryption in Active Directory.Security and Policies:Only the Active Directory Password Hash is synchronizedActual Passwords are not synchronized.Passwords are synced out of band with the regular object sync.Should be seconds or a few minutes (less than 5 min.), not hoursSynchronized passwords are not subject to Office 365 Password Policies.Active Directory policies apply.
Use as reference card to compare features in steps