Presentation is loading. Please wait.

Presentation is loading. Please wait.

Where we started at WPC 2014 WPC | July 2014 Where we got to before first call Sept 2014.

Similar presentations


Presentation on theme: "Where we started at WPC 2014 WPC | July 2014 Where we got to before first call Sept 2014."— Presentation transcript:

1

2 Where we started at WPC 2014 WPC | July 2014

3 Where we got to before first call Sept 2014

4 FastTrack and QuickLeads timeline Office 365 FastTrack & Adoption offer announced Office 365 FastTrack & Adoption offer live and in-market Partner deep-dive provides more details and what’s included Partner and customer feedback to involve partners sooner Contact process modified so partners are contacted first Positive PAC feedback; changes live in mid-Oct FastTrack portal open to all partners; emphasis on deployment plans

5 DataLOB Customer Partner

6 Office 365 FastTrack & Adoption offer announced Office 365 FastTrack & Adoption offer live and in-market Partner deep-dive provides more details and what’s included Partner and customer feedback to involve partners sooner Contact process modified so partners are contacted first Positive PAC feedback; changes live in mid-Oct FastTrack portal open to all partners; emphasis on deployment plans Remediation leads engaged partners worldwide through manual process More leads shared to drive customer adoption Leads routing process is automated worldwide

7 Customers who have a great experience getting started on a service use it more regularly Customers expect to use a cloud service as soon as they buy and have high expectations on speed to value Reduce the time it takes for partners to engage with the customer on high- margin value added services Accelerate partner engagement on high value services Shorten the time to value for customer Provide great customer experience FastTrack Guiding Principles

8 What does the data tell us about FastTrack Partner role & engagement P Customer behavior Customer satisfaction

9 Partner role & engagement 51% 49% of accounts did not have partners helping with onboarding 49% Partners are involved in 51% of customer accounts helping with onboarding

10 Partner role & engagement  “The people at the Onboarding Center were very skilled and helped us access high-level support resources. There’s value in having an open pipeline and sharing progress reports.” – Lars Riehn, CEO, infoWAN  Reduced deployment time by 2-4 weeks  Higher customer confidence  Clear communication with direct access to onboarding engineers Partner case study

11 Customer behavior What does the data tell us about FastTrack Customer satisfaction Partner role & engagement P

12 49% of accounts did not have partners helping with onboarding Customer behavior 49%

13 FastTrack QuickLeads worldwide 160,000+ total seat opportunities shared worldwide

14 Partner success with FastTrack QuickLeads “The single biggest benefit of the QuickLeads program is that it reduces the sales effort, and time we don’t spend selling the customer is time we can spend servicing the customer.” – Danny Burlage, CEO Why the success?

15 What does the data tell us about FastTrack Customer satisfaction Customer behavior Partner role & engagement P

16 Customer satisfaction 51% have OBC touch Our research indicates highest customer satisfaction occurs when partners & OBC work together 37% Improvement in time to onboard 64% Increase in customer satisfaction YOY

17 Customer feedback Thanks to the collaboration with Microsoft, we promptly received data storage and data processing services using modern equipment and reliable data transmission with "turnkey" data migration and onboarding with the help of professionals of the highest caliber. “ The integration process with the OBC (Office 365 Onboarding Center) was a critical factor for the successful completion of our project, and its ease of management has brought us greater operational agility. “

18 Continue onboarding support for all workloads Provide Email migration for eligible customers Onboarding & Migration available to be used by customers and by their partner Eligibility 150+ seats of eligible SKUs Available starting July 1, 2015 Provide onboarding support for all workloads Onboarding available to be used by customers and by their partner Eligibility 150+ seats of eligible SKUs Accelerate partner engagement on high value services Shorten the time to value for customer Provide great customer experience FY16 FastTrack Office 365 evolution CORE SERVICE BENEFIT Provide a consistent and straightforward experience to customers

