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

Estimating the migration effort

Once you have defined the high-level requirements and matched these to Microsoft product capabilities, you can gain an understanding of the effort required to migrate from the current architecture to Power Platform. You can estimate the migration effort by considering the following:

  • The volume of data to be migrated
  • The structure and format of the data to be migrated
  • Access the source data
  • The level of data processing required during migration
  • Potential API throttling that may impact the migration, depending on the throughput required
  • Production downtime considerations and the level of risk mitigation required

At this early stage in the project, it would suffice to understand the migration strategy at a high level. You will want to consider the acceptable length of time for key systems to remain offline, the rollback requirements, and mitigation through gradual migration from legacy systems where possible.

We will...