Book Image

Microsoft Power Platform Solution Architect's Handbook

By : Hugo Herrera
4.5 (2)
Book Image

Microsoft Power Platform Solution Architect's Handbook

4.5 (2)
By: Hugo Herrera

Overview of this book

If you’ve been looking for a way to unlock the potential of Microsoft Power Platform and take your career as a solution architect to the next level, then look no further—this practical guide covers it all. Microsoft Power Platform Solution Architect’s Handbook will equip you with everything you need to build flexible and cost-effective end-to-end solutions. Its comprehensive coverage ranges from best practices surrounding fit-gap analysis, leading design processes, and navigating existing systems to application lifecycle management with Microsoft Azure DevOps, security compliance monitoring, and third-party API integration. The book takes a hands-on approach by guiding you through a fictional case study throughout the book, allowing you to apply what you learn as you learn it. At the end of the handbook, you’ll discover a set of mock tests for you to embed your progress and prepare for PL-600 Microsoft certification. Whether you want to learn how to work with Power Platform or want to take your skills from the intermediate to advanced level, this book will help you achieve that and ensure that you’re able to add value to your organization as an expert solution architect.
Table of Contents (23 chapters)
1
Part 1: Introduction
4
Part 2: Requirements Analysis, Solution Envisioning, and the Implementation Roadmap
10
Part 3: Architecting the Power Platform Solution
15
Part 4: The Build – Implementing Solid Power Platform Solutions
20
Part 5: Power Platform Solution Architect Certification Prep

Best fit analysis deep-dive – matching AppSource, third-party product capabilities

Microsoft AppSource provides extensions to the standard Power Platform and Dynamics 365 product capabilities. As part of the discovery phase, you will make use of this resource to fill any gaps in Microsoft solution’s feature sets. 

AppSource components are available for review at https://appsource.microsoft.com/.

The proposed rationale behind using an AppSource and third-party component to fulfill organizational requirements is as follows: 

  • The standard Power Platform functionality does not fulfill a requirement.
  • It is not possible to adapt the requirement to match the Power Platform feature set.
  • One or more AppSource components exist that fulfill the requirement.
  • The AppSource components have been trialed in a POC, demonstrated, and rated internally to confirm their fitness for purpose.
  • The vendor has been identified...