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

Implementing solutions that work within Power Platform API limits

Power Platform applications are required to work within a set of API limits. These limits are in place to prevent the cloud-based platform from being overused and to provide a reliable service to all its users. You will typically assess the projected consumption during the design stage. Solution architects review detailed designs to identify areas that may lead to a Power Platform component breaching API limits.

User API limits

Users interact with Dataverse either via a Power App (for example, a Model-Driven App) or via the Dataverse API, as is the case with application users. The published request limits change from time to time (please visit https://docs.microsoft.com/power-platform/admin/api-request-limits-allocations for the latest allocation limits).

Licensed user request limits

Depending on the type of license, users will be presented with different API limit allocations. Solution architects review...