Architect solutions for Dynamics 365 and Power Platform

Advanced
Solutions Architect
Dynamics 365
Finance
Finance and Operations
Business Central
Customer Service
Field Service
Human Resources
Marketing
Commerce
Sales
Supply Chain Management
Power Automate
Power BI
Power Apps
Power Platform

A Solution Architect is responsible for the successful design, implementation, deployment, and adoption of an overall solution. A Solution Architect ensures that the solution meets the customer’s needs now and in the future. While the Solution Architect may not “click the buttons” during a deployment, they are ultimately responsible for the solution and work closely with the deployment team.

This learning path covers the pre-sales and analysis phases of a project to include:

  • What it takes to become a Solution Architect.
  • Discovering customer needs.
  • Proposing a solution.
  • Working with requirements.
  • Performing fit-gap analysis.

Instructor-led training (ILT) is available that provides more hands-on activities and both this Learning Path and ILT are needed for the exam. See courses MB-600T00-A and MB-700T00-A.

Prerequisites

  • Deep business acumen with Dynamics 365 and Power Platform.
  • Functional consultant experience with Dynamics 365 and Power Platform.
  • Familiarity with developer role activities for Dynamics 365 and Power Platform.

Modules in this learning path

Note

Effective November 2020

  • Common Data Service has been renamed to Microsoft Dataverse. Learn more.

  • Some terminology in Microsoft Dataverse has been updated. For example,entity is now table and field is now column. Learn more.

Modules will be updated soon to reflect the latest terminology.

The Solution Architect leads successful implementations and focuses on how solutions address the broader business and technical needs of organizations.  This module covers what it takes to get started as a Solution Architect and as key member of the overall project team.

Note

Effective November 2020

  • Common Data Service has been renamed to Microsoft Dataverse. Learn more.

  • Some terminology in Microsoft Dataverse has been updated. For example,entity is now table and field is now column. Learn more.

Modules will be updated soon to reflect the latest terminology.

Learn how to ask customers questions about their business processes and feature requirements to create a viable solution.

Note

Effective November 2020

  • Common Data Service has been renamed to Microsoft Dataverse. Learn more.

  • Some terminology in Microsoft Dataverse has been updated. For example,entity is now table and field is now column. Learn more.

Modules will be updated soon to reflect the latest terminology.

Learn how to propose a solution.

Note

Effective November 2020

  • Common Data Service has been renamed to Microsoft Dataverse. Learn more.

  • Some terminology in Microsoft Dataverse has been updated. For example,entity is now table and field is now column. Learn more.

Modules will be updated soon to reflect the latest terminology.

It is important to capture the customer’s needs accurately. This module explains how to capture requirements and identify functional and non-functional items.

Note

Effective November 2020

  • Common Data Service has been renamed to Microsoft Dataverse. Learn more.

  • Some terminology in Microsoft Dataverse has been updated. For example,entity is now table and field is now column. Learn more.

Modules will be updated soon to reflect the latest terminology.

A fit gap analysis identifies the difference between the known requirements and the proposed or current solution. This module covers performing a fit gap analysis.