19 $15 /seat from 150 -1000 seats $5 / seat thereafter, $60K maximum Active usage of 15% required for payment Two milestones available for payment (5% (1/3) & 15%) All workloads included besides Exchange (core benefit) Available from September 1, 2015 – March 31, 2016 $15 /seat from 150 -1000 seats $5 / seat thereafter, $60K maximum Active usage of 15% required for payment No limitations on workloads FY16 FastTrack Office 365 evolution Accelerate partner engagement on high value services Shorten the time to value for customer Provide great customer experience ADOPTION OFFER Adoption funds now available to all eligible customers Help partners engage with customers on advanced workloads

20 All Enterprise SKUs, paid G SKUs and paid EDU SKUs K SKUs and paid Non-profit SKUs now eligible for Onboarding + Migration Exchange, SharePoint, OneDrive for Business, Skype for Business + Enterprise Voice, Yammer, Office ProPlus, Project Online, Project Pro, Visio All Enterprise SKUs, paid G and A SKUs K SKUs or paid Non-Profit SKUs not eligible Exchange, SharePoint, OneDrive for Business, Skype for Business, Yammer, Office ProPlus, Project Online, Project Pro, Visio Accelerate partner engagement on high value services Shorten the time to value for customer Provide great customer experience FY16 FastTrack Office 365 evolution SKU EXPANSION & WORKLOADS Expand the list of SKUs and workloads to address broader set of customers

