Book Image

Microsoft Power Platform Enterprise Architecture

By : Robert Rybaric
Book Image

Microsoft Power Platform Enterprise Architecture

By: Robert Rybaric

Overview of this book

For forward-looking architects and decision makers who want to craft complex solutions to serve growing business needs, Microsoft Power Platform Enterprise Architecture offers an array of architectural best practices and techniques. With this book, you’ll learn how to design robust software using the tools available in the Power Platform suite and be able to integrate them seamlessly with various Microsoft 365 and Azure components. Unlike most other resources that are overwhelmingly long and unstructured, this book covers essential concepts using concise yet practical examples to help you save time. You’ll develop the skills you need to architect, design, and manage a complex solution as you follow the journey of a fictitious enterprise customer as they enter the world of Power Platform. Throughout the book, you’ll discover how to combine the functionality of Power Apps, Power Automate, Power BI, and Power Virtual Agents with various methodologies to effectively address application lifecycle management, security, and extensibility. Finally, you'll learn how to overcome common challenges in migrating data to and from Microsoft Power Platform using proven techniques. By the end of this book, you’ll have the strategic perspective of an enterprise architect to make accurate architectural decisions for your complex Power Platform projects.
Table of Contents (15 chapters)
1
Section 1: The Basics
4
Section 2: The Architecture
8
Section 3: Implementation

Application lifecycle management best practices

In the previous sections, we learned about the two key ALM pillars for Power Platform solution development: the solution management and the use of Azure DevOps. In this section, you will learn several best practices on how to make the best of using these two components.

Solution best practices

First, we will provide an overview of solution management-related best practices on how to properly use solution types, structure and segment solutions, and publishers.

General practices

It is best practice to always create a specific solution package for a defined purpose and to not use the Default Solution or just try to customize the environment outside of any dedicated solution package. While it is possible to include existing components in a solution package at any time, this should be only used to include standard components but never custom components. Custom components should always be created in the context of a solution from...