Introduction to developing with Power Platform

Intermediate
Developer
Dynamics 365
Power Platform
Power Apps

So, you want to be a Power Platform developer! This learning path is the first step in learning about platform, tools, and the ecosystem of the Power Platform.

Prerequisites

  • Basic understanding of Power Platform.
  • Experience in software development against the Microsoft stack and Visual Studio.
  • Experience in administering solutions in Azure is preferred.

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 goal of this module is to give a broad-scoped overview of the developer experience as it relates to the Power Platform. It will cover a high-level introduction how the ecosystem is represented, with the intended audience being a software developer with limited experience in working with the Power Platform.

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.

This module will focus on the available developer tools that can help you perform development activities with the Microsoft Power Platform.

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.

This module will focus on the underlying solution architecture from a technical perspective and what extensibility options exist. It will also cover the ever-important element of the Microsoft Power Platform development, which is the decision-making process of determining when to use configuration versus code.