21 Use the FastTrack Portal ( http://portal.fasttrack.office.com ) http://portal.fasttrack.office.com Use the Adoption offer to engage customers on new business scenarios Expand beyond Exchange to improve opportunity & profitability Call to Action Build your business around advanced workloads Focus on adoption- related activities that drive active usage Build a success plan for your customers Resources available on ( http://aka.ms/fasttrackforpartners ) http://aka.ms/fasttrackforpartners Future roadmap updates will be shared via ( http :// roadmap.office.com ) http :// roadmap.office.com

22

23 Onboarding & Migration details

24 Microsoft delivered onboarding for all users, organization wide to Office 365 services Exchange, SharePoint, Skype for Business, Office 365 Pro Plus, Yammer. Direct remote assistance provided by an Microsoft onboarding expert who will assist with various onboarding activities using a combination of tools, documentation, guidance, and carry out configuration tasks where applicable Robust suite of automated checks and configuration to assess—current state assessment, identity management, and domain configuration Onboarding support will be available in the following languages: Chinese, English, French, German, Italian, Japanese, Brazilian Portuguese or Spanish Available for all customers with 150+ seats of E, G, A (paid), and eligible SKUs Direct engineering support to help you onboard your customer to Office 365

25 Office 365 Core Onboarding Support Activation of your Office 365 tenant Configuration guidance for TCP/IP protocols and firewall Configuration guidance of DNS for eligible services Validation of connectivity to Office 365 Installation guidance and configuration assistance as needed for the following identity services  For a single-forest environment:  Installing a directory synchronization server between your Active Directory Domain Services (AD DS) and Office 365, if required.  Configuring password synchronization with the Azure Directory Synchronization tool (DirSync).  Configuring password hash sync to Office 365, if required.  For multiple forest environment:  Installing Forefront Identity Manager 2010 R2 and the Azure Active Directory Connector. Note: Password hash sync is not available.  Configure synchronization between on-premises Active Directory forests and Office 365 directory (Azure Active Directory). Note: Development and implementation for custom rules extensions are out of scope. Installing a Yammer Directory Sync server between your AD DS and Yammer, if applicable Testing single sign-on (SSO) functionality if deployed Provide the customer with a Remediation checklist Eligibility of Customer Customer purchases at least 150 licenses for a new Office 365 tenant in one of the following plans for Office 365 service. * Office 365 Enterprise plans (E1, E3, E4) Exchange Online Plan 1 and Exchange Online Plan 2 Office 365 Pro Plus, SharePoint Online standalone plans, Skype for Business standalone plans, OneDrive Standalone plans. Office 365 Government plans (G1, G3, G4) Paid Office 365 Education plans (A3, A4) Office 365 Kiosk plans (K) Office 365 Non-Profit SKUs * Office 365 Midsize business plans, Office 365 small business (P1), Office 365 small business (P2) plans, Yammer Enterprise standalone plan; Office 365 Dedicated and ITAR-support plans are ineligible. Eligibility Applications and Services Microsoft will onboard one or all of the following applications to Office 365 if the customer has purchased them. Each application will go through the Onboarding exercise once within the 12-month period from the time of initiation. Exchange Online SharePoint Online Skype for Business Online Yammer Enterprise Office ProPlus OneDrive for Business Project Online, Project Pro Visio Microsoft-provided enhanced onboarding support for eligible customers

26 Skype for Business Online onboarding Provide guidance with: Provisioning Skype for Business identities for Office 365 Service Enabling online conferencing, instant messaging (IM) and presence features for Office 365. Conference Room Device account configuration Split Domain (Hybrid Configuration) Exchange Online onboarding Provide guidance with: Creation and/or update of Autodiscover and sender policy framework records in Domain Name System (DNS). Configuration of the messaging setup to enable email routing between source messaging system and Office 365 environments. Configuring hybrid setup either between single on-premises Exchange organization and Office 365 OR between multiple on-premises Exchange organizations and Office 365. SharePoint Online onboarding Provide guidance with: Setting up user provisioning including licensing Enabling site creation for customer administrator Planning site collections Securing content and managing permissions Enabling personal sites and social features Configuring SharePoint Online features. Microsoft-provided enhanced onboarding support for eligible customers Office 365 ProPlus onboarding Provide guidance with: Assigning end-user licenses. Configuring DNS, network port and firewall. Installing Office 365 ProPlus from the Office 365 portal. Setting up a single on-site distribution server for Office 365 ProPlus, including guidance for creating a configuration.xml file for the Office Deployment Tool.

27 Microsoft-provided enhanced onboarding support for eligible customers Yammer onboarding Provide guidance with: Converting your single Yammer Basic network into a single Yammer Enterprise network Enabling Office 365 Simplified Login Integrating a single Yammer Enterprise network with Yammer Single Sign-On (if applicable) Setting up Yammer directory synchronization (if applicable) OneDrive for Business onboarding Provide guidance with: Identifying on-premises SharePoint version and integration options. Identifying synchronization and identity options. Selecting a rollout option: just-in-time rollout or staged rollout (sequenced and phased). Preparing on-premises environment for OneDrive deployment. Identifying correct OneDrive for Business sync client. Configuration of DNS, network ports, and firewall. Assigning end-user licenses. Setting up SharePoint Online audiences to control and govern who gets OneDrive for Business. Deploying the OneDrive for Business sync client to desktops. (SharePoint 2013 SP1 only) If needed, redirect on-premises My Sites and personal document libraries to OneDrive for Business.

28  Modifications to the Office 365 Service beyond the configurable options  Overall program and project management of customer resources.  End-user communications, documentation, training, and change management  Help-desk documentation and training  Producing customer specific reports, presentations, or meeting minutes  Architectural and technical documentation specific to the customer  Procurement, installation, and configuration of software Modification of current operational model and operation guides Setting up multifactor authentication Decommissioning and removal of on- premises environments (like messaging and collaboration) Construction and maintenance of customer test environment Installation of service packs and any required updates on infrastructure servers Design, procurement, installation, and configuration of hardware and networking Provide / configure public SSL certificates General Activities Depending on environment, these are the activities you may need to perform: Configuration, packaging, and distribution of client software required for Office 365 Service Managing, configuring, and applying security policies Activating mobile devices Network configuration, analysis, bandwidth validation, testing, and monitoring Managing a technical change management approval process and supporting documentation Specifying and defining of group policies for user, workstation, and server management

29  AD DS design, installation, and configuration, including trusts and site definitions  If applicable, Multi-forest consolidation including consolidating or decommissioning existing AD DS domains or domain controllers (if any)  AD DS organizational unit restructuring, workstation migration, and group policy change within the existing AD DS domains  Attribute changes in AD DS to allow for filtering of objects with Directory Synchronization tool  AD DS remediation production changes required to get a complete sync  Forefront Identity Manager implementation or customizations to support multiple Active Directory forests Integration into any other identity providers, such as using WS-Federation or SAML 2 Integration with information cards or Windows CardSpace identity selector Firewall changes, perimeter network setup, load balancing, or any other form of networking changes Customizations to authentication pages Third-party or reverse-proxy integration for presentation of AD FS services to the Internet Configuration of two-factor authentication Supporting pre-authentication to access the AD FS servers from the Internet Identity Integration Activities Depending on environment, these are the activities you may need to perform: Customization of the Directory Synchronization tool Disaster planning for Directory Synchronization tool with SQL Server software SQL Server software installation of Directory Synchronization tool Facilitating BlackBerry Business Cloud Services for the Office 365 Service Customization of the DirSync tool Disaster planning for DirSync tool Application code modifications to implement federation solution Security assessments or security-policy recommendations

30  Infrastructure, design changes or modifications to existing on-premises messaging servers.  Configuration to existing on-premises messaging servers.  Coexistence with business applications.  Domino directory to Active Directory synchronizations.  Ongoing synchronization between the Lotus Domino directory and AD DS.  Synchronization of security groups from Domino directory to on-premises instance of AD DS. Messaging Activities Depending on environment, these are the activities you may need to perform: Connectivity to any other identity sources or interfaces beyond those that are eligible for Onboarding benefit. Provisioning or removing of identity objects throughout the solution. Workflow functionality for providing automated approval and denial capabilities. Dependent application discovery, remediation, modifications or troubleshooting.

31 Mailbox Migration Microsoft will perform the following responsibilities for the migrations: Provide standard template for scheduling mailbox migrations. Provide information on required permissions for Microsoft personnel. Collect pre-determined mailbox migration schedule in pre-determined format. Perform pre-migration checks and provide pre-migration failure report. This report will provide a list of mailboxes that have a potential of failure during a migration time slot. Attempt to perform migration of a single mailbox up to 2 times in a migration time slot before reporting that mailbox as a failed migration. For Exchange and IMAP4 based source environments, migrate mailbox content up to 85 percent of the user mailbox storage limit as defined in the Office 365 service descriptions (e.g. if mailbox storage limit is 50GB, then Microsoft will migrate up to 85% of 50GB storage limit). Enable SMTP mail routing coexistence between source messaging environment and Office 365 Exchange Online unless cutover migration is being used. Provide post-migration reports. Provide post-migration support for critical issues. Following are considered critical issues. Data loss during migration. Source environment becoming unavailable during migration. Migration activities resulting in issues in the source environment. Migration Schedule and Operations Migration will be done on standardized prescheduled 24x5 basis in pre-defined time slots. There are 3 migration time slots per migration day. There are 5 migration days in a week from Monday 2:00 AM UTC to Friday Midnight UTC meaning the last scheduled migration is Friday 8:00 PM UTC. All migrations will use cloud-based migration tools. All migrations will use remote, globally placed resources. All migrations will require appropriate access and permissions to the source environment. Microsoft-provided email data migration support for eligible customers

32 Customer Responsibilities  Complete Exchange Online onboarding via Microsoft Onboarding Center or pass the checks via Onboarding Center (OBC).  Handle all communications with end users.  Ensure appropriate level of client software is installed as per Office 365 guidelines. Client software requirements for Exchange Online can be referenced at Clients and Mobile Devices.Clients and Mobile Devices  Validate SMTP mail routing coexistence between source messaging environment and Office 365 Exchange Online if applicable.  Run the pre-migration checks script on the applicable mailboxes and remediate those that do not pass.  Provide schedule in defined method and list of specific mailboxes to migrate for each migration event at least 21 days in advance.  Add to the schedule, new or rescheduled mailboxes that are up to 10% of already scheduled mailboxes until 5 days prior to migration time slot. At that point this is the final schedule for the corresponding migration slot  Drop mailboxes from the schedule until 5 days in advance of migration time slot. At that point this is the final schedule for the corresponding migration slot  Schedule a target average number of mailboxes in a 24-hour period  Schedule a minimum of 35 mailboxes in a migration time slot.  If applicable, fix pre-migration failures.  Provide access and permissions to the source environment as defined to Microsoft personnel so as to allow Microsoft to carry out migration activities.  Support client-side migration issues. Run post-migrations operations when necessary.  Migrate client-side data if desired. This includes, but is not limited to local address books, data in local PST files, Outlook rules and local Outlook settings.  If applicable, reduce mailbox size below 85 percent of the target Office 365 mailbox limit.  Handle actions from the post migration report, including mailboxes that did not move.  If applicable, fix post-migration failures and reschedule the mailboxes.  Engage in post-migration support for critical issues. Following are considered critical issues. Data loss during migration. Source environment becoming unavailable during migration. Migration activities resulting in issues in the source environment. Microsoft-provided email migration support for eligible customers

33 Source environmentType of migrationWill migrateWill not migrate Exchange 2003 / 2007 / Exchange 2010 / Exchange 2013 Cutover migration From source mailbox Emails Mailbox Rules Delegates Mailbox contacts Calendar Tasks Public Folders External contacts Mail-enabled users Signature Mailbox dumpster Any email that is 25MB or larger Archive data Rights managed or encrypted emails Corrupted items Exchange 2003 / 2007 Staged migration From source mailbox Emails Mailbox Rules Delegates Mailbox contacts Calendar Tasks Distribution Lists and external contacts with directory synchronization Public Folders External contacts Mail-enabled users Signature Mailbox dumpster Any email that is 25MB or larger Archive data Rights managed or encrypted emails Corrupted items Exchange 2010 & 2013 organization Migration with hybrid deployment From source mailbox Emails Mailbox Rules Delegates Mailbox contacts Calendar Tasks Signature Distribution Lists and external contacts with directory synchronization Public Folders Any email 25MB or larger Journaling Archive or any 3rd party archive solution Archive data Rights managed or encrypted emails Corrupted items

34 Source environmentType of migrationWill migrateWill not migrate Google Apps for Work environment (Gmail, Contacts and Calendar only) Cutover or Staged Migration From source mailbox Emails Mailbox contacts Calendar Labels Rules Delegates Signature Tasks Any email 25MB or larger Archive data Rights managed or encrypted email Corrupted items Google hangouts Novell GroupWise 7.0.3+ Staged Migration From source mailbox Emails Calendar Mailbox Contacts Personal Groups Tasks (with limitations) Documents Distribution Lists and external contacts with directory synchronization Rules Proxies/Delegates/ACL conversion Signatures Contact Categories Encrypted email Search Folders Any email 25MB or larger Archive data Rights-managed or encrypted items Corrupted items Calendar coexistence is not included

35 Source environmentType of migrationWill migrateWill not migrate IBM Lotus Domino 7.0.3+ Staged Notes Migration From source mailbox Emails - last 90 days Calendar - last 90 days and 1 year of future items Mailbox Contacts - all Tasks - all Rooms and resources - provided they are implemented with the standard template Distribution Lists and external contacts with directory synchronization Mail files, including shared mail files, must use the standard mail template Signature Mailbox Rules Delegates. Encrypted email Document links Any email that is 25MB or larger. Archive data Corrupted items Calendar coexistence is not included IMAP4 source Migration using native IMAP tools From source mailbox Emails Rules Delegates Distribution Lists External contacts Mail-enabled users Mailbox contacts Calendar Signature Tasks Any email that is 25MB or larger. Archive data Encrypted email Corrupted items


Download ppt "Where we started at WPC 2014 WPC | July 2014 Where we got to before first call Sept 2014."

Similar presentations


Ads by Google