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 Design tailor-made solutions for architects and decision makers to meet complex business requirements

Arrow left icon
Product type Paperback
Published in Jan 2023
Publisher Packt
ISBN-13 9781804612637
Length 534 pages
Edition 2nd Edition
Languages
Concepts
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 (18) Chapters Close

Preface 1. Section I: The Basics FREE CHAPTER
2. Microsoft Power Platform and Microsoft Dynamics 365 Overview 3. Microsoft 365 and Microsoft Azure Overview 4. Section II: The Architecture
5. Understanding the Microsoft Power Platform Architecture 6. Power Platform Customization and Development Tools and Techniques 7. Application Lifecycle Management 8. Section III: The Implementation
9. Implementation Approach and Methodologies 10. Microsoft Power Platform Security 11. Microsoft Power Platform Extensibility 12. Microsoft Power Platform Integration 13. Microsoft Power Platform Data Migration 14. Best Practices for Solution Architecture 15. Other Books You May Enjoy
16. Index
Appendix

Application lifecycle management best practices

In the previous sections, we learned about the two key ALM pillars for Power Platform solution development: solution management and ALM automation using tools like Azure DevOps. In this section, you will learn several best practices for 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 for how to properly use solution types, structure and segment solutions, and use publishers.

General practices

It is the best practice to always create a specific solution package for a defined purpose and 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 and never for custom components. Custom components should be always created...

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