Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Microsoft Power Platform Enterprise Architecture

You're reading from   Microsoft Power Platform Enterprise Architecture A guide for architects and decision makers to craft complex solutions tailored to meet business needs

Arrow left icon
Product type Paperback
Published in Sep 2020
Publisher Packt
ISBN-13 9781800204577
Length 452 pages
Edition 1st Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
Robert Rybaric Robert Rybaric
Author Profile Icon Robert Rybaric
Robert Rybaric
Arrow right icon
View More author details
Toc

Table of Contents (15) Chapters Close

Preface 1. Section 1: The Basics
2. Chapter 1: Microsoft Power Platform and Microsoft Dynamics 365 Overview FREE CHAPTER 3. Chapter 2: Microsoft 365 and Microsoft Azure Overview 4. Section 2: The Architecture
5. Chapter 3: Understanding Microsoft's Power Platform Architecture 6. Chapter 4: Tools and Techniques 7. Chapter 5: Application Lifecycle Management 8. Section 3: Implementation
9. Chapter 6: Implementation Approach and Methodologies 10. Chapter 7: Microsoft Power Platform Security 11. Chapter 8: Microsoft Power Platform Extensibility 12. Chapter 9: Microsoft Power Platform Integration 13. Chapter 10: Microsoft Power Platform Data Migration 14. Other Books You May Enjoy

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...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime