Views:

In this article: Approach | Deployment Plan Project Phase | Core and Service Onboarding Project Phases | The difference between Core and Service Onboarding Projects | Resources


Overview

Approach

Partners should continue to familiarize themselves with Microsoft 365 Scenarios in the FastTrack Playbook. This explains the roadmap to enable M365 workloads, the Advanced Deployment Guides for Microsoft 365 and Office 365 Services, and Microsoft 365 FastTrack best practices.

Projects supports the customer requirement to assist with positioning Microsoft 365. It also provides closer integration between the FastTrack Ready Partner Team with the Microsoft Customer Success Unit (Microsoft Account Team).

The engagement model is divided into three sections:

  • Deployment Plan Project Phase
  • Core Onboarding Project Phase
  • Service Onboarding Project Phase

Deployment Plan Project Phase

The Deployment Plan Project Phase includes:

  • Field Engagement
  • Envisioning
  • Discovery
  • Deployment Planning

Core and Service Onboarding Project Phases

The Core and Service Onboarding Project Phases includes:

  • Kick-Off
  • Plan
  • Technical Onboarding
  • Migrate
  • Closeout

The difference between Core and Service Onboarding Projects

  • Core Onboarding Project is used to setup the initial Tenant Identity and Authentication.
  • Service Onboarding Project is used for service and/or workload enablement.

Differences between Core and Service Onboarding Projects

Resources

Microsoft is committed to transforming the go-to-market experience to better serve partners and our joint customers. Review the Microsoft Partner Commercial Incentive Guide for additional insight into how to maximize earning opportunities and create new value for customers.

Comments (1)
  • test comment